Bug 8157 - unknow error in mm -> juicy incidents
Summary: unknow error in mm -> juicy incidents
Alias: None
Product: Other
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: other_other
Depends on:
Reported: 2007-03-08 22:32 UTC by Oliver Pinter
Modified: 2007-04-09 16:24 UTC (History)
5 users (show)

See Also:
Kernel Version: 2.6.21-rc[123]
Regression: ---
Bisected commit-id:


Description Oliver Pinter 2007-03-08 22:32:40 UTC
Most recent kernel where this bug did *NOT* occur: <= 2.6.20-.1
Distribution: debian 4.0
Hardware Environment: asus p4c800 p4ht(northwood) R9600 
Software Environment: gcc-4.1 Xorg 7.0
Problem Description: more X erros and unrannable programs

Steps to reproduce:

1. start gdm
2. start kde-3.5.5
3  start amarok or other multimedia program
4. wait ~2hours
5. crashed the kde-enviroment
Comment 1 Diego Calleja 2007-03-09 13:27:22 UTC
Is there any error message left in your dmesg after crashing kde? This looks
like a kde bug
Comment 2 Oliver Pinter 2007-03-09 22:38:56 UTC
I think, that is a kde bug, but under <= functionirt.
dmesg is all ok, 
Comment 3 Olaf Kirch 2007-03-27 04:13:33 UTC
Can you please provide more information on what stops working, and
the symptoms?

What are the symptoms of "KDE environment crashes"? Do applications
segfault? The X server? Are there any messages in ~/.xsession-errors?
As far as I understand, this is not a kernel crash, right?
Comment 4 Eric W. Biederman 2007-04-02 18:25:02 UTC
There is a signal handling bug, before 2.6.21-rc6 that has caused similar KDE
problems does running Linus latest tree cause this to go away?

Comment 5 Adrian Bunk 2007-04-09 16:24:04 UTC
Eric W. Biederman:
Oliver reports the problem not recurring after updating to 2.6.21-rc5-git7.

Note You need to log in before you can comment on or make changes to this bug.