Bug 8157

Summary:	unknow error in mm -> juicy incidents
Product:	Other	Reporter:	Oliver Pinter (oliver.pntr)
Component:	Other	Assignee:	other_other
Status:	CLOSED PATCH_ALREADY_AVAILABLE
Severity:	normal	CC:	akpm, bunk, diegocg, ebiederm, okir
Priority:	P2
Hardware:	i386
OS:	Linux
Kernel Version:	2.6.21-rc[123]	Subsystem:
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 <=2.6.20.1 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?

Eric

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.