[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#595483: kde: KDE4 Crashes system



> -----Original Message-----
> From: George Kiagiadakis [mailto:kiagiadakis.george@gmail.com]
> Sent: Saturday, September 04, 2010 7:06 AM
> To: lrhorer; 595483@bugs.debian.org
> Cc: control@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 <lrhorer@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.




Reply to: