Bug 455765 – crash in Users and Groups: I was adding user

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 455765 - crash in Users and Groups: I was adding user


Summary:	crash in Users and Groups: I was adding user


Status:	RESOLVED DUPLICATE of bug 425062

Product:	gnome-system-tools
Classification:	Deprecated
Component:	users-admin
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Carlos Garnacho
QA Contact:	Carlos Garnacho

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-11 01:41 UTC by greg108
Modified:	2007-07-11 09:45 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description greg108 2007-07-11 01:41:57 UTC

Version: 2.18.0

What were you doing when the application crashed?
I was adding user


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.21-sabayon-r2 #1 SMP Sun Jun 24 20:31:31 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: 110399488 vsize: 110399488 resident: 22409216 share: 12718080 rss: 22409216 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184117783 rtime: 87 utime: 87 stime: 0 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)
0x00002b6de1e93ad5 in waitpid () from /lib/libpthread.so.0

+ Trace 147154

#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 ---------------------
  Resource id:  0x3a002e3
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x3a002e3
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x3a002e3
(users-admin:12184): Liboobs-WARNING **: There was an unknown error communicating with the backends: Process /usr/bin/system-tools-backends exited with status 0
(users-admin:12184): Liboobs-WARNING **: There was an unknown error communicating with the backends: Process /usr/bin/system-tools-backends exited with status 0
(users-admin:12184): Liboobs-WARNING **: There was an unknown error communicating with the backends: Message did not receive a reply (timeout by message bus)
--------------------------------------------------

Comment 1 Damien Durand 2007-07-11 09:45:08 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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