GNOME Bugzilla – Bug 492750
crash in Network Manager:
Last modified: 2007-11-02 16:43:41 UTC
What were you doing when the application crashed? Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-10-30 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-gentoo-r9 #5 SMP Wed Oct 31 23:53:23 WET 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 281026560 vsize: 281026560 resident: 30035968 share: 25800704 rss: 30035968 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194020728 rtime: 27 utime: 24 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nm-applet' (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 47637836792448 (LWP 5655)] 0x00002b5389a5daef in waitpid () from /lib/libpthread.so.0
+ Trace 174646
Thread 1 (Thread 47637836792448 (LWP 5655))
----------- .xsession-errors (13 sec old) --------------------- /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/X11/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0" "tkoh" /etc/X11/gdm/Xsession: Beginning session setup... /etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session SESSION_MANAGER=local/gena:/tmp/.ICE-unix/5605 (gnome-session:5605): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** (gnome-session:5605): WARNING **: Host name lookup failure on localhost. Initializing gnome-mount extension (gnome-panel:5646): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 --------------------------------------------------
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 435036 ***