Bug 360784 – 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 360784 - crash in Networking:


Summary:	crash in Networking:


Status:	RESOLVED DUPLICATE of bug 360781

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-10-08 23:47 UTC by nicholas
Modified:	2006-10-08 23:54 UTC

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

Description nicholas 2006-10-08 23:47:51 UTC

Version: 2.15.5

What were you doing when the application crashed?



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

Memory status: size: 31981568 vsize: 0 resident: 31981568 share: 0 rss: 8527872 rss_rlim: 0
CPU usage: start_time: 1160351264 rtime: 0 utime: 9 stime: 0 cutime:9 cstime: 0 timeout: 0 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 -1225546064 (LWP 5307)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75343

Thread 1 (Thread -1225546064 (LWP 5307))

#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 ??
from /usr/lib/liboobs-1.so.2
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#0 __kernel_vsyscall

Comment 1 Elijah Newren 2006-10-08 23:54:20 UTC

Hi, you don't need to report this one again.

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