Bug 646758 - [abrt] gnome-screensaver-2.30.2-2.fc14: dbus_message_unref: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-screensaver-2.30.2-2.fc14: dbus_message_unref: Process /usr/libe...
Keywords:
Status: CLOSED DUPLICATE of bug 710892
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-screensaver
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f67cdd03a64fb0d649504578ca2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-26 07:17 UTC by Chris Underhill
Modified: 2012-03-20 17:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-20 17:06:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (24.06 KB, text/plain)
2010-10-26 07:17 UTC, Chris Underhill
no flags Details

Description Chris Underhill 2010-10-26 07:17:32 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gnome-screensaver-dialog --status-message= --enable-switch
comment: Screensaver crashed while pc was idle overnight
component: gnome-screensaver
crash_function: dbus_message_unref
executable: /usr/libexec/gnome-screensaver-dialog
kernel: 2.6.35.6-45.fc14.x86_64
package: gnome-screensaver-2.30.2-2.fc14
rating: 4
reason: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1288063741
uid: 500

Comment 1 Chris Underhill 2010-10-26 07:17:35 UTC
Created attachment 455700 [details]
File: backtrace

Comment 2 Fedora Admin XMLRPC Client 2011-06-21 15:58:53 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 abrt-bot 2012-03-20 17:06:59 UTC
Backtrace analysis found this bug to be similar to bug #710892, closing as duplicate.

This comment is automatically generated.

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


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