Bug 466304 – crash in Network Manager: Trying to "Connect to ot...

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 466304 - crash in Network Manager: Trying to "Connect to ot...


Summary:	crash in Network Manager: Trying to "Connect to ot...


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-08-13 17:10 UTC by screening4ashes
Modified:	2007-10-06 18:03 UTC

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

Description screening4ashes 2007-08-13 17:10:21 UTC

What were you doing when the application crashed?
Trying to "Connect to other wireless networks"


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.2 2007-08-13 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-gentoo-r2 #2 SMP PREEMPT Sun Aug 12 20:43:30 CDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 230526976 vsize: 230526976 resident: 33161216 share: 27627520 rss: 33161216 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187027886 rtime: 52 utime: 49 stime: 3 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46943099424896 (LWP 23275)]
0x00002ab1c854b53e in waitpid () from /lib/libpthread.so.0

+ Trace 154915

Thread 1 (Thread 46943099424896 (LWP 23275))

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



----------- .xsession-errors (13 sec old) ---------------------
** (nm-applet:23275): WARNING **: <WARN>  nma_dbus_init(): org.freedesktop.DBus.Error.FileNotFound raised:
 Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
** (nm-applet:23275): WARNING **: <WARN>  nma_dbus_init(): org.freedesktop.DBus.Error.FileNotFound raised:
 Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
** 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:03:11 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 ***