GNOME Bugzilla – Bug 502209
crash in Battery Charge Monitor: switching on and off the...
Last modified: 2007-12-07 21:31:59 UTC
What were you doing when the application crashed? switching on and off the bluetooth (laptop Compaq nc6120) Distribution: Unknown Gnome Release: 2.20.1 2007-10-19 (Archlinux) BugBuddy Version: 2.20.1 System: Linux 2.6.23-ARCH #1 SMP PREEMPT Sun Nov 18 07:43:05 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 23486464 vsize: 23486464 resident: 9728000 share: 8335360 rss: 9728000 rss_rlim: 4294967295 CPU usage: start_time: 1196970654 rtime: 14 utime: 12 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/battstat-applet-2' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb7f3bb30 (LWP 8188)] 0xb7f63410 in __kernel_vsyscall ()
+ Trace 181041
Thread 1 (Thread 0xb7f3bb30 (LWP 8188))
----------- .xsession-errors (6087 sec old) --------------------- (evolution:8210): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:8210): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:8210): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:8210): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:8210): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:8210): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (evolution:8210): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 446097 ***