Bug#595483: kde: KDE4 Crashes system
I believe this bug report can be closed. I've upgraded two systems to the stable release, and both have been up for more than 24 hours without a failure. One system has been up nearly 3 days. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595483: kde: KDE4 Crashes system
Package: kde Version: KDE4 Severity: critical Justification: breaks the whole system KDE4 invariably crashes the system. This system is running on an AMD Athlon 64 x 2 processer under Debian Squeeze and kernel 2.6.32-3-amd64. The same symptoms (only worse) are also observed on a Pentium IV system running 2.6.32-trunk-686. One can log in via kdm and bring up KDE4, but sooner or later - usually within an hour or two, the system will crash hard. One then cannot reach the system via telnet, XDMCP, or from the console. Often, it will not even reply to pings. The only option is to hit the power switch. If no KDE session is active, both machines are 100% stable, up continuously for months at a time without issues. If a KDE4 session is active, then after between 30 minutes and 24 hours, the system will crash. No activity is required on the KDE session for the failure to occur, but it seems that changing window foocus often triggers an event. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kde depends on: pn kde-core none (no description available) pn kdeaccessibility none (no description available) pn kdeaddons none (no description available) pn kdeadmin none (no description available) pn kdeartworknone (no description available) pn kdeedunone (no description available) pn kdegames none (no description available) pn kdegraphics none (no description available) pn kdemultimedia none (no description available) pn kdenetworknone (no description available) pn kdepimnone (no description available) pn kdetoys none (no description available) pn kdeutils none (no description available) pn kdewebdev none (no description available) kde recommends no packages. Versions of packages kde suggests: pn kde-i18n none (no description available) pn x-window-system-core none (no description available) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595483: kde: KDE4 Crashes system
severity 595483 normal thanks On Sat, Sep 4, 2010 at 2:46 PM, lrhorer lrho...@fletchergeek.com wrote: Package: kde Version: KDE4 Severity: critical Justification: breaks the whole system KDE4 invariably crashes the system. This system is running on an AMD Athlon 64 x 2 processer under Debian Squeeze and kernel 2.6.32-3-amd64. The same symptoms (only worse) are also observed on a Pentium IV system running 2.6.32-trunk-686. One can log in via kdm and bring up KDE4, but sooner or later - usually within an hour or two, the system will crash hard. One then cannot reach the system via telnet, XDMCP, or from the console. Often, it will not even reply to pings. The only option is to hit the power switch. If no KDE session is active, both machines are 100% stable, up continuously for months at a time without issues. If a KDE4 session is active, then after between 30 minutes and 24 hours, the system will crash. No activity is required on the KDE session for the failure to occur, but it seems that changing window foocus often triggers an event. This is most likely due to a faulty gpu driver. I guess you are using amd's proprietary fglrx driver? I have seen such issues in the past with this driver. KDE has no way to lock the system, if a system lock happens this is a problem deep in the kernel or some of its modules. Btw, both of these kernels that you are using are out-of-date. The latest squeeze kernel is 2.6.32-5-amd64. I advise you to upgrade to this kernel and uninstall any proprietary graphics drivers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595483: kde: KDE4 Crashes system
-Original Message- From: George Kiagiadakis [mailto:kiagiadakis.geo...@gmail.com] Sent: Saturday, September 04, 2010 7:06 AM To: lrhorer; 595...@bugs.debian.org Cc: cont...@bugs.debian.org Subject: Re: Bug#595483: kde: KDE4 Crashes system severity 595483 normal thanks On Sat, Sep 4, 2010 at 2:46 PM, lrhorer lrho...@fletchergeek.com wrote: Package: kde Version: KDE4 Severity: critical Justification: breaks the whole system KDE4 invariably crashes the system. This system is running on an AMD Athlon 64 x 2 processer under Debian Squeeze and kernel 2.6.32-3-amd64. The same symptoms (only worse) are also observed on a Pentium IV system running 2.6.32-trunk-686. One can log in via kdm and bring up KDE4, but sooner or later - usually within an hour or two, the system will crash hard. One then cannot reach the system via telnet, XDMCP, or from the console. Often, it will not even reply to pings. The only option is to hit the power switch. If no KDE session is active, both machines are 100% stable, up continuously for months at a time without issues. If a KDE4 session is active, then after between 30 minutes and 24 hours, the system will crash. No activity is required on the KDE session for the failure to occur, but it seems that changing window foocus often triggers an event. This is most likely due to a faulty gpu driver. I guess you are using amd's proprietary fglrx driver? I have seen such issues in the past with this driver. KDE has no way to lock the system, if a system lock happens this is a problem deep in the kernel or some of its modules. Btw, both of these kernels that you are using are out-of-date. The latest squeeze kernel is 2.6.32-5-amd64. I advise you to upgrade to this kernel and uninstall any proprietary graphics drivers. A normal severity for a bug that causes the system to be completely unusable when the package is in use? That locks up the system like Fort Knox? That causes data loss if any files are still open? I'm hard pressed to think of a more severe problem. There are no proprietary gpu drivers, and please re-read the post. One of the systems is Intel. Both systems were upgraded from Debian Lenny with no problems whatsoever running KDE3. Neither has any problem running gnome. KDE4 was so unusable on the Pentium system I wiped the drive and installed fresh from the Squeeze installer. It didn't help. Both use the graphics processors embedded on the motherboard, with plain-vanilla Debian installations straight from the Debian install CD. The Pentium system is an old Dell Optiplex GX-1 system, which is about as Plain Jane Intel as it gets. The AMD is over a year old. All of the software on both machines - other than that I have written myself - is straight from the Debian repositories. I'll try upgrading the kernel on the AMD system. The Pentium is not local to me, and an upgrade failure would probably be unrecoverable. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-dist
Bug#595483: kde: KDE4 Crashes system
On Sat, Sep 4, 2010 at 3:32 PM, Leslie Rhorer lrho...@fletchergeek.com wrote: A normal severity for a bug that causes the system to be completely unusable when the package is in use? That locks up the system like Fort Knox? That causes data loss if any files are still open? I'm hard pressed to think of a more severe problem. It is a serious problem, but it is not related to the 'kde' package where you reported it. The 'kde' package is a metapackage from lenny and does not even exist in squeeze. The most likely cause of the bug is the kernel, so this bug should eventually be reasigned there and have its severity raised, however I cannot do that until the problem has been fully identified. There are no proprietary gpu drivers, and please re-read the post. One of the systems is Intel. Both systems were upgraded from Debian Lenny with no problems whatsoever running KDE3. Neither has any problem running gnome. KDE4 was so unusable on the Pentium system I wiped the drive and installed fresh from the Squeeze installer. It didn't help. Both use the graphics processors embedded on the motherboard, with plain-vanilla Debian installations straight from the Debian install CD. The Pentium system is an old Dell Optiplex GX-1 system, which is about as Plain Jane Intel as it gets. The AMD is over a year old. All of the software on both machines - other than that I have written myself - is straight from the Debian repositories. An intel system can have an amd graphics card, this is not uncommon. I still believe the problem is in graphics drivers, though. Even if these are the free intel or radeon drivers. Radeon drivers are known to lock up if their non-free firmware is missing, perhaps you should make sure to install firmware-linux-nonfree and I'm not sure about the intel drivers (never had one of those). Anyway, the kernel upgrade may help, since the -5- version of this kernel has all the graphics drivers backported from 2.6.33. PS: Do not keep cont...@bugs.debian.org in CC, it will just send you back an email full of errors, since you are not following its syntax in the email (it is a bot). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595483: kde: KDE4 Crashes system
-Original Message- From: George Kiagiadakis [mailto:kiagiadakis.geo...@gmail.com] Sent: Saturday, September 04, 2010 7:48 AM To: Leslie Rhorer Cc: 595...@bugs.debian.org Subject: Re: Bug#595483: kde: KDE4 Crashes system On Sat, Sep 4, 2010 at 3:32 PM, Leslie Rhorer lrho...@fletchergeek.com wrote: A normal severity for a bug that causes the system to be completely unusable when the package is in use? That locks up the system like Fort Knox? That causes data loss if any files are still open? I'm hard pressed to think of a more severe problem. It is a serious problem, but it is not related to the 'kde' package where you reported it. The 'kde' package is a metapackage from lenny and does not even exist in squeeze. The most likely cause of the bug is the kernel, so this bug should eventually be reasigned there and have its severity raised, however I cannot do that until the problem has been fully identified. OK. There are no proprietary gpu drivers, and please re-read the post. One of the systems is Intel. Both systems were upgraded from Debian Lenny with no problems whatsoever running KDE3. Neither has any problem running gnome. KDE4 was so unusable on the Pentium system I wiped the drive and installed fresh from the Squeeze installer. It didn't help. Both use the graphics processors embedded on the motherboard, with plain-vanilla Debian installations straight from the Debian install CD. The Pentium system is an old Dell Optiplex GX-1 system, which is about as Plain Jane Intel as it gets. The AMD is over a year old. All of the software on both machines - other than that I have written myself - is straight from the Debian repositories. An intel system can have an amd graphics card, this is not uncommon. I As I said, neither has a graphics card, and I certainly have never seen an Intel motherboard with an AMD GPU. I would think the execs at Intel would rather have their nards shredded than use an AMD product on one of their motherboards. Come to think of it, however, would the GPU or its drivers even have any effect on XDMCP? I'm not an expert on X11, but I don't think X11 makes use of any local GPU resources - hardware or software - when the X-server is remote, does it? That, along with the fact the GPUs are as different as can be would seem to tend to eliminate the GPUs or their drivers as the source of the issue. That said, on a note related to the Intel GPU, I did have to disable the i915 modeset in /etc/modeprobe.d/i915-kms.conf on the Pentium system or else it would not boot without a monitor. As I recall, the video driver installed by Debian is xserver-xorg-video-intel. (Oh, BTW, I mis-spoke a bit: It's a GX-260, not a GX-1.) On what I don't think is a related note - but could be - KDM does not come up on the console of the AMD machine. The console never switches to the graphical interface. I'm not sure why, but since I never use the console, I really haven't worried about it. I don't recall exactly when this broke. I don't think it was during the upgrade to Squeeze / KDE4, but I could be mistaken. It definitely worked under Lenny, however. still believe the problem is in graphics drivers, though. Even if these are the free intel or radeon drivers. Radeon drivers are known to lock up if their non-free firmware is missing, perhaps you should make sure to install firmware-linux-nonfree and I'm not sure about the I don't follow. The embedded controller on the Asus MB is a Radeon HD 3200, though. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-dist
