Bug 480458 – crash in Network Manager: Looking for wireless net...

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 480458 - crash in Network Manager: Looking for wireless net...


Summary:	crash in Network Manager: Looking for wireless net...


Status:	RESOLVED DUPLICATE of bug 435036

Product:	NetworkManager
Classification:	Platform
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Dan Williams
QA Contact:	Dan Williams

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-26 04:29 UTC by jessopc
Modified:	2007-10-06 18:04 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description jessopc 2007-09-26 04:29:26 UTC

What were you doing when the application crashed?
Looking for wireless networks


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 469266432 vsize: 469266432 resident: 21241856 share: 13398016 rss: 21241856 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190758157 rtime: 750 utime: 650 stime: 100 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nm-applet'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912679091824 (LWP 3078)]
(no debugging symbols found)
0x00002aaab050f89f in waitpid () from /lib64/libpthread.so.0

+ Trace 165540

Thread 1 (Thread 46912679091824 (LWP 3078))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_free
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 gtk_combo_box_set_model
from /usr/lib64/libgtk-x11-2.0.so.0
#4 wso_wpa_eap_new
#5 wsm_set_capabilities
#6 nma_other_network_dialog_run
#7 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#8 g_free
from /lib64/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit
from /lib64/libgobject-2.0.so.0
#11 gtk_widget_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#12 gtk_menu_shell_activate_item
from /usr/lib64/libgtk-x11-2.0.so.0
#13 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#14 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#15 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#16 g_free
from /lib64/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#18 g_signal_emit
from /lib64/libgobject-2.0.so.0
#19 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#20 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#21 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#22 g_free
from /usr/lib64/libgdk-x11-2.0.so.0
#23 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#24 g_free
from /lib64/libglib-2.0.so.0
#25 g_main_loop_run
from /lib64/libglib-2.0.so.0
#26 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#27 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (108 sec old) ---------------------
localuser:jessopc being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2903
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Loading "installonlyn" plugin
** Message: <info>  You are now connected to the wired network.
** Message: <info>  You are now connected to the wired network.
--------------------------------------------------

Comment 1 Susana 2007-10-06 18:04:13 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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