Bug 355037 – crash in Networking: started 'network-admin'

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 355037 - crash in Networking: started 'network-admin'


Summary:	crash in Networking: started 'network-admin'


Status:	RESOLVED DUPLICATE of bug 350758

Product:	gnome-system-tools
Classification:	Deprecated
Component:	network-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:	2006-09-09 01:07 UTC by daniel.amendoeira
Modified:	2006-09-09 06:44 UTC

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

Description daniel.amendoeira 2006-09-09 01:07:46 UTC

Version: 2.15.4

What were you doing when the application crashed?
started 'network-admin'


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 18808832 vsize: 0 resident: 18808832 share: 0 rss: 6995968 rss_rlim: 0
CPU usage: start_time: 1157764017 rtime: 0 utime: 3 stime: 0 cutime:2 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/network-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 -1225492816 (LWP 4864)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71928

Thread 1 (Thread -1225492816 (LWP 4864))

#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 __kernel_vsyscall
#5 *__GI_raise
from /lib/tls/i686/cmov/libc.so.6
#6 *__GI_abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 oobs_session_get
from /usr/lib/liboobs-1.so.1
#11 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#12 g_object_set
from /usr/lib/libgobject-2.0.so.0
#13 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#14 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_object_new
from /usr/lib/libgobject-2.0.so.0
#16 oobs_session_get
from /usr/lib/liboobs-1.so.1
#17 ??
#18 ??
from /usr/lib/libgobject-2.0.so.0
#19 ??
#20 ??
#21 g_object_connect
from /usr/lib/libgobject-2.0.so.0
#22 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#23 g_object_set
from /usr/lib/libgobject-2.0.so.0
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
from /usr/lib/libgobject-2.0.so.0
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 g_malloc
from /usr/lib/libglib-2.0.so.0
#0 __kernel_vsyscall

Comment 1 Fabio Bonelli 2006-09-09 06:44:52 UTC

Thanks for the bug report. 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?


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