randomly gnome-settings-daemon fails to start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Settings Daemon |
Unknown
|
Medium
|
|||
gnome-settings-daemon (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gnome-settings-
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-
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:/
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-
I have the following in xsession-errors:
The program 'gnome-
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
tags: | added: lucid maverick |
Changed in gnome-settings-daemon (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in gnome-settings-daemon: | |
importance: | Unknown → Medium |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http:// wiki.ubuntu. com/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.