GNOME Bugzilla – Bug 492257
crash in Users and Groups: I was entering a new use...
Last modified: 2007-11-01 12:25:21 UTC
Version: 2.18.0 What were you doing when the application crashed? I was entering a new user settings 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 Group X Vendor Release: 6600 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Human-Graphite Icon Theme: Tango Memory status: size: 110215168 vsize: 110215168 resident: 22282240 share: 12746752 rss: 22282240 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193868254 rtime: 136 utime: 111 stime: 25 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) 0x00002ad659ca0ad5 in waitpid () from /lib/libpthread.so.0
+ Trace 174284
----------- .xsession-errors --------------------- restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window restacking: Warnning unknown next window --------------------------------------------------
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 ***