User-Agent: Mozilla/5.0 (X11; U; Linux i686; en; rv:1.8.1.6) Gecko/20061201 Epiphany/2.18 Firefox/2.0.0.6 (Ubuntu-feisty) Build Identifier: This was reported on Launchpad : https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/123701 by : https://bugs.launchpad.net/~shirishag75 I had just closed down exaile from the panel instead of closing it from system tray when xfce4-panel crashed. First exaile crashed then this. Reproducible: Couldn't Reproduce ThreadStackTrace : http://launchpadlibrarian.net/8286117/ThreadStacktrace.txt StackTrace : http://launchpadlibrarian.net/8286116/Stacktrace.txt
The stack trace involves a GtkTable widget. The panel does not use tables except in the customize panel dialog. Did you have that dialog open at the time of the crash? I also don't understand what you mean by 'closing exaile from the panel, instead of closing it from the system tray'. Maybe you have a plugin that controls exaile?
I will ask this to the original reporter.
Answer of the original reporter : "I don't remember if there was a dialog open at the time of the crash or not. It used to happen pretty often is all I know/remember. Since then I've moved to exaile svn & being happy there ;) Now for the other query. Apologies for not making sense, that's simply due to me coming from windows. I'll try to explain. How its set up at my end is having two panels, a panel at the top comprising of icons & the systray where active applications come up. The other panel resides down. which again just has the active applications open with the darkness telling which is the active application of them. For e.g. in the screenshot I have attached FF is the active application. Now right-clicking on any of these applications has 6 options like Unmaximize, Hide, Shade, Stick, Send to... and then Close. This used to happen when I'm triggering the Close option. Hope this is good enough. Please lemme know if more info. is required."
There is 1 table used in this crash: netk-taskbar. I'd appreciate it if you can try this with the latest rc of gtk 2.11. 2.11 is known to have some (if not a lot) regressions, so it's hard to blaim this on the panel/netk code.
Well, in Gusty we have GTK+ 2.11.6 the latest rc, but it happened when there was still 2.11.4. Now with GTK+ 2.11.6 and exaile from svn, shirish says that it doesn't happen anymore, so it was either a problem with gtk or with exaile. Maybe you can close this, and we will reopen if it happens again with the updated libs/apps. Thanks.
Sounds like a good solution to me.
Thanks.