GNOME Bugzilla – Bug 491223
crash in Panel: Opening metisse gnome
Last modified: 2008-03-02 12:38:21 UTC
Version: 2.18.1 What were you doing when the application crashed? Opening metisse gnome Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.18.1 2007-05-04 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-sabayon #1 SMP Wed Aug 1 22:48:31 UTC 2007 x86_64 X Vendor: The X.Org Group X Vendor Release: 6600 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Human-Graphite Icon Theme: Tango Memory status: size: 229744640 vsize: 229744640 resident: 23781376 share: 14581760 rss: 23781376 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193620905 rtime: 62 utime: 56 stime: 6 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) 0x00002b214ba06ad5 in waitpid () from /lib/libpthread.so.0
+ Trace 173545
----------- .xsession-errors --------------------- [FVWM][GetWindowSizeHints]: <<WARNING>> The application window (id 0x1c00323) "Save File" has broken size hints (max_width). fvwm is ignoring those hints. hint override = 0, flags = 234 min_width = 624, min_height = 185, max_width = 497, max_height = 185 width_inc = 497, height_inc = 70 min_aspect = 6469760/0, max_aspect = 8186064/0 base_width = 6005472, base_height = 0 win_gravity = 1 If you are having a problem with the application, send a bug report with this message included to the application owner. There is no need to notify fvwm-workers@fvwm.org. ** ERROR **: file orbit-object.c: line 149 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0) aborting... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 327972 ***
*** Bug 491612 has been marked as a duplicate of this bug. ***
*** Bug 519884 has been marked as a duplicate of this bug. ***