desktop-packages team mailing list archive

[Daniel van Vugt <vanvugt@xxxxxxxxx>]

I haven't been able to reproduce the bug for over an hour so getting a breakpoint in is a bit difficult right now. But it appears the problem is likely a race condition whereby gnome-settings-daemon is starting slightly too quickly, expecting something else to be running already that isn't. This theory seems to be supported by the message:
    WARN  2011-10-25 14:07:02 glib.gdk <unknown>:0 gdk_xsettings_watch_cb(): Couldn't find window to unwatch
which is only seen in xsession-errors when the bug occurs.

@everyone: When you reproduce this bug next, could you please open a terminal and run:
    ps auxw > /tmp/pslist.txt
and attach the file pslist.txt to this bug?

-- 
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/879793

Title:
  No GTK theme applied on login, should be Ambiance

Status in “gnome-settings-daemon” package in Ubuntu:
  Incomplete

Bug description:
  On random occasions, logging into Ubuntu (Unity) there is no GTK/Gnome
  theme active. You only see what looks like stock icons and GTK
  theming. Logging out and logging back in again usually fixes the
  problem, and the Ambiance theme (or whatever) is then applied
  correctly.

  We have confirmation this is affecting multiple users in Ubuntu 11.10.
  However I personally used to see the problem occasionally in Ubuntu
  11.04 too.

  When the bug occurs you will see "BadMatch ... error_code 8
  request_code 3 minor_code 0" in .xsession-errors:

  (gnome-settings-daemon:2108): Gdk-WARNING **: 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 1265 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.)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 22 08:46:57 2011
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-10-21 (0 days ago)
  XsessionErrors:
   (nautilus:1944): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
   (nautilus:1944): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
   (jupiter:1965): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed

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