Bug 590128 - [abrt] crash in gnome-screensaver-2.30.0-1.fc13: raise: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnome-screensaver-2.30.0-1.fc13: raise: Process /usr/libexec/...
Keywords:
Status: CLOSED DUPLICATE of bug 562829
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-screensaver
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: jmccann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:94ff7d770364b18065f7cf93e9c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-07 19:15 UTC by Stephane Gauthier
Modified: 2015-01-14 23:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:36:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (20.08 KB, text/plain)
2010-05-07 19:15 UTC, Stephane Gauthier
no flags Details

Description Stephane Gauthier 2010-05-07 19:15:57 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gnome-screensaver-dialog --status-message= --enable-switch
component: gnome-screensaver
crash_function: raise
executable: /usr/libexec/gnome-screensaver-dialog
global_uuid: 94ff7d770364b18065f7cf93e9ca28cee9da8992
kernel: 2.6.33.3-72.fc13.x86_64
package: gnome-screensaver-2.30.0-1.fc13
rating: 4
reason: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

Comment 1 Stephane Gauthier 2010-05-07 19:15:59 UTC
Created attachment 412428 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 09:36:17 UTC

*** This bug has been marked as a duplicate of bug 562829 ***

Comment 3 Karel Klíč 2010-05-25 09:36:17 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #562829.

Sorry for the inconvenience.


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