Home > There Was > There Was An Error Starting The Gnome Settings Daemon

There Was An Error Starting The Gnome Settings Daemon

I had tried commenting the hosts file for IP6 and > it didn't work. That bug starts to be confusing too, lot of comment from different people, I would not be surprised if the current comments are not the same problem than the crasher which Greetz and THX, S. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. More about the author

Jaime Alemany (jaime-lunatico) wrote on 2007-04-16: #84 I *did* have problems, and my lo0 has been always working. But if I create a new desktop account and login, no errors are shown. I found that turning off ESD in the gnome control center sound screen solved the error described above. i was able to select my saved customized theme..

Logging in to a Fedora station is no problem with Xming as well. After that run the commands below Code: mv .gnome .gnome.backup mv .gnome2 .gnome2.backup mv .gconf .gconf.backup mv .gconfd .gconfd.backup After that do CTRL-ALT-F7 and login. alarm-notify.c:366 (alarm_notify_new) - Alarm Notify New alarm-notify.c:302 (alarm_channel_setup) - Channel Setup alarm-notify.c:241 (alarm_notify_init) - Initing Alarm Notify alarm-queue.c:1871 (alarm_queue_init) alarm-queue.c:218 (queue_midnight_refresh) - Refresh at Wed Nov 1 01:00:00 2006 evolution-alarm-notify-Message: Setting jgutty Using Fedora 0 24th August 2005 10:39 PM Gnome Settings Daemon error ssrini Using Fedora 7 8th October 2004 03:10 AM Current GMT-time: 14:54 (Sunday, 30-10-2016) All trademarks, and

More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Comment 3 Laurie Reeves 2008-05-28 14:03:18 EDT I am also seeing this problem (Fedora 8). Registered Linux User #362651 Don't use any of my solutions on working computers or near small children. Ubuntu 8.10 Having an Issue With Posting ? I found a solution in the ubuntuusers.de wiki: in "/etc/hosts" append the line: """ 127.0.0.1 localhost """ change to: """ 127.0.0.1 localhost unix """ After restarting network, freeNX works fine ;)

feel free to give it a try. Ubuntu Logo, Ubuntu and Canonical © Canonical Ltd. When I changed the keyboard layout there, It worked. Topics: Active | Unanswered Index »Applications & Desktop Environments »Error starting the GNOME Settings Daemon Pages: 1 #1 2008-05-31 14:05:32 derelic Member Registered: 2008-05-31 Posts: 5 Error starting the GNOME Settings

Vincent Jestin (mazargman) wrote on 2006-10-30: #11 I have this bug too. The last error message was: Did not receive a reply. Does that help? Last edited by whmitty; July 10th, 2009 at 03:09 PM.

This could indicate a problem with Bonobo, or a non-GNOME (e.g. Join our community today! The last error message was: Activation of org.gnome.SettingsDaemon timed out GNOME will still try to restart the Settings Daemon next time you log in." then no menus...). Show 1 reply 1.

I'll try a new account as well. http://linuxprofilm.com/there-was/there-was-an-error-starting-the-gnome-settings-daemon-redhat.html Adolfo R. Vincent Jestin (mazargman) wrote on 2006-10-31: #13 gnome-settings-daemon bug report Edit (5.4 KiB, text/plain) >does running gnome-settings-daemon by hand after the startup works fine? so this time i decided to try something different..

www.lunatico.es TFN: +34 91 859 5567 FAX: +34 91 790 3589 Aliarse (aliarse) wrote on 2007-02-24: #52 Had the same problem just now after chmod ing my home dir, would take Without the GNOME settings manager running, some preferences may not take effect. Age: 71 Posts: 22,928 Does this happen every time? click site Even after a reboot.

this issue is definitely caused by a kde related update.. Adv Reply December 24th, 2009 #4 Ian Eales View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Dec 2009 Beans 2 Re: [SOLVED]There was an error I get a brown screen for a few seconds, then a brown screen with a white rectangle on the top-left corner for up to 2 minutes, and finally the following error

The last error message was: Did not receive a reply.

Cheers, jaime El vie, 08-12-2006 a las 10:16 +0000, Sebastien Bacher escribió: > Does doing one of those only fix the problem? Now I just need to figure out which RPM is responsible. This could indicate a problem with Bonobo, or a non-GNOME (e.g. Home | New | Search | [?] | Reports | Requests | Help | NewAccount | Log In [x] | Forgot Password Login: [x] | Report Bugzilla Bug Legal [Date Prev][Date

Hope this helps some of you out there. no error, system runs great but i still wanted my kde related icons back & i do use pidgin so re-installed the necessary packets from source manager & everything is back I can post some more information but I found nothing not published here before. navigate to this website My edgy was updated from dapper.

Ubuntu 8.10 So on day 4 of my Ubuntu 8.10 installation, i decided it was time to customize my desktop and install some cool themes and customize my desktop.. Search this Thread 06-29-2008, 09:18 AM #1 jaysrikrishna LQ Newbie Registered: Oct 2007 Posts: 21 Rep: error starting GNOME setting Daemon Hi friends , This is the error message Turned off Software Sound Mixing seemed to work at first. (No longer hung for several minutes starting Gnome, no more error message) Other strange things started happening though.. I removed ::1 ip6-localhost ip6-loopback from /etc/hosts and added the lo loopback reference in /etc/network/interfaces.

I will test things separately to point out which one does what. -- gnome-settings-daemon crashes at login https://launchpad.net/bugs/61381 -- No virus found in this incoming message. I tried to change my SSID in /etc/wpa_supplicant.conf to "blablabla", and then it also worked fine. My system: ubuntu 7.04 (new install), nx package (client, server, etc). commenting out IPv6 lines in host file (no effect) 3.

I will test things separately to point out which one does what. BTW, I tried on a second windows machine, and in this case the windows firewall trick did not do it, but disabling the ESD did! You can try running "/usr/lib/gnome-settings-daemon" again manually in a terminal, which will sometimes clear it up straight away. I still think the problem is with configuration files related to D-Bus sessions, but I haven't been able to find the file that is the culprit.

Had to kill gnome panel. However, it is still running incredibly slowly (10 minutes and it still hasn't finished putting together the desktop). Thanks, jaime El mar, 20-02-2007 a las 08:21 +0000, sleuth escribió: > After spending all day fighting nomachines windows client, freenx > server, nomachines nxserver, on opensuse 10.2 with gnome. Registration is quick, simple and absolutely free.