Bug 581795 - [abrt] crash in emerald-0.8.4-3.fc13: Process /usr/bin/emerald-theme-manager was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in emerald-0.8.4-3.fc13: Process /usr/bin/emerald-theme-manager ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: emerald
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: leigh scott
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1edd72a4570c0c7cca962728f21...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-13 09:09 UTC by leon Cogs
Modified: 2010-05-17 19:03 UTC (History)
5 users (show)

Fixed In Version: emerald-0.8.4-4.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-17 19:03:09 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (14.45 KB, text/plain)
2010-04-13 09:09 UTC, leon Cogs 		no flags Details
View All

Description leon Cogs 2010-04-13 09:09:24 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/emerald-theme-manager -i
component: emerald
executable: /usr/bin/emerald-theme-manager
global_uuid: 1edd72a4570c0c7cca962728f21626f692d93184
kernel: 2.6.33.1-24.fc13.x86_64
package: emerald-0.8.4-3.fc13
rating: 4
reason: Process /usr/bin/emerald-theme-manager was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 leon Cogs 2010-04-13 09:09:27 UTC 
Created attachment 406181 [details]
File: backtrace
Comment 2 Fedora Admin XMLRPC Client 2010-05-16 15:23:51 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Fedora Update System 2010-05-16 16:44:10 UTC 
emerald-0.8.4-4.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/emerald-0.8.4-4.fc13
Comment 4 Fedora Update System 2010-05-17 19:02:43 UTC 
emerald-0.8.4-4.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.