I'm seeing the same problem after this morning's update (I'm running Tribe 5, and my previous update was on the 14th). I get the same error as Andrew. Furthermore, if you run gnome-settings-daemon in a terminal, you get:
$ gnome-settings-daemon Gdk-ERROR **: The program 'gnome-settings-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 1260 error_code 2 request_code 147 minor_code 35) (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.) aborting... [1190035719,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationAborted (core dumped) Running gnome-settings-daemon --sync gives the same error. Oh, and Andrew, I think the theme you're seeing is just the gnome failsafe, not a crossover from kubuntu, because my theme changed from what I was running to something that looks like a blocky win98. -- gnome startup problem with initialization https://bugs.launchpad.net/bugs/139761 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for meta-gnome2 in ubuntu. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
