GNOME Bugzilla – Bug 499324
crash in Users and Groups: Installed sabayon 86_64f...
Last modified: 2007-11-24 12:44:54 UTC
Version: 2.18.0 What were you doing when the application crashed? Installed sabayon 86_64f DVD; could not logon as normal user, so logged on as root & tried to create a user. I left the user id (?) at its default (0), clicked to create the user and the program crashed. 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: 109637632 vsize: 109637632 resident: 21671936 share: 12738560 rss: 21671936 rss_rlim: 18446744073709551615 CPU usage: start_time: 1195884139 rtime: 58 utime: 45 stime: 13 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) 0x00002ba17e921ad5 in waitpid () from /lib/libpthread.so.0
+ Trace 179447
----------- .xsession-errors (65 sec old) --------------------- MNG error 11: Function is invalid at this point; chunk vpAg; subcode 0:0 MNG error 11: Function is invalid at this point; chunk vpAg; subcode 0:0 Loading socket FrontEnd module ... Starting SCIM as daemon ... Loading socket Config module ... Creating backend ... Loading x11 FrontEnd module ... Starting SCIM as daemon ... SCIM has been successfully launched. X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2e00003 (users-admin:24441): 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 ***