Bug 660004

Summary: [abrt] xfdesktop-4.6.2-2.fc14.1: __libc_message: Process /usr/bin/xfdesktop-settings was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Barry Godusky <bgodusky>
Component: xfdesktopAssignee: Kevin Fenzi <kevin>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: kevin
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:32e290c18f9a78a9767995ff24817559629377b2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 19:43:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Barry Godusky 2010-12-04 23:24:36 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/xfdesktop-settings
component: xfdesktop
crash_function: __libc_message
executable: /usr/bin/xfdesktop-settings
kernel: 2.6.35.6-48.fc14.i686
package: xfdesktop-4.6.2-2.fc14.1
rating: 4
reason: Process /usr/bin/xfdesktop-settings was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1291330541
uid: 501

How to reproduce
-----
1.
2.
3.Just happens every now and then after system updates have been applied
Comment 1 Barry Godusky 2010-12-04 23:24:39 UTC 
Created attachment 464783 [details]
File: backtrace
Comment 2 Kevin Fenzi 2010-12-04 23:31:31 UTC 
Interesting. Can you also provide: 

dmesg

and

~/.xsession-errors 

Also, what updates were applied?
Comment 3 Barry Godusky 2010-12-04 23:54:43 UTC 
Oops sorry this is not the right occurrence. This happens when changing settings in xfdesktop-setting. Meaning I was changing something when it happened and I have no idea since this crash happened at the end of last month. It has been reported at least 2 times already but with a different exit code each time. I think if you search through my bug reports you will find them and that may give you a better idea what is going on.
Comment 4 abrt-bot 2012-03-20 19:43:56 UTC 
Backtrace analysis found this bug to be similar to bug #773044, closing as duplicate. This bug seems to belong to component gtk2, glib2 or glibc.

Bugs which were found to be similar to this bug: 
  audacious: bug #723416
  backintime: bug #734973
  clamtk: bug #722643
  file-roller: bug #649206
  gnome-utils: bug #666691
  gtk2: bug #753978, bug #771659
  inkscape: bug #785087
  keepassx: bug #717570
  openoffice.org: bug #664483
  perl-Gtk2: bug #773044
  pitivi: bug #713884
  rhythmbox: bug #675318
  totem: bug #666243
  transmission: bug #711042
  virt-manager: bug #723422
  xnoise: bug #789531

This comment is automatically generated.

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