GNOME Bugzilla – Bug 504637
crash in Users and Groups: Added a user
Last modified: 2007-12-23 19:57:14 UTC
Version: 2.18.0 What were you doing when the application crashed? Added a user Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.18.1 2007-05-04 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-sabayon #1 SMP Mon Sep 3 00:33:06 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 112357376 vsize: 112357376 resident: 19398656 share: 13131776 rss: 19398656 rss_rlim: 18446744073709551615 CPU usage: start_time: 1198179105 rtime: 91 utime: 80 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/users-admin' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) 0x00002ae2e0008ad5 in waitpid () from /lib/libpthread.so.0
+ Trace 182421
----------- .xsession-errors (236 sec old) --------------------- SESSION_MANAGER=local/pundit-x86-64:/tmp/.ICE-unix/9740 (nm-applet:9805): Gtk-CRITICAL **: gtk_tooltips_set_tip: assertion `widget != NULL' failed (nm-applet:9805): Gtk-CRITICAL **: gtk_image_set_from_pixbuf: assertion `GTK_IS_IMAGE (image)' failed (gnome-panel:9794): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 You can not run beagle as root. Beagle is designed to run from your own user account. If you want to create multiuser or system-wide indexes, use the beagle-build-index tool. You can override this setting using the beagle-config or beagle-settings tools. Initializing gnome-mount extension (users-admin:9857): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus) --------------------------------------------------
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 425062 ***