Bug 532058 - Evolution "Could not send message to GConf daemon: Message did not receive a reply"
Summary: Evolution "Could not send message to GConf daemon: Message did not receive a ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-30 13:32 UTC by Máirín Duffy
Modified: 2010-12-04 03:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 03:35:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
error dialog (22.02 KB, image/png)
2009-10-30 13:32 UTC, Máirín Duffy
no flags Details

Description Máirín Duffy 2009-10-30 13:32:42 UTC
Created attachment 366796 [details]
error dialog

Description of problem:

Just installed F12 from beta and did updates from the rawhide repo last night. Turned my computer on, fresh boot, this morning and opened up evolution to check my mail. Got a popup error dialog saying:

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))

Attaching screenshot.

evolution-2.28.0-2.fc12.x86_64

Comment 1 Matthew Barnes 2009-10-30 14:36:45 UTC
I see those messages too from time to time.  They seem harmless; a temporary hiccup in the GConf daemon where I guess it failed to respond within a given timeout.  But then it seems okay again.  I'm not sure what's causing it -- maybe Ray knows?

Comment 2 Bug Zapper 2009-11-16 14:41:28 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2010-11-04 06:58:37 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2010-12-04 03:35:54 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


Note You need to log in before you can comment on or make changes to this bug.