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


Summary:	crash in Networking:


Status:	RESOLVED FIXED

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:	379136 (view as bug list)
Depends on:
Blocks:

Reported:	2006-11-25 14:13 UTC by msn4us
Modified:	2008-01-08 00:30 UTC

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

Description msn4us 2006-11-25 14:13: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: 28139520 vsize: 0 resident: 28139520 share: 0 rss: 11624448 rss_rlim: 0
CPU usage: start_time: 1164214424 rtime: 0 utime: 39 stime: 0 cutime:37 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 -1225169232 (LWP 12021)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 89257

Thread 1 (Thread -1225169232 (LWP 12021))

#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_alloc
from /usr/lib/libglib-2.0.so.0
#5 g_slice_alloc0
from /usr/lib/libglib-2.0.so.0
#6 g_list_alloc
from /usr/lib/libglib-2.0.so.0
#7 g_object_notify
from /usr/lib/libgobject-2.0.so.0
#8 gtk_widget_set_sensitive
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
#10 ??
#11 ??
#12 ??
#0 __kernel_vsyscall

Comment 1 Don Scorgie 2006-11-25 18:46:53 UTC

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

Comment 2 Jens Granseuer 2006-11-25 19:35:33 UTC

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

Comment 3 André Klapper 2007-10-29 01:24:10 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 4 Carlos Garnacho 2008-01-08 00:30:11 UTC

No new reports since 2.15.x, I think it's the same memory corruption than the one in bug #357730.