Description of problem: KDE terminates without prior warning and in various situations, often at times when the user triggered no particular action. Inspection of /var/log/messages after such a termination that had occured at about 17:25 revealed the following final messages ("diogenes" is the hostname): May 30 17:24:41 diogenes abrt[25645]: saved core dump of pid 13941 (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2011-05-30-17:24:37-13941.new/coredump (59150336 bytes) May 30 17:24:41 diogenes abrtd: Directory 'ccpp-2011-05-30-17:24:37-13941' creation detected May 30 17:24:42 diogenes kdm[1227]: X server for display :0 terminated unexpectedly May 30 17:24:49 diogenes abrtd: New dump directory /var/spool/abrt/ccpp-2011-05-30-17:24:37-13941, processing May 30 17:24:54 diogenes dbus: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) May 30 17:24:54 diogenes dbus: [system] Successfully activated service 'net.reactivated.Fprint' This indicates that ccpp had crashed and the X server terminated when abrt tried to report the core cump. Note that the abrt message never appeared on screen. Version-Release number of selected component (if applicable): This is Fedora 15 on x86_x64 with all updates installed as of 30th May 2011. Specifically: cups 1.4.6-15.fc15 abrt 2.0.2-5.fc15 kdm 4.6.3-5.fc15 kdebase-workspace 4.6.3-5.fc15 How reproducible: For me, reproducing this is a matter of starting up KDE and waiting a while without doing much. The problem does not occur extremely frequently (today it occurred twice in about 6 hours). I am unsure whether this is only triggered by crashes of ccpp or also other programs. Nor do I do why ccpp crashes in the first place. Until recently I was running F14, but the x86 (not 64 bit) version of the kernel. This problem had never occurred. Additional info: This might or might not be related to https://bugzilla.redhat.com/show_bug.cgi?id=653708
This has nothing to do with cups, although that is what I believed at first. It is in fact the same issue as bug #709091. I'll mark this one as duplicate. *** This bug has been marked as a duplicate of bug 709091 ***