GNOME Bugzilla – Bug 483606
crash in Panel: je voulais rajouter un a...
Last modified: 2007-10-05 10:46:12 UTC
Version: 2.18.1 What were you doing when the application crashed? je voulais rajouter un applet au tableau de bord 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: 280141824 vsize: 280141824 resident: 17555456 share: 12591104 rss: 17555456 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191564493 rtime: 18 utime: 16 stime: 2 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 47662892017872 (LWP 4538)] (no debugging symbols found) 0x00002b595edc6bf4 in waitpid () from /lib64/libpthread.so.0
+ Trace 167895
Thread 1 (Thread 47662892017872 (LWP 4538))
----------- .xsession-errors --------------------- (gnome-panel:4538): Wnck-WARNING **: Property _NET_WM_VISIBLE_NAME contained invalid UTF-8 [FVWM][Echo]: fvwmi StartFunction executed [FVWM][Echo]: fvwmi SessionInitFunction executed (gnome-panel:4538): Wnck-WARNING **: Property _NET_WM_VISIBLE_NAME contained invalid UTF-8 Initializing gnome-mount extension SIOCETHTOOL: Opération non permise SIOCETHTOOL: Opération non permise ** 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 ***