Bug 875449

Summary: [abrt] gnome-gmail-1.8.2-2.fc17: setOOmailer:197:should_set_oo_mailer:GError: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down.
Product: [Fedora] Fedora Reporter: Sergiu Niculescu <contact.sergiuniculescu>
Component: gnome-gmailAssignee: Guillaume Kulakowski <guillaume>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: guillaume
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8f2ff80b3b687a80f156a6031687e04521c5424f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 03:02:03 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: executable
none
File: environ
none
File: smolt_data
none
File: core_backtrace none

Description Sergiu Niculescu 2012-11-11 10:20:26 UTC 
Description of problem:
It's the classic problem with Gnome. After I run 'sudo killall gconfd-2', everything starts OK.

Version-Release number of selected component:
gnome-gmail-1.8.2-2.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
cmdline:        /usr/bin/python /usr/bin/setOOmailer
kernel:         3.6.6-1.fc17.x86_64

backtrace:
:setOOmailer:197:should_set_oo_mailer:GError: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down.
:
:Traceback (most recent call last):
:  File "/usr/bin/setOOmailer", line 214, in <module>
:    if( not should_set_oo_mailer() ):
:  File "/usr/bin/setOOmailer", line 197, in should_set_oo_mailer
:    the_bool = client.get_bool( basedir + "OOfix" )
:GError: Configuration server couldn't be contacted: D-BUS error: The GConf daemon is currently shutting down.
:
:Local variables in innermost frame:
:client: <gconf.Client object at 0x228f320 (GConfClient at 0x216ff00)>
:basedir: '/apps/gnome-gmail/'

Potential duplicate bug: 761721
Comment 1 Sergiu Niculescu 2012-11-11 10:20:29 UTC 
Created attachment 642716 [details]
File: executable
Comment 2 Sergiu Niculescu 2012-11-11 10:20:31 UTC 
Created attachment 642717 [details]
File: environ
Comment 3 Sergiu Niculescu 2012-11-11 10:20:34 UTC 
Created attachment 642718 [details]
File: smolt_data
Comment 4 Sergiu Niculescu 2012-11-11 10:20:36 UTC 
Created attachment 642719 [details]
File: core_backtrace
Comment 5 Fedora End Of Life 2013-07-03 23:54:35 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2013-08-01 03:02:07 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.