[hardy] gnome-settings-daemon doesn't start

Bug #188010 reported by Hervé Cauwelier
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-settings-daemon

Just started my session and I have the default Gnome icons and colors, with ridiculously small fonts.

I read this when trying to start gnome-settings-daemon by hand:

$ gnome-settings-daemon

** (gnome-settings-daemon:7298): WARNING **: Failed to acquire org.gnome.SettingsDaemon

** (gnome-settings-daemon:7298): WARNING **: Could not acquire name
** (gnome-settings-daemon:7298): DEBUG: SettingsDaemon finished

Sending it a signal to restart doesn't change anything.

ii gnome-settings-daemon 2.21.90.1-0ubuntu3 GNOME settings daemon

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. Is dbus working correctly? Do you have issues with other things?

Changed in gnome-settings-daemon:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Hervé Cauwelier (hcauwelier-deactivatedaccount) wrote :

I forgot about this bug. It was fixed a few days later.

Let's close it.

Changed in gnome-settings-daemon:
status: Incomplete → Invalid
Revision history for this message
trisa (dietisheim) wrote :

current version has that bug again... (it was fixed for some days and reappeared with the last update): 2.22.0-0ubuntu1 (hardy)

trisa@pmobilead:~$ gnome-settings-daemon
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 89 error_code 1 request_code 151 minor_code 6)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Revision history for this message
David Gillies (daveg) wrote :

I'm also seeing the same error as trica

Revision history for this message
drjimmy42 (jjrussell) wrote :

Just upgraded today and the BadRequest bug is still there. Is there any workaround to get GSD started?

Revision history for this message
Damiano Dallatana (damidalla) wrote :

Same behaviour here with Hardy installed as Alpha6 and updated as of yesterday.
The starting g-s-d manually gets:

$ gnome-settings-daemon
** (gnome-settings-daemon:14409): WARNING **: Failed to acquire org.gnome.SettingsDaemon
** (gnome-settings-daemon:14409): WARNING **: Could not acquire name

Revision history for this message
NoOp (glgxg) wrote :

Same here following an upgrade from Gutsy to 8.04.1 using the latest Alternate 8.04.1 CD. gnome-settings-daemon 2.22.1-0ubuntu2. Hardware is an IBM Thinkpad A21.

Tried reinstalling:
sudo apt-get install --reinstall gnome-settings-daemon
and that stops on "Unpacking replacement gnome-settings-daemon" w/disk light constant on.

Revision history for this message
NoOp (glgxg) wrote :

I've resolved this issue on my Thinkpad (which is a T21 - the A21 had no issues). I stumbled across this after I found that I could no longer ping localhost or hostname. What I found:

1. /etc/network/interfaces had the following line commented out:

# iface lo inet loopback

I uncommented the line.

2. I used the following to bring up loopback:

sudo ifconfig lo localhost
sudo route add localhost dev lo

courtesy of: <http://sudan.ubuntuforums.com/showpost.php?s=8089ac6575f0425788949c951c5b3e8b&p=657273&postcount=7>

I also found a similar blog regarding the same:
<http://arunpc.com/2008/06/01/ubuntu-there-was-an-error-starting-the-gnome-settings-daemon/>

After I was able to reliably ping localhost I no long get the gnome-settings-daemon msg.

Revision history for this message
Tanath (tanath) wrote :

I still get this bug often on first login. I have to log out and back in to fix it. I have no problems pinging localhost.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.