GNOME Bugzilla – Bug 528867
crash in Panel:
Last modified: 2008-04-19 08:46:22 UTC
Version: 2.22.1.2 What were you doing when the application crashed? Distribution: Gentoo Base System release 2.0.0 Gnome Release: 2.22.1 2008-04-18 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.23-gentoo-r9 #3 SMP Tue Mar 11 20:55:27 CET 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Lila Memory status: size: 232157184 vsize: 232157184 resident: 18329600 share: 13221888 rss: 18329600 rss_rlim: 18446744073709551615 CPU usage: start_time: 1208597690 rtime: 112 utime: 96 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' [Thread debugging using libthread_db enabled] [New Thread 0x2af83fb327c0 (LWP 4727)] 0x00002af83d17cf95 in __libc_waitpid (pid=4734, stat_loc=0x7fff74f1b7d0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 195610
Thread 1 (Thread 0x2af83fb327c0 (LWP 4727))
----------- .xsession-errors --------------------- ** (gsynaptics-init:4638): WARNING **: Using synclient ** (nm-applet:4644): WARNING **: <WARN> nma_dbus_update_wireless_enabled_cb(): dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files ** (nautilus:4633): WARNING **: Unable to add monitor: Stöds inte warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff2ddfd000 32 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory. warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff74ffd000 32 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory. --------------------------------------------------
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 527441 ***