Bug 867648

Summary: [abrt] soundconverter-2.0.3-5.fc17: gstreamer.py:58:<module>:GError: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down.
Product: [Fedora] Fedora Reporter: david <david.airbus>
Component: soundconverterAssignee: Xavier Lamien <lxtnow>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: bugs.michael, lxtnow
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6794dcdef4e26c178dd325ebcb18d93417fb6765
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-18 08:18:58 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
File: core_backtrace none

Description david 2012-10-17 23:33:10 UTC
Description of problem:
after install some nautilus extensions among others "convert audio files" soundconverter stop working

Version-Release number of selected component:
soundconverter-2.0.3-5.fc17

Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
cmdline:        /usr/bin/python /usr/bin/soundconverter
kernel:         3.6.1-1.fc17.x86_64

Comment 1 david 2012-10-17 23:33:12 UTC
Created attachment 629118 [details]
File: backtrace

Comment 2 david 2012-10-17 23:33:14 UTC
Created attachment 629119 [details]
File: core_backtrace

Comment 3 Michael Schwendt 2012-10-18 08:18:58 UTC
Searching bugzilla for the error message would have turned up something affecting lots of apps:

| GError: Configuration server couldn't be contacted:
| D-BUS error: The GConf daemon is currently shutting down.

I don't think it's SoundConverter's responsibility to handle that gracefully and sleep'n'retry after some time.  -> bug 756245

There's a test update there. Give it a try, please!

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