Bug 398764 – crash in Users and Groups: Abrir sistema, administr...

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 398764 - crash in Users and Groups: Abrir sistema, administr...


Summary:	crash in Users and Groups: Abrir sistema, administr...


Status:	RESOLVED DUPLICATE of bug 350758

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-20 16:31 UTC by jparrondo
Modified:	2007-01-20 17:00 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description jparrondo 2007-01-20 16:31:08 UTC

Version: 2.15.5

What were you doing when the application crashed?
Abrir sistema, administracion, usuarios y grupos


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 19521536 vsize: 0 resident: 19521536 share: 0 rss: 7110656 rss_rlim: 0
CPU usage: start_time: 1169310630 rtime: 0 utime: 13 stime: 0 cutime:11 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/users-admin'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226032752 (LWP 6690)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 103805

Thread 1 (Thread -1226032752 (LWP 6690))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_type_instance_get_private
from /usr/lib/liboobs-1.so.2
#5 oobs_session_get
from /usr/lib/liboobs-1.so.2
#6 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#7 g_object_set
from /usr/lib/libgobject-2.0.so.0
#8 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#9 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_object_new
from /usr/lib/libgobject-2.0.so.0
#11 oobs_session_get
from /usr/lib/liboobs-1.so.2
#12 ??
#13 ??
from /usr/lib/libgobject-2.0.so.0
#14 ??
#15 ??
#16 g_object_connect
from /usr/lib/libgobject-2.0.so.0
#17 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#18 g_object_set
from /usr/lib/libgobject-2.0.so.0
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
from /usr/lib/libgobject-2.0.so.0
#24 ??
#25 ??
#26 ??
#27 ??
from /usr/lib/libgobject-2.0.so.0
#28 ??
#29 ??
#30 ??
#31 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#32 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#33 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#34 g_object_new
from /usr/lib/libgobject-2.0.so.0
#35 ??
#36 ??
#37 _IO_stdin_used
#38 _IO_stdin_used
#39 _IO_stdin_used
#40 ??
#41 _IO_stdin_used
#42 _IO_stdin_used
#43 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-01-20 17:00:23 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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