desktop-packages team mailing list archive

[Matt Fischer <588155@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 649809 ***
    https://bugs.launchpad.net/bugs/649809

I am seeing this in 11.10 after I resume from sleep.  Tamas's work-
around seems to solve the problem, as does logging out and logging back
in.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/588155

Title:
  randomly gnome-settings-daemon fails to start

Status in Gnome Settings Daemon:
  Unknown
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-settings-daemon

  Randomly when logging in, rather than the normal Ambiance theme I get
  a default default GTK theme on the gnome-panel.

  There is no gnome-settings-daemon listed in the processes.

  Going in the the Appearance seems to start it up, and the theme is
  applied to the gnome-panel. I need to kill nautilus for it to be
  rethemed.

  This is happening on 2 different computer systems. Both AMD64 with
  nvidia graphics cards (using the proprietary driver), otherwise with
  fairly different hardware.

  There was another bug for this, with several other people reporting the same issue however it seems to have been closed as 'incomplete'.
  https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/312501

  I also sometimes notice the long delay on login mentioned in the above
  bug, (basically the wallpaper loads then it just sits there doing
  nothing, then the panels come in). Not sure if it has anything to do
  with the gnome-settings-daemon though (sometimes the panels come in
  fine).

  I have the following in xsession-errors:
  The program 'gnome-settings-daemon' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadMatch (invalid parameter attributes)'.
    (Details: serial 1177 error_code 8 request_code 3 minor_code 0)
    (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.)

  lsb_release -rd 
  Description:	Ubuntu 10.04 LTS
  Release:	10.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/588155/+subscriptions