Bug#301127: kaboodle dies with "sigsev" or so when trying to play an mpeg
SO, I've updated the system today, problem is still existing. Message is (translated): "soundserver (artsd) died and leaved signal 11 (SIGSEGV)." So perhaps it's the wrong bugreport and it's for artsd? @ Steve: problem exists with any mpg I've got here on my system. After testing this, *.wmv are running, but I only hear sound, theres no picture. The same files are played fine under 32-Bit on the same system. ciao, Dirk P.S.: at the time I have not installed gdb - is it needed? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301127: kaboodle dies with "sigsev" or so when trying to play an mpeg
On Wed, Mar 23, 2005 at 05:28:59PM -0500, Justin Pryzby wrote: > On Wed, Mar 23, 2005 at 10:39:16PM +0100, Dirk Salva wrote: > > Package: kaboodle > > Version: 4:3.3.1-2 > > Severity: grave > > Justification: renders package unusable > > When I start trying to view an mpeg or something else (like from leech.dk), > > kaboodle only starts, but does not play. When I push play-button, it > > breaks with a sigsev (KDE-crash-notifier) or so. Under 32bit sarge the same > > video-file works fine. Asus A8V Deluxe, NVidia 6600GT, 1GB RAM. > Can you run it under GDB and see if the backtrace is usable? > $ gdb kaboodle > > run > > bt > Can someone test this on a 64 bit architecture other than amd64? This > is sarge-ignore if the other 64 bit archs work. If someone can provide me a reasonably-sized sample video file that's known to work with kaboodle on i386 and known to fail on amd64, I can test it on an alpha here. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#301124: klaptopdaemon: feature request: "Lock desktop" as another Lid-Action
On Wednesday 23 March 2005 22:55, Tobias Geiger wrote: > Package: klaptopdaemon > Version: 4:3.4.0-0pre1 > Severity: wishlist > > > Hi, > > i'd be great if there would be a "Lock down Desktop" - Option in > Klaptopdaemon within the "Lid-Actions" > Right now know problem to workaround this > (small entry like "dcop kdesktop KScreensaverIface lock" in > /etc/acpi/actions/lm_lid.sh) but this requires ugly su - wrappers and is > therefore only practical on a single-user-laptop ;) If the script is run as root you could do dcop --all-users --all-sessions Cheers, Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KDE_3_3_BRANCH: kdesdk/debian
CVS commit by benb: Install cvsforwardport, which has been added to KDE_3_3_BRANCH. Acvsforwardport.1 1.1.4.1 M +1 -0 changelog 1.60.2.7 M +1 -0 kdesdk-scripts.install 1.12.2.2 M +1 -0 kdesdk-scripts.manpages 1.13.2.2 --- kdesdk/debian/changelog #1.60.2.6:1.60.2.7 @@ -7,4 +7,5 @@ * Added a note to README.Debian in the poxml package regarding the necessity of system identifiers (closes: #286103). + * Installing the new script cvsforwardport and a corresponding manpage. -- Ben Burton <[EMAIL PROTECTED]> Thu, 24 Mar 2005 07:59:47 +1100 --- kdesdk/debian/kdesdk-scripts.install #1.12.2.1:1.12.2.2 @@ -10,4 +10,5 @@ usr/bin/cvsblame usr/bin/cvscheck +usr/bin/cvsforwardport usr/bin/cvslastchange usr/bin/cvslastlog --- kdesdk/debian/kdesdk-scripts.manpages #1.13.2.1:1.13.2.2 @@ -9,4 +9,5 @@ debian/cvsbackport.1 debian/cvscheck.1 +debian/cvsforwardport.1 debian/cvslastchange.1 debian/cvslastlog.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301127: kaboodle dies with "sigsev" or so when trying to play an mpeg
severity 301127 important stop amd64 is not an official architecture at this point, so this is hardly release critical. It would also be helpful if you updated to the latest packages (unless amd64 is really out of date, kdelibs and kdemultimedia all have updates over the versions listed in your report). Cheers, Christopher Martin On March 23, 2005 16:39, Dirk Salva wrote: > Package: kaboodle > Version: 4:3.3.1-2 > Severity: grave > Justification: renders package unusable > > When I start trying to view an mpeg or something else (like from > leech.dk), kaboodle only starts, but does not play. When I push > play-button, it breaks with a sigsev (KDE-crash-notifier) or so. Under > 32bit sarge the same video-file works fine. Asus A8V Deluxe, NVidia > 6600GT, 1GB RAM. pgpgjGe0X4yTg.pgp Description: PGP signature
Processed: Re: Bug#301127: kaboodle dies with "sigsev" or so when trying to play an mpeg
Processing commands for [EMAIL PROTECTED]: > severity 301127 important Bug#301127: kaboodle dies with "sigsev" or so when trying to play an mpeg Severity set to `important'. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KDE_3_3_BRANCH: kdesdk/debian
CVS commit by benb: Another 3.3.2 upload including the umbrello drag-and-drop bugfix, the full GFDL in debian/copyright and additional documentation for the poxml package. M +11 -0 changelog 1.60.2.6 M +412 -0copyright 1.15.2.3 M +32 -10poxml.README.Debian 1.1.2.2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301127: kaboodle dies with "sigsev" or so when trying to play an mpeg
On Wed, Mar 23, 2005 at 10:39:16PM +0100, Dirk Salva wrote: > Package: kaboodle > Version: 4:3.3.1-2 > Severity: grave > Justification: renders package unusable > > When I start trying to view an mpeg or something else (like from leech.dk), > kaboodle only starts, but does not play. When I push play-button, it > breaks with a sigsev (KDE-crash-notifier) or so. Under 32bit sarge the same > video-file works fine. Asus A8V Deluxe, NVidia 6600GT, 1GB RAM. Can you run it under GDB and see if the backtrace is usable? $ gdb kaboodle > run > bt Can someone test this on a 64 bit architecture other than amd64? This is sarge-ignore if the other 64 bit archs work. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301127: kaboodle dies with "sigsev" or so when trying to play an mpeg
Package: kaboodle Version: 4:3.3.1-2 Severity: grave Justification: renders package unusable When I start trying to view an mpeg or something else (like from leech.dk), kaboodle only starts, but does not play. When I push play-button, it breaks with a sigsev (KDE-crash-notifier) or so. Under 32bit sarge the same video-file works fine. Asus A8V Deluxe, NVidia 6600GT, 1GB RAM. -- System Information: Debian Release: 3.1 64-Bit Architecture: amd64 (x86_64) Kernel: Linux 2.6.10-9-amd64-k8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages kaboodle depends on: ii kdelibs4 4:3.3.2-1 KDE core libraries ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libarts1 1.3.2-2 aRts Sound system ii libasound2 1.0.8-3 ALSA library ii libaudio2 1.7-2 The Network Audio System (NAS). (s ii libaudiofile0 0.2.6-5 Open-source version of SGI's audio ii libc6 2.3.2.ds1-20.0.0.1.pure64 GNU C Library: Shared libraries an ii libesd00.2.35-2 Enlightened Sound Daemon - Shared ii libfam0c1022.7.0-6 client library to control the FAM ii libgcc11:3.4.3-9 GCC support library ii libglib2.0-0 2.6.3-1 The GLib library of C routines ii libice64.3.0.dfsg.1-10 Inter-Client Exchange library ii libidn11 0.5.13-1.0GNU libidn library, implementation ii libjack0.80.0- 0.99.0-6 JACK Audio Connection Kit (librari ii libmad00.15.1b-1 MPEG audio decoder library ii libogg01.1.0-1 Ogg Bitstream Library ii libpng12-0 1.2.8rel-1PNG library - runtime ii libqt3c102-mt 3:3.3.3-8 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-10 X Window System Session Management ii libstdc++5 1:3.3.5-8 The GNU Standard C++ Library v3 ii libvorbis0a1.0.1-1 The Vorbis General Audio Compressi ii libvorbisenc2 1.0.1-1 The Vorbis General Audio Compressi ii libvorbisfile3 1.0.1-1 The Vorbis General Audio Compressi ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-10 X Window System miscellaneous exte ii libxrender10.8.3-7 X Rendering Extension client libra ii libxt6 4.3.0.dfsg.1-10 X Toolkit Intrinsics ii xlibs 4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-4 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassigning
Processing commands for [EMAIL PROTECTED]: > reassign 300747 kinput2-canna Bug#300747: kde: whole GUI hangs when using canna Japanese input system Bug reassigned from package `kde' to `kinput2-canna'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301124: klaptopdaemon: feature request: "Lock desktop" as another Lid-Action
Package: klaptopdaemon Version: 4:3.4.0-0pre1 Severity: wishlist Hi, i'd be great if there would be a "Lock down Desktop" - Option in Klaptopdaemon within the "Lid-Actions" Right now know problem to workaround this (small entry like "dcop kdesktop KScreensaverIface lock" in /etc/acpi/actions/lm_lid.sh) but this requires ugly su - wrappers and is therefore only practical on a single-user-laptop ;) Sorry if such feature-requests are wrong in the debian-bug-list... Greetings Tobias -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages klaptopdaemon depends on: ii kdelibs4 4:3.4.0-0pre2 core libraries for all KDE applica ii libc62.3.2.ds1-20GNU C Library: Shared libraries an ii libgcc1 1:3.4.3-6 GCC support library ii libqt3c102-mt3:3.3.3-8 Qt GUI Library (Threaded runtime v ii libstdc++5 1:3.3.5-8 The GNU Standard C++ Library v3 ii libxtst6 4.3.0.dfsg.1-10 X Window System event recording an ii xlibs4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-kde-talk] Logitech mice and media:/ kioslave support
On March 22, 2005 09:54, Iacopo Spalletti wrote: > Alle 14:19, martedì 22 marzo 2005, Christopher Martin ha scritto: > > On March 22, 2005 08:02, Iacopo Spalletti wrote: > > > I'm testing packages from > > > http://pkg-kde.alioth.debian.org/kde-3.4.0/. > > > > > > Packages do not provides support for the logitech mice features > > > module in kcontrol; such module needs special permissions (rw for the > > > user who is owning X) on device file (which is normally owned by > > > root); kde upstream provides the usbmap file and a simple shell > > > script to fix this. By default the script uses pam_console to check > > > for X user, but to my knowledge debian does not use such pam module, > > > so i grabbed the user grepping command from Ubuntu. > > > I can work on a patch or just email such files to the list. > > > > If you could explain further the exact nature of the problem, I would > > be grateful. > > With KDE 3.4 is shipped an addon to kde control panel available in > "Control Center->Peripherals->Mouse" which gives information about > logitech mice. Such addon needs the user to own the device file in > /proc/bus/usb directory to work. > KDE sources provides two files for hotplug to manage such permissions (in > kdebase tarball: kcontrol/input/consoleUserPerms and > kcontrol/input/logitechmouse.usermap); these files should be moved > in /etc/hotplug/usb to actually change file permissions on mouse > plugging. As debian does not use pam_console by default, however > consoleUserPerms should be modified to detect user not using console lock > file. Add the attached files to /etc/hotplug/usb, owned by root, with permissions of 644 for logitechmouse.usermap, and 755 for logitechmouse. Then do "/etc/init.d/hotplug force-reload", and add your user to the plugdev group if they're not already in it. The Logitech config screen should now be available. If this works (let me know), then I will add these files to the KDE packaging. Cheers, Christopher Martin logitechmouse Description: application/shellscript # script match_flags idVendor idProduct bcdDevice_lo bcdDevice_hi bDeviceClass bDeviceSubClass bDeviceProtocol bInterfaceClass bInterfaceSubClass bInterfaceProtocol driver_info # Wheel Mouse Optical logitechmouse 0x0003 0x046d 0xc00e0x 0x 0x00 0x000x000x000x00 0x00 0x # MouseMan Traveler logitechmouse 0x0003 0x046d 0xc00f0x 0x 0x00 0x000x000x000x00 0x00 0x # MouseMan Dual Optical logitechmouse 0x0003 0x046d 0xc0120x 0x 0x00 0x000x000x000x00 0x00 0x # MX310 Optical Mouse logitechmouse 0x0003 0x046d 0xc01b0x 0x 0x00 0x000x000x000x00 0x00 0x # MX510 Optical Mouse logitechmouse 0x0003 0x046d 0xc01d0x 0x 0x00 0x000x000x000x00 0x00 0x # MX300 Optical Mouse logitechmouse 0x0003 0x046d 0xc0240x 0x 0x00 0x000x000x000x00 0x00 0x # MX500 Optical Mouse logitechmouse 0x0003 0x046d 0xc0250x 0x 0x00 0x000x000x000x00 0x00 0x # iFeel Mouse logitechmouse 0x0003 0x046d 0xc0310x 0x 0x00 0x000x000x000x00 0x00 0x # Mouse Receiver logitechmouse 0x0003 0x046d 0xc5010x 0x 0x00 0x000x000x000x00 0x00 0x # Dual Receiver logitechmouse 0x0003 0x046d 0xc5020x 0x 0x00 0x000x000x000x00 0x00 0x # Cordless Freedom Optical logitechmouse 0x0003 0x046d 0xc5040x 0x 0x00 0x000x000x000x00 0x00 0x # Cordless Elite Duo logitechmouse 0x0003 0x046d 0xc5050x 0x 0x00 0x000x000x000x00 0x00 0x # MX700 Optical Mouse logitechmouse 0x0003 0x046d 0xc5060x 0x 0x00 0x000x000x000x00 0x00 0x # Cordless Optical Trackman logitechmouse 0x0003 0x046d 0xc508
Bug#294267: Me too.
I’m experiencing the same problem – exact same symptoms. I have a similar setup to [EMAIL PROTECTED]. I’m booting using PXE and an initrd. My root file system is a normal “unstable” install mounted over nfs. Thanks, Mathew Johnston
Bug#297861: Fwd: #99535
tags 297861 patch thanks - Forwarded message - Subject: #99535 Date: Monday, 21. March 2005 13:15 From: Will Stephenson <[EMAIL PROTECTED]> To: Daniel Molkentin <[EMAIL PROTECTED]> This patch disables Kopete from handling RTF format messages in ICQ, preventing the bug in the RTF parser from manifesting. Apply to kdenetwork/kopete/protocols/oscar/oscarsocket/oscarsocket.cpp HTH Will -- Will Stephenson IRC: Bille --- --- oscarsocket.cpp~2004-07-27 02:38:34.0 +0100 +++ oscarsocket.cpp 2005-03-19 19:19:27.0 + @@ -1523,11 +1523,11 @@ if (mIsICQ) { - capBuf.addString(oscar_caps[CAP_ICQSERVERRELAY], 16); // we support type-2 messages + //capBuf.addString(oscar_caps[CAP_ICQSERVERRELAY], 16); // we support type-2 messages capBuf.addString(oscar_caps[CAP_UTF8], 16); // we can send/receive UTF encoded messages capBuf.addString(oscar_caps[CAP_ISICQ], 16); // I think this is an icq client, but maybe I'm wrong capBuf.addString(oscar_caps[CAP_KOPETE], 16); // we are the borg, resistance is futile - capBuf.addString(oscar_caps[CAP_RTFMSGS], 16); // we do incoming RTF messages + //capBuf.addString(oscar_caps[CAP_RTFMSGS], 16); // we do incoming RTF messages capBuf.addString(oscar_caps[CAP_TYPING], 16); // we can send/receive typing notifications } else - End forwarded message - -- Violence in reality is quite different from theory. -- Spock, "The Cloud Minders", stardate 5818.4 signature.asc Description: Digital signature
Processed: Fwd: #99535
Processing commands for [EMAIL PROTECTED]: > tags 297861 patch Bug#297861: Kopete crashes on incoming icq message from icq5 user Tags were: security Bug#295265: kopete: Crashes with new ICQ-version Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#301001: kmail: freezes sometimes
Package: kmail Version: 4:3.3.2-0pre1 Severity: important KMail sometimes hangs for a certain amount of time (maybe about 30 seconds but it's possible that I err here). I think, this problem started after upgrading to this very version. The freezes happen in various situations - when sending an e-mail, when scrolling through a mail message in the main window, etc., etc. KMail doesn't crash, it's just that I have to wait for a rather long time until KMail continuous to work as expected again. I don't know what other information to provide at the moment. If you want more, please tell me exactly what information you want and how to provide it. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.7-pike Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kmail depends on: ii kdelibs4 4:3.3.2-1 KDE core libraries ii libc62.3.2.ds1-20GNU C Library: Shared libraries an ii libgcc1 1:3.4.3-6 GCC support library ii libice6 4.3.0.dfsg.1-10 Inter-Client Exchange library ii libkcal2a4:3.3.2-0pre1 KDE calendaring library ii libkdenetwork2 4:3.3.2-0pre1 KDE Network library ii libkdepim1 4:3.3.2-0pre1 KDE PIM library ii libkleopatra0a 4:3.3.2-0pre1 KDE GnuPG interface libraries ii libkpimidentities1 4:3.3.2-0pre1 KDE PIM user identity information ii libksieve0 4:3.3.2-0pre1 KDE mail/news message filtering li ii libmimelib1a 4:3.3.2-0pre1 KDE mime library ii libpng12-0 1.2.8rel-1 PNG library - runtime ii libqt3c102-mt3:3.3.3-8 Qt GUI Library (Threaded runtime v ii libsm6 4.3.0.dfsg.1-10 X Window System Session Management ii libstdc++5 1:3.3.5-8 The GNU Standard C++ Library v3 ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-10 X Window System miscellaneous exte ii perl 5.8.4-6 Larry Wall's Practical Extraction ii xlibs4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu ii zlib1g 1:1.2.2-3 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]