GNOME Bugzilla – Bug 531745
crash in System Monitor: closed, opened, closed a...
Last modified: 2011-11-11 10:03:55 UTC
Version: 2.20.2 What were you doing when the application crashed? closed, opened, closed and opened again Ekiga Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.20.3 2008-03-29 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.24-gentoo #8 SMP Thu May 1 22:58:15 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: OSX Memory status: size: 24387584 vsize: 24387584 resident: 9900032 share: 8335360 rss: 9900032 rss_rlim: 4294967295 CPU usage: start_time: 1210082997 rtime: 3 utime: 1 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-system-monitor' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6b91940 (LWP 14426)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 197032
Thread 1 (Thread 0xb6b91940 (LWP 14426))
----------- .xsession-errors (189016 sec old) --------------------- (11:37:41) pidgin-libnotify: closed_cb(), notification: 0x8626100 (11:37:41) pidgin-libnotify: closed_cb(), notification: 0x82707d0 (11:38:09) blist: Updating buddy status for 4588458 (ICQ) (11:38:09) blist: Updating buddy status for 4588458 (ICQ) (11:38:09) blist: Updating buddy status for 4588458 (ICQ) (11:38:26) oscar: Claiming to have a buddy icon (11:38:26) oscar: Sending IM, charset=0x0000, charsubset=0x0000, length=158 (11:38:26) oscar: Sent message to 380440756. (11:39:57) oscar: incomingim_ch1: unknown TLV 0x0016 (len 4) (11:39:57) oscar: incomingim_ch1: unknown TLV 0x0013 (len 1) (11:39:57) oscar: Received IM from 380440756 with 1 parts (11:39:57) oscar: Parsing IM part, charset=0x0000, charsubset=0x0000, datalen=2 (11:39:57) pidgin-libnotify: notify(), new: title: 'grimreaper says:', body: 'ah', buddy: 'grimreaper' ...Too much output, ignoring rest... --------------------------------------------------
Sorry, I thought this was related to Ekiga. The error occured probably again that I accidently clicked twice on the system monitor.
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 516325 ***