Bug 374059 – crash in Networking: Wireless signal lost so ...

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 374059 - crash in Networking: Wireless signal lost so ...


Summary:	crash in Networking: Wireless signal lost so ...


Status:	RESOLVED INCOMPLETE

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-11-11 22:27 UTC by steve.duckworth
Modified:	2007-03-24 00:04 UTC

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

Description steve.duckworth 2006-11-11 22:27:21 UTC

Version: 2.15.5

What were you doing when the application crashed?
Wireless signal lost so went to System >Administration > Networking Tools. Devices showed ra0 Link Speed as 1Mbps so clicked configure which sometimes, without doing anything other than closing it again, restores the Link Speed.




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

Memory status: size: 59281408 vsize: 0 resident: 59281408 share: 0 rss: 13344768 rss_rlim: 0
CPU usage: start_time: 1163283714 rtime: 0 utime: 70 stime: 0 cutime:65 cstime: 0 timeout: 5 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 -1225959760 (LWP 5553)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 85583

Thread 1 (Thread -1225959760 (LWP 5553))

#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_list_prepend
from /usr/lib/libglib-2.0.so.0
#6 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#7 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#8 g_object_new
from /usr/lib/libgobject-2.0.so.0
#9 spi_text_interface_new
from /usr/lib/libspi.so.0
#10 spi_accessible_construct
from /usr/lib/libspi.so.0
#11 spi_accessible_new
from /usr/lib/libspi.so.0
#12 gnome_accessibility_module_shutdown
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#13 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#16 gail_tree_view_new
from /usr/lib/gtk-2.0/modules/libgail.so
#17 _gtk_marshal_VOID__BOXED_BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 gtk_tree_model_row_inserted
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_list_store_insert
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_list_store_append
from /usr/lib/libgtk-x11-2.0.so.0
#25 ??
#26 ??
#27 ??
#28 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-02-21 18:37:47 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.
Thanks in advance!

Comment 2 Bruno Boaventura 2007-03-24 00:04:18 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!