GNOME Bugzilla – Bug 475219
crash in Panel: ajouter wallpaper tray p...
Last modified: 2007-09-09 20:30:08 UTC
Version: 2.18.3 What were you doing when the application crashed? ajouter wallpaper tray pour barre gnome ! Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 313286656 vsize: 313286656 resident: 33075200 share: 24039424 rss: 33075200 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189363728 rtime: 209 utime: 179 stime: 30 cutime:0 cstime: 1 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 46912496335280 (LWP 2833)] (no debugging symbols found) 0x00000031d8c0d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 161603
Thread 1 (Thread 46912496335280 (LWP 2833))
----------- .xsession-errors --------------------- (gnome-panel:2833): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x6bc860 (gnome-panel:2833): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x6bc860 (gnome-panel:2833): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x6bc860 21:36:16 : Getting packages : installed 21:36:16 : Found 1 installed packages 21:36:16 : Getting packages : available 21:36:16 : Found 1 available packages 21:36:16 : Sorting packages 21:36:16 : Population view with packages 21:36:16 : Population Completed ** ERROR **: file orbit-object.c: line 159 (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 ***