Red Hat Bugzilla – Bug 998448
[abrt] gnome-screensaver-2.28.3-27.el6: find_usable_monitor: Process /usr/bin/gnome-screensaver was killed by signal 11 (SIGSEGV)
Last modified: 2014-01-02 04:04:48 EST
Description of problem:
automatic or user invoked start of scrensaver followed by poking screen after few seconds
user's workspace reamins unlocked!
Version-Release number of selected component:
libreport version: 2.0.9
cmdline: /usr/bin/gnome-screensaver --no-daemon
:Thread no. 1 (10 frames)
: #0 find_usable_monitor at gs-manager.c
: #1 find_window_at_usable_monitor at gs-manager.c
: #2 gs_manager_request_unlock at gs-manager.c
: #3 gs_marshal_BOOLEAN__VOID at gs-marshal.c
: #8 maybe_handle_activity at gs-window-x11.c
: #9 gs_window_real_motion_notify_event at gs-window-x11.c
: #10 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c
: #15 gtk_widget_event_internal at gtkwidget.c
: #16 IA__gtk_propagate_event at gtkmain.c
: #17 IA__gtk_main_do_event at gtkmain.c
Created attachment 787994 [details]
Created attachment 787995 [details]
Created attachment 787996 [details]
Created attachment 787997 [details]
Created attachment 787998 [details]
Created attachment 787999 [details]
Created attachment 788000 [details]
Created attachment 788001 [details]
Created attachment 788002 [details]
Created attachment 788003 [details]
Created attachment 788004 [details]
package gnome-screensaver-2.28.3-24 does run without this issue
I've tested the package -28 release in my environment, the bug seems to be fixed in it.
yes, in that setup it crashed every time it kicked in. either by gnome or by mentioned command. Blank screen appeared and after short while (<1s) it crashed, or crashed after moving by mouse.
I've already tested the bug in my previous environment, please see comment 14
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.