Yes, i have the problem here.

On Thu, Apr 3, 2008 at 7:43 AM, Shaligar <email address hidden> wrote:

> Hello,
>
> When I try to login into gnome, I get an empty brown background, but if
> I wait long enough (around 2 minutes), the desktop loads, along with an
> error about gnome-settings-daemon. Because of that, my skins / icons are
> not configured as they should. After some more time, tho, gnome-
> settings-daemon seems to load, as my skin and icons change, and the
> welcome sound is played.
>
> If this the same bug, I'm ready to test any fixes.
>
> --
> error starting GNOME Settings Daemon
> https://bugs.launchpad.net/bugs/199960
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "gnome-settings-daemon" in Ubuntu: Confirmed
>
> Bug description:
> Happened after last night's updates to Hardy.
>
> ** (gnome-settings-daemon:11172): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/media-keys for changes
> ** (gnome-settings-daemon:11172): DEBUG: GnomeSettingsModule 0x8080200
> initialising
> ** (gnome-settings-daemon:11172): DEBUG: Loading
> /usr/lib/gnome-settings-daemon-2.0/libxrandr.so
>
> ** (gnome-settings-daemon:11173): WARNING **: Failed to acquire
> org.gnome.SettingsDaemon
>
> ** (gnome-settings-daemon:11173): WARNING **: Could not acquire name
> ** (gnome-settings-daemon:11173): DEBUG: SettingsDaemon finished
> ** (gnome-settings-daemon:11172): DEBUG: Registering GsdXrandrPlugin
> ** (gnome-settings-daemon:11172): DEBUG: Creating object of type
> GsdXrandrPlugin
> ** (gnome-settings-daemon:11172): DEBUG: GsdXrandrPlugin initializing
> ** (gnome-settings-daemon:11172): DEBUG: Activating xrandr plugin
> ** (gnome-settings-daemon:11172): DEBUG: Starting xrandr manager
> 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.)
> 1205011405.201156 Session manager: disconnected...
> ** (gnome-settings-daemon:11184): DEBUG: Successfully connected to D-Bus
> ** (gnome-settings-daemon:11184): DEBUG: Starting settings manager
> ** (gnome-settings-daemon:11184): DEBUG: Loading settings plugins from
> dir: /usr/lib/gnome-settings-daemon-2.0/
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/xrdb for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/screensaver.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/screensaver for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/xsettings for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/background.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/background for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/keybindings for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/keyboard for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/typing-break for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/font.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/font for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/a11y-keyboard for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/clipboard for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/dummy.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/dummy for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/mouse.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/mouse for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/sound.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/sound for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/xrandr for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/media-keys.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/media-keys for changes
> ** (gnome-settings-daemon:11184): DEBUG: GnomeSettingsModule 0x8080200
> initialising
> ** (gnome-settings-daemon:11184): DEBUG: Loading
> /usr/lib/gnome-settings-daemon-2.0/libxrandr.so
> ** (gnome-settings-daemon:11184): DEBUG: Registering GsdXrandrPlugin
> ** (gnome-settings-daemon:11184): DEBUG: Creating object of type
> GsdXrandrPlugin
> ** (gnome-settings-daemon:11184): DEBUG: GsdXrandrPlugin initializing
> ** (gnome-settings-daemon:11184): DEBUG: Activating xrandr plugin
> ** (gnome-settings-daemon:11184): DEBUG: Starting xrandr manager
> 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.)
>
> [Update]
> This was happening previously as bug 197153, which was believed fixed, but
> evidently not.  -- bryce
>
>