GNOME Bugzilla – Bug 446196
crash in Panel: I saved a page from arch...
Last modified: 2007-06-11 21:31:37 UTC
Version: 2.18.2 What were you doing when the application crashed? I saved a page from archlinux forum "bbs.archlinux.org/viewtopic.php?id=30782" to a file as html complete from firefox. Distribution: Unknown Gnome Release: 2.18.2 2007-05-31 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.21-ARCH #1 SMP PREEMPT Fri Jun 8 20:10:32 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 59461632 vsize: 59461632 resident: 16461824 share: 12439552 rss: 16461824 rss_rlim: 4294967295 CPU usage: start_time: 1181400488 rtime: 445 utime: 384 stime: 61 cutime:0 cstime: 2 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) [Thread debugging using libthread_db enabled] [New Thread -1224939840 (LWP 6021)] (no debugging symbols found) 0xb7f2c410 in __kernel_vsyscall ()
+ Trace 139912
Thread 1 (Thread -1224939840 (LWP 6021))
----------- .xsession-errors --------------------- Initializing gnome-mount extension seahorse nautilus module initialized ** (gimp:6086): CRITICAL **: clearlooks_style_draw_focus: assertion `height >= -1' failed Starting lincity-ng (version 1.1.0)... [/home/rossm/.lincity] is in the search path. [/usr/share/lincity-ng] is in the search path. LINCITY_HOME: /usr/share/lincity-ng SDL Mode 1024x768 warning: .dynamic section for "/usr/lib/libcairo.so.2" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libexpat.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
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 422966 ***