Version-Release number of selected component: kde-workspace-4.10.1-2.fc18 Additional info: backtrace_rating: 4 cmdline: kblankscrn.kss -window-id 75497540 crash_function: qt_message_output executable: /usr/bin/kblankscrn.kss kernel: 3.8.4-202.fc18.x86_64 uid: 1000 ureports_counter: 1 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
Created attachment 731705 [details] File: backtrace
Created attachment 731706 [details] File: cgroup
Created attachment 731707 [details] File: core_backtrace
Created attachment 731708 [details] File: dso_list
Created attachment 731709 [details] File: environ
Created attachment 731710 [details] File: limits
Created attachment 731711 [details] File: maps
Created attachment 731712 [details] File: open_fds
Created attachment 731713 [details] File: proc_pid_status
Created attachment 731714 [details] File: var_log_messages
Created attachment 731715 [details] File: xsession_errors
It crashed on resume, and the screen was not locked as it normally is. backtrace_rating: 4 cmdline: kblankscrn.kss -window-id 109051946 crash_function: qt_message_output executable: /usr/bin/kblankscrn.kss kernel: 3.8.5-201.fc18.x86_64 package: kde-workspace-4.10.1-2.fc18 reason: Process /usr/bin/kblankscrn.kss was killed by signal 6 (SIGABRT) uid: 1201 ureports_counter: 1 xsession_errors: kblankscrn.kss(24906): Got X error after loss of parent process. Terminating.
just happened to me. didnt notice the screensaver doing anything as i was using the box. all of a sudden a failure popped up
Still current on F19 as per duplicate.
*** Bug 1009770 has been marked as a duplicate of this bug. ***
1. Install FC19, KDE, current updates (this have been happening for a long time though). Note: this wasn't happening before I've installed NVidia drivers and not for a while afterwards either. 2. The boot sequence will continue until the point when a graphical login interface is supposed to appear. 3. The screen will go blank (a graphic mode) but then it (the graphic mode) will fail and the boot log will appear again. 4. Press ctrl+alt+f2, log in in the text mode and use startx 5. The KDE workspace will appear -> The kblankscrn.kss warning will appear in abrt reporter: libreport-2.1.8 backtrace_rating: 4 cmdline: kblankscrn.kss -window-id 79691828 crash_function: qt_message_output executable: /usr/bin/kblankscrn.kss kernel: 3.11.6-200.fc19.x86_64 package: kde-workspace-4.11.2-1.fc19 reason: Process /usr/bin/kblankscrn.kss was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp
Another user experienced a similar problem: Unknown how problem occurred. My default screen saver is blank screen and the crash was reported when the screen saver was not 'on'. reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: kblankscrn.kss -window-id 94371934 crash_function: qt_message_output executable: /usr/bin/kblankscrn.kss kernel: 3.13.9-100.fc19.x86_64 package: kde-workspace-4.11.8-1.fc19 reason: kblankscrn.kss killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.