Bug 487502 – crash in Users and Groups:

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 487502 - crash in Users and Groups:


Summary:	crash in Users and Groups:


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-10-17 13:46 UTC by Vojageros
Modified:	2007-10-17 23:33 UTC

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

Description Vojageros 2007-10-17 13:46:27 UTC

Version: 2.18.0

What were you doing when the application crashed?



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 Wed Aug 1 22:48: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: 115228672 vsize: 115228672 resident: 21078016 share: 13430784 rss: 21078016 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192635492 rtime: 130 utime: 116 stime: 14 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)
0x00002b81eb801ad5 in waitpid () from /lib/libpthread.so.0

+ Trace 170845

#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 ---------------------
(gnome-panel:26761): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:26761): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:26761): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:26761): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:26761): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:26761): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:26761): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:26761): Wnck-WARNING **: Unhandled action type (nil)
--------------------------------------------------

Comment 1 André Klapper 2007-10-17 23:33:28 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 ***