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 469726 - crash in Users and Groups: Try to add one useraccou...
crash in Users and Groups: Try to add one useraccou...
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: 2007-08-23 21:30 UTC by kpstaack
Modified: 2007-09-05 21:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description kpstaack 2007-08-23 21:30:34 UTC 
Version: 2.18.0

What were you doing when the application crashed?
Try to add one useraccount


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 Sat Jul 21 08:41:12 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: 110268416 vsize: 110268416 resident: 22290432 share: 12746752 rss: 22290432 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187886446 rtime: 103 utime: 79 stime: 24 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)
0x00002ac82512fad5 in waitpid () from /lib/libpthread.so.0

+ Trace 157470

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strlen
    from /lib/libc.so.6
  • #4 ??
    from /usr/lib/libdbus-1.so.3
  • #5 ??
    from /usr/lib/libdbus-1.so.3
  • #6 dbus_message_iter_append_basic
    from /usr/lib/libdbus-1.so.3
  • #7 ??
    from /usr/lib/liboobs-1.so.3
  • #8 ??
    from /usr/lib/liboobs-1.so.3
  • #9 oobs_object_commit
    from /usr/lib/liboobs-1.so.3
  • #10 on_user_new_clicked
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #26 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #30 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #31 ??
    from /usr/lib/libglib-2.0.so.0
  • #32 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #33 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 main 


----------- .xsession-errors (132 sec old) ---------------------
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:  0x2e0033d
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x2e00007
(users-admin:9778): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus)
--------------------------------------------------
Comment 1 Carlos Garnacho 2007-09-05 21:52:33 UTC 

*** This bug has been marked as a duplicate of 425062 ***