GNOME Bugzilla – Bug 450332
crash in Panel: I was inserting a networ...
Last modified: 2007-06-26 21:56:22 UTC
Version: 2.18.0 What were you doing when the application crashed? I was inserting a network speed monitor Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 51265536 vsize: 51265536 resident: 23470080 share: 13660160 rss: 23470080 rss_rlim: 4294967295 CPU usage: start_time: 1181420140 rtime: 526 utime: 440 stime: 86 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208363296 (LWP 5584)] (no debugging symbols found) 0x00ded402 in __kernel_vsyscall ()
+ Trace 143106
Thread 1 (Thread -1208363296 (LWP 5584))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libbz2.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libattr.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libacl.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 419622 ***