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 510647 - crash in Users and Groups: yet again!
crash in Users and Groups: yet again!
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:37 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:37:52 UTC 
Version: 2.18.0

What were you doing when the application crashed?
yet again!


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: 25612288 vsize: 25612288 resident: 16564224 share: 10850304 rss: 16564224 rss_rlim: 4294967295
CPU usage: start_time: 1200764197 rtime: 185 utime: 162 stime: 23 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)
0xb722196e in waitpid () from /lib/libpthread.so.0

+ Trace 185981

  • #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:18 UTC
        



And Yet again!!!

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 ***