GNOME Bugzilla – Bug 463307
crash in Panel: nothing
Last modified: 2007-08-23 19:20:19 UTC
Version: 2.18.0 What were you doing when the application crashed? nothing Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 59375616 vsize: 59375616 resident: 17436672 share: 9629696 rss: 17436672 rss_rlim: 4294967295 CPU usage: start_time: 1183513391 rtime: 45 utime: 34 stime: 11 cutime:0 cstime: 0 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 -1208752416 (LWP 2991)] (no debugging symbols found) 0x00aac402 in __kernel_vsyscall ()
+ Trace 152681
Thread 1 (Thread -1208752416 (LWP 2991))
----------- .xsession-errors --------------------- Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/smp-2.4.9-3.i686enterprise-RHAS2.1/objects (total watches = 947) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/smp-2.4.20-8.i686bigmem-RH9.0/objects (total watches = 948) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/bld-2.4.20-31.i686-RH1081895016/objects (total watches = 949) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/smp-2.4.9-34.i686-RH7/objects (total watches = 950) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/bld-2.4.9-57.i686smp-RH1102038758/objects (total watches = 951) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/up-2.4.20-18.athlon-RH9.0/objects (total watches = 952) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/smpPAE-2.4.19-175-SuSE-8.1/objects (total watches = 953) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/smp-2.4.9-31.i686enterprise-RH7.2/objects (total watches = 954) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/bld-2.6.8-24.14-i586bigsmp-SuSE9.2/objects (total watches = 955) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/smpPAE-2.4.18-1_turbo-80/objects (total watches = 956) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/up-2.4.18-14.athlon-RH8.0/objects (total watches = 957) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/bld-2.4.9-e.65-athlonsmp-RHEL2.1/objects (total watches = 958) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/bld-2.6.11.4-21.9-i586default-SuSE9.3/objects (total watches = 959) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/smp-2.4.9-21.i686-RH7.2/objects (total watches = 960) Watching directory /home/rdurham/Desktop/vmware-distrib/lib/modules/binary/bld-2.6.11.4-21.7-i586bigsmp-SuSE9.3/objects (total watches = 961) --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 452428 ***