First of all, I am sorry that I may send this bug report against the wrong package.
With Ubuntu 10.10 (actually on two different machines: one of them is a notebook with fresh install, the other is upgraded since the "stone age" but it is also a 10.10 32 bit version now) sometimes I have the experience that gtk/gnome apps loses the theme. It means that things appears in a default "themeless" GTK way. On the notebook (the new install) let's say 2 startups from 10 (in average) results the themeless appearance after logging in (including the gnome panel). On the other machine, if some application which used the panel exists (or killed) there is a chance that theme switches back to the "themeless" state without my will. In both cases, if I start application "gnome-appearance-properties", everything returns into the correct themed appearance even without doing anything in gnome-appearance-properties just starting it, and CTRL-C before its window appears (I run it from terminal window) helps. I have no idea what can cause this really annoying bug. Thanks in advance, if you have any advice to avoid this.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libgtk2.0-0 2.22.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8
Uname: Linux 2.6.35-24-generic-pae i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sun Jan 2 12:22:08 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: gtk+2.0
Hmm, I found this in .xsession-erros file:
** Message: applet now embedded in the notification area
The program 'gnome-
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 1365 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.)
Can it cause the problem? Is it a gnome-setting-