Bug 385589 – crash in Networking:

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 385589 - crash in Networking:


Summary:	crash in Networking:


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-12-13 20:06 UTC by moebius
Modified:	2006-12-13 21:48 UTC

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

Description moebius 2006-12-13 20:06:37 UTC

Version: 2.15.4

What were you doing when the application crashed?



Distribution: Mandriva Linux release 2007.0 (Official) for x86_64
Gnome Release: 2.16.0 2006-09-05 (Mandriva)
BugBuddy Version: 2.16.0

Memory status: size: 90439680 vsize: 90439680 resident: 8093696 share: 6500352 rss: 8093696 rss_rlim: -1
CPU usage: start_time: 1166040376 rtime: 7 utime: 4 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47256432568912 (LWP 7362)]
(no debugging symbols found)
0x00002afabdbc0d35 in waitpid () from /lib64/libpthread.so.0

+ Trace 93919

Thread 1 (Thread 47256432568912 (LWP 7362))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /usr/lib64/libglib-2.0.so.0
#6 g_log
from /usr/lib64/libglib-2.0.so.0
#7 g_assert_warning
from /usr/lib64/libglib-2.0.so.0
#8 oobs_session_get
from /usr/lib64/liboobs-1.so.1
#9 g_type_create_instance
from /usr/lib64/libgobject-2.0.so.0
#10 g_object_set
from /usr/lib64/libgobject-2.0.so.0
#11 g_object_newv
from /usr/lib64/libgobject-2.0.so.0
#12 g_object_new_valist
from /usr/lib64/libgobject-2.0.so.0
#13 g_object_new
from /usr/lib64/libgobject-2.0.so.0
#14 oobs_session_get
from /usr/lib64/liboobs-1.so.1
#15 ??
#16 g_type_create_instance
from /usr/lib64/libgobject-2.0.so.0
#17 g_object_set
from /usr/lib64/libgobject-2.0.so.0
#18 ??
#19 ??
#20 g_object_newv
from /usr/lib64/libgobject-2.0.so.0
#21 g_object_new_valist
from /usr/lib64/libgobject-2.0.so.0
#22 g_object_new
from /usr/lib64/libgobject-2.0.so.0
#23 ??
#24 ??
#25 __libc_start_main
from /lib64/libc.so.6
#26 ??
#27 ??
#28 ??

Comment 1 palfrey 2006-12-13 21:48:30 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 ***