GNOME Bugzilla – Bug 437401
crash in Panel:
Last modified: 2007-05-10 13:49:10 UTC
Version: 2.18.0 What were you doing when the application crashed? 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 Group X Vendor Release: 6600 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Orange Icon Theme: gnome Memory status: size: 33910784 vsize: 33910784 resident: 13922304 share: 10534912 rss: 13922304 rss_rlim: 4294967295 CPU usage: start_time: 1178791037 rtime: 32 utime: 28 stime: 4 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 -1226807616 (LWP 6565)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 133443
Thread 1 (Thread -1226807616 (LWP 6565))
----------- .xsession-errors --------------------- [FVWM][GetWindowSizeHints]: <<WARNING>> The application window (id 0x2a001b0) "Save File" has broken size hints (max_width). fvwm is ignoring those hints. hint override = 0, flags = 234 min_width = 804, min_height = 181, max_width = 595, max_height = 181 width_inc = 181, height_inc = 391 min_aspect = 325/134709424, max_aspect = 364/346 base_width = 181, base_height = 595 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 taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 419622 ***