Description of problem: To reproduce the problem just lock screen and then login. This problems is present after update on 21 march 2013. I use shortcut to lock screen (meta + s). Before update i used kscreenlocker to lock screen, after update this program was removed. Version-Release number of selected component: kdeartwork-screensavers-4.10.1-1.fc17 Additional info: backtrace_rating: 4 cmdline: kslideshow.kss -window-id 111149124 crash_function: qt_message_output executable: /usr/bin/kslideshow.kss kernel: 3.7.9-104.fc17.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #6 qt_message_output at global/qglobal.cpp:2323 #7 ~QDebug at /usr/include/QtCore/qdebug.h:85 #8 xErrorHandler at /usr/src/debug/kde-workspace-4.10.1/kscreensaver/libkscreensaver/main.cpp:120 #10 handle_error at xcb_io.c:212 #11 handle_response at xcb_io.c:324 #13 _XGetWindowAttributes at GetWAttrs.c:114 #14 XGetWindowAttributes at GetWAttrs.c:149 #15 QWidgetPrivate::create_sys at kernel/qwidget_x11.cpp:591 #16 QWidget::create at kernel/qwidget.cpp:1515 #17 KScreenSaver::KScreenSaver at /usr/src/debug/kde-workspace-4.10.1/kscreensaver/libkscreensaver/kscreensaver.cpp:44 Potential duplicate: bug 922975
Created attachment 714345 [details] File: backtrace
Created attachment 714346 [details] File: cgroup
Created attachment 714347 [details] File: core_backtrace
Created attachment 714348 [details] File: dso_list
Created attachment 714349 [details] File: environ
Created attachment 714350 [details] File: limits
Created attachment 714351 [details] File: maps
Created attachment 714352 [details] File: open_fds
Created attachment 714353 [details] File: proc_pid_status
Created attachment 714354 [details] File: smolt_data
Created attachment 714355 [details] File: var_log_messages
Crashes when screen saver exits. Started occuring with the recent software upgrade the supported different 'random' screen savers on each physical monitor. backtrace_rating: 4 cmdline: klines.kss -window-id 50331739 crash_function: qt_message_output executable: /usr/bin/klines.kss kernel: 3.7.9-104.fc17.i686.PAE package: kdeartwork-screensavers-4.10.1-1.fc17 reason: Process /usr/bin/klines.kss was killed by signal 6 (SIGABRT) uid: 1001 ureports_counter: 2
The problem happens everytime my screensaver closes. backtrace_rating: 4 cmdline: kfountain.kss -window-id 83886148 crash_function: qt_message_output executable: /usr/bin/kfountain.kss kernel: 3.8.3-103.fc17.x86_64 package: kdeartwork-screensavers-4.10.1-1.fc17 reason: Process /usr/bin/kfountain.kss was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 1 xsession_errors: kfountain.kss(19153): Got X error after loss of parent process. Terminating.
After moving the mouse to quit the screensaver, it says that kslideshow has been killed by signal 6, it aint a problem for me, it just makes the automatic bug report tool appear. backtrace_rating: 4 cmdline: kslideshow.kss -window-id 37748788 crash_function: qt_message_output executable: /usr/bin/kslideshow.kss kernel: 3.8.4-102.fc17.x86_64 package: kdeartwork-screensavers-4.10.2-1.fc17 reason: Process /usr/bin/kslideshow.kss was killed by signal 6 (SIGABRT) uid: 1000 ureports_counter: 1 xsession_errors: kslideshow.kss(9856): Got X error after loss of parent process. Terminating.
I believe this crash occured after bringing the laptop back from sleep mode. backtrace_rating: 4 cmdline: kdeasciiquarium.kss -window-id 27263018 crash_function: qt_message_output executable: /usr/bin/kdeasciiquarium.kss kernel: 3.8.4-102.fc17.x86_64 package: kdeartwork-screensavers-4.10.1-1.fc17 reason: Process /usr/bin/kdeasciiquarium.kss was killed by signal 6 (SIGABRT) reported_to: uReport: BTHASH=9711aae6e8a65d35597da25083067500a11640e2 uid: 1000 ureports_counter: 1 xsession_errors: kdeasciiquarium.kss(23684): Got X error after loss of parent process. Terminating.
It seems to me the "error" message is accurate - it seems reasonable that the screensaver process would be killed using a SIGABRT. Nonetheless it's annoying to have to deal with a bug alert everytime one resumes work (especially since this introduces ANOTHER interruption). Any suggestions on how to get this to NOT issue a bug alert?
> it seems reasonable that the screensaver process would be killed using a SIGABRT. No. A SIGABRT is always a bug (abort(), assertion failure, uncaught C++ exception or similar; in this case, a qFatal is being triggered in the code). Killing a process normally uses SIGTERM, not SIGABRT.
Happens regularly when deactivating screensaver backtrace_rating: 4 cmdline: keuphoria.kss -window-id 109051956 crash_function: qt_message_output executable: /usr/bin/keuphoria.kss kernel: 3.8.13-100.fc17.x86_64 last_occurrence: 1371586419 package: kdeartwork-screensavers-4.10.4-1.fc17 reason: Process /usr/bin/keuphoria.kss was killed by signal 6 (SIGABRT) runlevel: unknown uid: 500 ureports_counter: 1 xsession_errors: keuphoria.kss(28985): Got X error after loss of parent process. Terminating.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.