GNOME Bugzilla – Bug 496247
crash in Workspace Switcher:
Last modified: 2007-11-13 07:24:02 UTC
Version: 2.20.1 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.20.1 2007-11-09 (JHBuild) BugBuddy Version: 2.20.1 System: Linux 2.6.23.1-mactel #1 SMP Fri Nov 9 19:12:52 CET 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: 28155904 vsize: 28155904 resident: 12910592 share: 10182656 rss: 12910592 rss_rlim: 4294967295 CPU usage: start_time: 1194899298 rtime: 25 utime: 22 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/local/libexec/wnck-applet' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6df46c0 (LWP 4472)] 0xb7f29410 in __kernel_vsyscall ()
+ Trace 177270
Thread 1 (Thread 0xb6df46c0 (LWP 4472))
----------- .xsession-errors --------------------- alarm-queue.c:2123 (alarm_queue_remove_async) - Disconnecting Client alarm-queue.c:2132 (alarm_queue_remove_async) - Disconnecting Query alarm-notify.c:259 (dequeue_client) - Removing client 0x80e2310 alarm-queue.c:2169 (alarm_queue_remove_client) - Posting a task alarm-queue.c:2118 (alarm_queue_remove_async) alarm-queue.c:2090 (remove_client_alarms) - size 0 alarm-queue.c:2123 (alarm_queue_remove_async) - Disconnecting Client alarm-queue.c:2132 (alarm_queue_remove_async) - Disconnecting Query alarm-notify.c:259 (dequeue_client) - Removing client 0x80e1e00 alarm-queue.c:2169 (alarm_queue_remove_client) - Posting a task alarm-queue.c:2118 (alarm_queue_remove_async) alarm-queue.c:2090 (remove_client_alarms) - size 0 alarm-queue.c:2123 (alarm_queue_remove_async) - Disconnecting Client alarm-queue.c:2132 (alarm_queue_remove_async) - Disconnecting Query alarm-queue.c:1941 (alarm_queue_done) --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 385380 ***