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


Summary:	crash in Networking:


Status:	RESOLVED DUPLICATE of bug 354536

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:

Duplicates:	401089 401090 401092 (view as bug list)
Depends on:
Blocks:

Reported:	2007-01-26 18:20 UTC by lince74
Modified:	2007-01-26 21:44 UTC

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

Description lince74 2007-01-26 18:20:28 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: 34254848 vsize: 0 resident: 34254848 share: 0 rss: 11804672 rss_rlim: 0
CPU usage: start_time: 1169835602 rtime: 0 utime: 36 stime: 0 cutime:34 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 -1225045744 (LWP 5438)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 105477

Thread 1 (Thread -1225045744 (LWP 5438))

#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_slice_free_chain_with_offset
from /usr/lib/libglib-2.0.so.0
#5 g_list_free
from /usr/lib/libglib-2.0.so.0
#6 ??
#7 ??
#8 gtk_combo_box_set_active_iter
#9 ??
#0 __kernel_vsyscall

Comment 1 Damien Durand 2007-01-26 21:42:39 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 354536 ***

Comment 2 Damien Durand 2007-01-26 21:43:28 UTC

*** Bug 401089 has been marked as a duplicate of this bug. ***

Comment 3 Damien Durand 2007-01-26 21:43:58 UTC

*** Bug 401090 has been marked as a duplicate of this bug. ***

Comment 4 Damien Durand 2007-01-26 21:44:25 UTC

*** Bug 401092 has been marked as a duplicate of this bug. ***