Bug 581795

Summary: [abrt] crash in emerald-0.8.4-3.fc13: Process /usr/bin/emerald-theme-manager was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: leon Cogs <leoncogs>
Component: emeraldAssignee: leigh scott <leigh123linux>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: adam, antvick.monher, extras-orphan, lgraves, maycon.franca
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:1edd72a4570c0c7cca962728f21626f692d93184
Fixed In Version: emerald-0.8.4-4.fc13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-17 19:03:09 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 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.