GNOME Bugzilla – Bug 644129
crash in Panel: system idle, screensaver running
Last modified: 2011-03-14 15:49:30 UTC
Version: 2.30.2 What were you doing when the application crashed? I was away from my desk, so the screen saver was running. Distribution: Debian 6.0 Gnome Release: 2.30.2 2010-11-12 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-5-686-bigmem #1 SMP Wed Jan 12 04:40:25 UTC 2011 i686 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Enabled GTK+ Theme: Dust Sand Icon Theme: Human GTK+ Modules: gail:atk-bridge, gnomebreakpad, gail-gnome, canberra-gtk-module Memory status: size: 614510592 vsize: 614510592 resident: 349614080 share: 21381120 rss: 349614080 rss_rlim: 18446744073709551615 CPU usage: start_time: 1298912669 rtime: 85440 utime: 69627 stime: 15813 cutime:202 cstime: 426 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' [Thread debugging using libthread_db enabled] 0xb773b424 in __kernel_vsyscall ()
+ Trace 226218
Thread 1 (Thread 0xb642e750 (LWP 30987))
Inferior 1 [process 30987] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (30 sec old) --------------------- Window manager warning: Invalid WM_TRANSIENT_FOR window 0x7b specified for 0x7800003 (pinentry). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x7b specified for 0x7800003 (pinentry). Playing WAVE '/usr/share/sounds/info.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ** (<unknown>:30971): WARNING **: Failed to send buffer ** (<unknown>:30971): WARNING **: Failed to send buffer ** (<unknown>:30971): WARNING **: Failed to send buffer (evolution-alarm-notify:31011): evolution-alarm-notify-WARNING **: alarm.c:252: Requested removal of nonexistent alarm! (evolution-alarm-notify:31011): evolution-alarm-notify-WARNING **: alarm.c:252: Requested removal of nonexistent alarm! ** ERROR:orbit-object.c:149:do_unref: assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) --------------------------------------------------
It's possible that some Iceowl reminders had just popped up. Ordinarily, this would affect the panel, but I've been trying to use alltray to dock my iceowl. It doesn't work when I run alltray iceowl as a startup item -- iceowl appears just like it would if i ran it without alltray -- although when I run alltray iceowl manually, after startup, I do get the docking effect.
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
I have -dbg packages installed for most things on my system. However, it looks like the missing debug symbols in the stack trace are for libORBit-2 and libbonobo-2. Unfortunately, I can't find any packages containing debug symbols for these libraries. Any suggestions?
Don't know Debian's package names. Plus nobody works on 2.30 anymore (2.32 is latest stable; 2.91 is unstable) so I don't see much sense in it...
(In reply to comment #4) > Don't know Debian's package names. In Debian is easy to guess package names (if you know the rule ;-) http://www.debian.org/doc/manuals/maint-guide/ch-first.en.html#s-namever In short: - All letters are in lowercase - Multiple words names are contracted - Version is added So, in this case the package names are liborbit2 and libbonobo2-0. Unfortunately, no -dbg packages for those ones. > Plus nobody works on 2.30 anymore (2.32 is latest stable; 2.91 is unstable) so > I don't see much sense in it... In some packages there are no big changes between 2.30 and 2.32, or even between several releases. So, even if it is always better having stack traces for the latest version, there are exceptions where those still might be useful (if the stack traces were complete, though). It seems today I woken up in verbose mode.
@André: unfortunately, even Debian unstable has only 2.30. @Germán: thanks for the clarifications. I'm hoping this is a one-off, and we can just ignore it, so I'm closing this again for now. However, if it starts happening a lot I'll figure out some way to get some better info to add to this bug (eg by building things from source).
This is exactly the same stack trace as bug #606700, so marking as a duplicate. The problem happened again over the weekend. I took a more careful look at the stack trace, and it seems to arise from gtk_event_box_size_allocate (called from panel_applet_size_allocate) when accessibility is enabled. (I did switch on accessibility recently.) Although the missing symbols are in /usr/lib/libORBit-2.so.0, I don't think these symbols are actually needed to debug the problem. The caller has a refcount problem, and looking at the code in liborbit isn't going to help with that. 606700 itself is marked as a duplicate of bug #597914, which dates from as long ago as 2009-10-09 and is associated with at-spi rather than gnome-panel. Although this bug, and 606700, are not exactly the same as 597914, it does seem that the problem is in at-spi, so I'm changing the product to at-spi. I'll leave this bug as resolved/duplicate but I'll make a note on 597914 which said on 2011-03-05, 'No recent duplicates". *** This bug has been marked as a duplicate of bug 606700 ***