GNOME Bugzilla – Bug 479628
crash in Users and Groups: adding a user and creati...
Last modified: 2007-09-24 01:32:26 UTC
Version: 2.18.0 What were you doing when the application crashed? adding a user and creating shell path 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: 70000000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 110211072 vsize: 110211072 resident: 22372352 share: 12754944 rss: 22372352 rss_rlim: 18446744073709551615 CPU usage: start_time: 1190581925 rtime: 103 utime: 84 stime: 19 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) 0x00002b6788ba6ad5 in waitpid () from /lib/libpthread.so.0
+ Trace 164927
----------- .xsession-errors (6 sec old) --------------------- intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer setParam(pad.cpp:303) --- setParam setParam(pad.cpp:304) --- NOT YET THREAD SAFE! intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer setParam(pad.cpp:303) --- setParam setParam(pad.cpp:304) --- NOT YET THREAD SAFE! intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer intVerToStrVer(pad.cpp:96) --- intVerToStrVer --------------------------------------------------
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 ***