Red Hat Bugzilla – Bug 697187
[abrt] gnome-screensaver-3.0.0-1.fc15: do_user_switch: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 11 (SIGSEGV)
Last modified: 2012-03-21 11:52:47 EDT
abrt version: 2.0.0
cmdline: /usr/libexec/gnome-screensaver-dialog --status-message= --enable-switch
reason: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 11 (SIGSEGV)
os_release: Fedora release 15 (Lovelock)
Text file: event_log, 25989 bytes
Text file: smaps, 118140 bytes
Text file: build_ids, 3936 bytes
Binary file: coredump, 27922432 bytes
Text file: dsos, 19002 bytes
Text file: maps, 20952 bytes
Text file: backtrace, 30952 bytes
Created attachment 492600 [details]
Created attachment 492601 [details]
Created attachment 492602 [details]
Created attachment 492603 [details]
Created attachment 492604 [details]
Created attachment 492605 [details]
OS Release: Fedora release 15 (Lovelock)
How to reproduce
Install of Fedora 12 upgraded to 15
Created attachment 505634 [details]
abrt log and backtrace
The following may be related and exists after a new install of F15.
Assume two users.
1. Log in as user1.
2. Switch to and log in as user2.
3. Lock screen as user2.
4. At screen saver dialog, switch user.
5. Log in as already logged in user1.
6. Log out user1.
7. Log in as already logged in user2.
Sometimes you may see a flash of the screen saver dialog just as login completes. Sometimes the gnome shell for user2 does not respond to input from keyboard or mouse. Sometimes you a black screen when logging out after the crash.
It occurs whether you lock the screen manually or allow it to time-out and lock.
I changed all my passwords that may be in the attached file.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Backtrace analysis found this bug to be similar to bug #698627, closing as duplicate.
Bugs which were found to be similar to this bug: bug #683771, bug #684515, bug #692612, bug #698627
This comment is automatically generated.
*** This bug has been marked as a duplicate of bug 698627 ***