GNOME Bugzilla – Bug 440600
crash in Panel: abrindo a seção depois d...
Last modified: 2007-05-23 01:11:06 UTC
Version: 2.18.0 What were you doing when the application crashed? abrindo a seção depois de trocar o tema do GDM Distribution: Mandriva Linux release 2007.1 (Official) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-13mdvlegacy #1 SMP Fri Mar 23 19:05:24 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Glossy Icon Theme: OSX Memory status: size: 53858304 vsize: 53858304 resident: 20213760 share: 12881920 rss: 20213760 rss_rlim: 4294967295 CPU usage: start_time: 1179869845 rtime: 103 utime: 92 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/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226651968 (LWP 14736)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 135616
Thread 1 (Thread -1226651968 (LWP 14736))
----------- .xsession-errors --------------------- kxdocker: WARNING: loading xml... kxdocker: WARNING: saving xml configuration to backup configuration... kxdocker: WARNING: loading plugins... XEPlugin_Sounds xeplugin_register() kxdocker: WARNING: Plugins loaded: kxdocker: WARNING: Going to background... GTK Accessibility Module initialized GTK Accessibility Module initialized Bonobo accessibility support initialized /home/oracle/.MdkOnline/mdkonline should be set to TRUE: please use --force or -f option to launch applet at /usr/bin/mdkapplet line 242. GTK Accessibility Module initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
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 432554 ***