Bug 437369 – crash in Network Manager: Attempting to 'connect t...

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 437369 - crash in Network Manager: Attempting to 'connect t...


Summary:	crash in Network Manager: Attempting to 'connect t...


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-05-10 07:21 UTC by john
Modified:	2007-05-12 12:30 UTC

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

Description john 2007-05-10 07:21:58 UTC

What were you doing when the application crashed?
Attempting to 'connect to other networks' after launching the network manager


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

System: Linux 2.6.21-1.3116.fc7 #1 SMP Thu Apr 26 10:17:55 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 374976512 vsize: 374976512 resident: 16203776 share: 10760192 rss: 16203776 rss_rlim: 18446744073709551615
CPU usage: start_time: 1178781632 rtime: 49 utime: 40 stime: 9 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 46912496347072 (LWP 3579)]
(no debugging symbols found)
0x0000003ed7a0d83f in waitpid () from /lib64/libpthread.so.0

+ Trace 133420

Thread 1 (Thread 46912496347072 (LWP 3579))

#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 (11 sec old) ---------------------
localuser:john being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3425
compiz: No stencil buffer. Clipping of transformed windows is not going to be correct when screen is transformed.
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: <info>  Creating network 'jt' on device '/org/freedesktop/NetworkManager/Devices/wlan0'.
--------------------------------------------------

Comment 1 Susana 2007-05-12 12:30:46 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 435036 ***