Bug 615918 - [abrt] crash in gnome-settings-daemon-2.30.1-7.fc13: convert_clipboard: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-settings-daemon-2.30.1-7.fc13: convert_clipboard: Proce...
Keywords:
Status: CLOSED DUPLICATE of bug 615487
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d836a20fb1ec05647128f2e14f9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-19 09:29 UTC by Mark van Rossum
Modified: 2010-11-08 19:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 19:03:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (51.33 KB, text/plain)
2010-07-19 09:29 UTC, Mark van Rossum
no flags Details

Description Mark van Rossum 2010-07-19 09:29:40 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gnome-settings-daemon
comment: Random crash, I was not doing anything in particulat.
component: gnome-settings-daemon
crash_function: convert_clipboard
executable: /usr/libexec/gnome-settings-daemon
global_uuid: d836a20fb1ec05647128f2e14f9002e708fa467a
kernel: 2.6.33.6-147.fc13.i686.PAE
package: gnome-settings-daemon-2.30.1-7.fc13
rating: 4
reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 Mark van Rossum 2010-07-19 09:29:42 UTC
Created attachment 432805 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 19:03:18 UTC

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

Comment 3 Karel Klíč 2010-11-08 19:03:18 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 #615487.

Sorry for the inconvenience.


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