Bug 363040 – crash in Networking: Trying to call up networ...

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 363040 - crash in Networking: Trying to call up networ...


Summary:	crash in Networking: Trying to call up networ...


Status:	RESOLVED DUPLICATE of bug 360435

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-18 03:12 UTC by doxland
Modified:	2006-10-18 03:38 UTC

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

Description doxland 2006-10-18 03:12:19 UTC

Version: 2.15.5

What were you doing when the application crashed?
Trying to call up network connection eth1 for config


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

Memory status: size: 32403456 vsize: 0 resident: 32403456 share: 0 rss: 8781824 rss_rlim: 0
CPU usage: start_time: 1161141052 rtime: 0 utime: 9 stime: 0 cutime:7 cstime: 0 timeout: 2 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 -1225939280 (LWP 30916)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 76908

Thread 1 (Thread -1225939280 (LWP 30916))

#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-18 03:38:22 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 360435 ***