GNOME Bugzilla – Bug 483760
crash in Panel: nothing
Last modified: 2007-10-06 11:48:02 UTC
Version: 2.18.1 What were you doing when the application crashed? nothing Distribution: Mandriva Linux release 2007.1 (Official) for x86_64 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-15mdv #1 SMP Tue Aug 14 18:32:17 MDT 2007 x86_64 X Vendor: The X.Org Group X Vendor Release: 6600 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 280403968 vsize: 280403968 resident: 17850368 share: 12697600 rss: 17850368 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191593281 rtime: 16 utime: 15 stime: 1 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47748372592848 (LWP 4547)] (no debugging symbols found) 0x00002b6d45e67bf4 in waitpid () from /lib64/libpthread.so.0
+ Trace 168015
Thread 1 (Thread 47748372592848 (LWP 4547))
----------- .xsession-errors (6 sec old) --------------------- Initializing gnome-mount extension SIOCETHTOOL: Opération non permise SIOCETHTOOL: Opération non permise getting exclusive lock on urpmi unlocking urpmi database le média « Updates for Mandriva Linux 2007.1 » est à jour (/usr/lib64/beagle/BeagleDaemon.exe:4683): libebook-WARNING **: invalid escape, passing it through (/usr/lib64/beagle/BeagleDaemon.exe:4683): libebook-WARNING **: invalid escape, passing it through (/usr/lib64/beagle/BeagleDaemon.exe:4683): libebook-WARNING **: invalid escape, passing it through ** ERROR **: file orbit-object.c: line 149 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... --------------------------------------------------
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 ***