After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 511152 - crash in Users and Groups: Creating a user
crash in Users and Groups: Creating a user
Status: RESOLVED DUPLICATE of bug 425062
Product: gnome-system-tools
Classification: Deprecated
Component: users-admin
2.18.x
Other All
: High critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
Depends on:
Blocks:
 
 
Reported: 2008-01-22 00:42 UTC by Mario Wilson
Modified: 2008-01-23 18:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Mario Wilson 2008-01-22 00:42:52 UTC 
Version: 2.18.0

What were you doing when the application crashed?
Creating a user


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.1 2007-05-01 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-sabayon #1 SMP Fri Aug 31 22:28:10 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Human-Graphite
Icon Theme: Tango

Memory status: size: 26169344 vsize: 26169344 resident: 17215488 share: 11022336 rss: 17215488 rss_rlim: 4294967295
CPU usage: start_time: 1202326982 rtime: 385 utime: 331 stime: 54 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)
0xb720896e in waitpid () from /lib/libpthread.so.0

+ Trace 186268

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 ??
  • #3 ??
  • #4 ?? 


----------- .xsession-errors (227 sec old) ---------------------
$UI not set defaulting to swt
--------------------------------------------------
Comment 1 Carlos Garnacho 2008-01-23 18:18:54 UTC 
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 ***