Bug 592682 - [abrt] crash in gnome-screensaver-2.28.3-1.fc12: main: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 11 (SIGSEGV)
[abrt] crash in gnome-screensaver-2.28.3-1.fc12: main: Process /usr/libexec/g...
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: gnome-screensaver (Show other bugs)
12
i686 Linux
low Severity medium
: ---
: ---
Assigned To: jmccann
Fedora Extras Quality Assurance
abrt_hash:d73d3aedfffed76976164d773af...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-16 04:59 EDT by Jayrome
Modified: 2015-01-14 18:25 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-09-18 07:19:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
File: backtrace (13.20 KB, text/plain)
2010-05-16 04:59 EDT, Jayrome
no flags Details

  None (edit)
Description Jayrome 2010-05-16 04:59:47 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gnome-screensaver-dialog --status-message= --enable-switch
comment: returned to netbook with its screen blocked (by GNOME). The Empty Screen screensaver was running blocking the screen and only showing the screen without windows when the cursor moved on the touchpad or with mouse and continuing to go blanking the screen as soon as the cursor stopped. The login window failed to appear.
component: gnome-screensaver
crash_function: main
executable: /usr/libexec/gnome-screensaver-dialog
global_uuid: d73d3aedfffed76976164d773af210aeb9c5c3e9
kernel: 2.6.32.11-99.fc12.i686
package: gnome-screensaver-2.28.3-1.fc12
rating: 4
reason: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Jayrome 2010-05-16 04:59:57 EDT
Created attachment 414325 [details]
File: backtrace

Note You need to log in before you can comment on or make changes to this bug.