GNOME Bugzilla – Bug 484778
crash in Panel: Lunch of Wireshark in ro...
Last modified: 2007-10-08 19:31:12 UTC
Version: 2.20.0.1 What were you doing when the application crashed? Lunch of Wireshark in root mode Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.21.070730 #1 SMP Sun Jul 29 19:45:36 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 42029056 vsize: 42029056 resident: 25645056 share: 13402112 rss: 25645056 rss_rlim: 4294967295 CPU usage: start_time: 1191828838 rtime: 4927 utime: 4446 stime: 481 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (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 0xb6f326b0 (LWP 6052)] (no debugging symbols found) 0xb782dbce in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 168813
Thread 1 (Thread 0xb6f326b0 (LWP 6052))
----------- .xsession-errors (7973 sec old) --------------------- fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub fixme:imm:ImmReleaseContext (0xd0234, 0x11a460): stub ...Too much output, ignoring rest... --------------------------------------------------
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 480982 ***