GConf daemon not starting

[admered1]

I have been having this from time to time as well.

The fix that works for me is to kill gconfd-2

# killall gconfd-2

The next time something that needs it starts, the daemon restarts as well.

Hope this helps

[Dutchy]

I have been having this from time to time as well.

The fix that works for me is to kill gconfd-2

# killall gconfd-2

The next time something that needs it starts, the daemon restarts as well.

Hope this helps

Thanks, that solution works great for me!

[admered1]

Thanks, that solution works great for me!

Excellent

Now I guess we just have to hope that someone susses out why gconfd-2 is glitching and failing to shut down properly.

[ranjithsiji]

I have been having this from time to time as well.

The fix that works for me is to kill gconfd-2

# killall gconfd-2

The next time something that needs it starts, the daemon restarts as well.

Hope this helps

http://forums.fedoraforum.org/archiv.../t-273292.html

[lukeab]

this thread is tagged as [SOLVED] and it's not by all reports in the comments above and in the alternate thread posted by ranjithsiji .
I've been getting this error since i installed back in February. The workarounds above are good, but it's not SOLVED.

[DBelton]

Well, this forum isn't about solving problems that take a developer to fix in the application, and then packaging it up and making it available to all users in the updates repo. The developers don't hang around in here.

This forum is about getting things working on peoples system that are having problems. If a workaround fixes their issue, then it is considered solved in a case like this one. (If you look around, most of the cases in here where there is an issue with the application the solution is a workaround, not actual an actual fix)

I do agree, the issue really isn't solved, but for the purpose of this forum it is. The original poster found a way to work around the issue, so his issue was solved.

To get a solution, chances are you would have to file a bug report wherever the developer of the application would see it. (If it happens to be a Gnome application, then you are probably just SOL. I have filed several bug reports against Gnome applications, most have been sitting there over a year now without even a single response, and yes, the bugs still exist. The only) bug report on a gnome application I even got a response to was only after it was mentioned that it might be put on the blocker list (that bug did get fixed, too).)

[cohmstede]

Is it just me or is this problem getting worse?

[Alternator]

Is it just me or is this problem getting worse?

Got the same on Opensuse 12.2 with Gnome

[admered1]

Funnily enough, I have just had to restart the gconfd-2 daemon on a F17 laptop .. again

[KJG41HES99]

I upgraded to F18 a few weeks ago and since a few days I started to see this **** again (as with F16). I strongly think that it's related to some of my post-installation changes, but trying to remember, the only thing that I can think is the disabling of the tracker stuff; I re-enabled it but the problem persists. Sigh.

[dmcnulty]

I wrote the original message back in Nov 2011 and I'm amazed that the problem is still plaguing users after 15 months. I switched over to XFCE exclusively for a long time, even through an upgrade to F17. But when MATE became available, I switched over to that, and I'm quite pleased with it. I have revived a few of the Gnone apps I formerly used and haven't had any configuration daemon problems. I might consider the Gnome desktop again someday if they do away with setting up the start menu as a screenful of icons.

[tkalfaoglu]

I just started getting this too on Fedora 18..

The only changes between now and this morning when I was not getting this error are:
1) Removed nouveau.modeset=0 from /boot/grub2/grub.cfg
2) ReInstalled latest compat-wireless for my problems with Atheros AR8152