GNOME Bugzilla – Bug 549190
crash in Computer:
Last modified: 2008-08-24 12:11:44 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: NoiaWarm Memory status: size: 68804608 vsize: 68804608 resident: 20811776 share: 14884864 rss: 20811776 rss_rlim: 4294967295 CPU usage: start_time: 1219574502 rtime: 281 utime: 235 stime: 46 cutime:2 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6a4e710 (LWP 5347)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 205597
Thread 1 (Thread 0xb6a4e710 (LWP 5347))
----------- .xsession-errors --------------------- alarm-queue.c:2102 (alarm_queue_remove_async) alarm-queue.c:2075 (remove_client_alarms) - size 0 alarm-queue.c:2107 (alarm_queue_remove_async) - Disconnecting Client alarm-queue.c:2116 (alarm_queue_remove_async) - Disconnecting Query alarm-notify.c:255 (dequeue_client) - Removing client 0x80d0ba0 alarm-queue.c:2102 (alarm_queue_remove_async) alarm-queue.c:2075 (remove_client_alarms) - size 0 alarm-queue.c:2107 (alarm_queue_remove_async) - Disconnecting Client alarm-queue.c:2116 (alarm_queue_remove_async) - Disconnecting Query alarm-notify.c:255 (dequeue_client) - Removing client 0x80d4cc0 alarm-queue.c:2102 (alarm_queue_remove_async) alarm-queue.c:2075 (remove_client_alarms) - size 0 alarm-queue.c:2107 (alarm_queue_remove_async) - Disconnecting Client alarm-queue.c:2116 (alarm_queue_remove_async) - Disconnecting Query alarm-queue.c:1930 (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 480179 ***