GNOME Bugzilla – Bug 328002
keyboard applet sometimes crash when logout
Last modified: 2006-03-22 00:06:51 UTC
Steps to reproduce: just logout Stack trace: (gdb) thread apply all bt
+ Trace 65459
Thread 1 (process 8821)
Other information:
Ghm, I cannot really reproduce it:((. The story is that GSwitchItAppletFilterXEvt should be unregistered when the last applet is removed (so globals.appletInstances turns to NULL). But it seems for some reason it is called in some "semi-destroyed" state. Could you please run the applet from the console with XKL_DEBUG=150 or smth. May be it would give some hints...
exact gnome version: * gnome-desktop package - 2.12.1-0ubuntu * gnome-applets 2.12.1-0ubuntu i tried do another backtraces and some diffs. it's seems that bt is exactly same (called function). i added XKL_DEBUG to GNOME start script, and i'm waiting for core dump. it's not easy to reproduce that problem, so please be patient. can you explain what you mean with smth?
Well, this env. variable makes gnome-keyboard-indicator applet output a lot of interesting trace information into stdout. So if you could capture it and attach - I'd really appreciate. "smth" means you can change the trace level. With level 500 it will really output LOADS of stuff. The reasonable trace level is usually somewhere between 150 and 200.
sorry, but i can't do this. reproduce of this bug is not easy, that is reason for using core. Is there any solution to forward stdout(or that debugging information) of that applet to file automaticly? removing applet from panel and running from console all the time after login is backwardness and i must do it all time for example for week before crash.
Ghm. So what you are saying is this bug not always reproducable? I love this kind of bugs :((( Well, there is solution - but it would require some hacking of the source code and rebuilding the applet. If you are ready for this - I can give you some pointers.
Created attachment 58917 [details] Keyboard DEBUG log at level 200 from login to logout + crash, BT is same
Tonight I put committed some minor fixes to libxklavier CVS (on freedesktop.org). Could you please have a look whether it would help you?
Created attachment 59635 [details] Keyboard DEBUG log at level 200 from login to logout - CVS version of xklavier
thanks, I'll have a look
Well, there is nothing really suspicious in the log file. The applet's window 3000003 gets destroyed - but the visible effect of it is well within limits... I added a bit more debug stuff into CVS. But at the moment I do not have any brilliant idea... If you could find some way to reproduce it reliably...
Ok, so the fix is found now, I'll commit the code to CVS. I will break the code freeze - because it is a bad crash...
committed.