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 510645 - crash in Users and Groups: cannot set up a user thi...
crash in Users and Groups: cannot set up a user thi...
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-19 17:35 UTC by doug
Modified: 2008-01-23 18:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description doug 2008-01-19 17:35:32 UTC 
Version: 2.18.0

What were you doing when the application crashed?
cannot set up a user this is pants!


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: Clearlooks
Icon Theme: gnome

Memory status: size: 26095616 vsize: 26095616 resident: 17022976 share: 10891264 rss: 17022976 rss_rlim: 4294967295
CPU usage: start_time: 1200764025 rtime: 150 utime: 128 stime: 22 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)
0xb71d696e in waitpid () from /lib/libpthread.so.0

+ Trace 185980

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






Comment 1


Carlos Garnacho





          2008-01-23 18:18:00 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 ***