Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I recently updated my fedora 13 system with the latest package versions. Following this update the gconf daemon started crashing continuously (i.e. it crashes, gets restarted by the system, crashes, ...).
I am no longer to log into the gnome desktop, i assume because of the dependency it has on gconf.
I am able to run the kde desktop but can realistically only run xterms because most other apps I run (e.g. firefox, thunderbird) cause the system to communicate with the gconf daemon.
Is there a way to disable gconf so kde won't use it or alternatively is there a way to restore gconf to a usable state?
I have opened a bug with redhat and looking through the bugzilla list it looks like others are having the same issue. One has to wonder why such a heavyweight system is used to store desktop and application settings (according to wikipedia gconf uses corba for client server communication).
Here is the crash info:
[New Thread 2342]
Core was generated by `/usr/libexec/gconfd-2'.
Program terminated with signal 11, Segmentation fault.
#0 IA__g_slist_foreach (list=0xe64b847c,
func=0x381583a520 <IOP_component_free>, user_data=0x0) at gslist.c:855
855 gslist.c: No such file or directory.
Assuming that you have not updated the system again since this error began, use
yum history undo last
Then if you know for certain what package caused the problem you can update with
yum update --exclude <bad-package>
Thanks for the suggestion.
The gconf site (http://projects.gnome.org/gconf/) stated that it's database is stored in $HOME/.gconf. Do I deleted this directory (actually moved it to another name) as well as a $HOME/.gconfd directory which existed as well. After logging out and back in again no more crashes in gconfd. Looks like the database somehow got corrupted and gconf didn't deal with it gracefully.