NetworkManager and "illegal" SSID chars = crash?

Matthew Miller mattdm at
Thu Sep 6 04:40:50 UTC 2007

On Wed, Sep 05, 2007 at 01:00:44PM -0400, Dan Williams wrote:
> Definitely.  Can you get a backtrace of where it's crashing?  It should
> dump output to /var/log/messages, including a backtrace.  If that
> doesn't work, maybe hooking up to it with gdb would help.

Here's the gdb backtrace from nm-applet:

Starting program: /usr/bin/nm-applet 
[Thread debugging using libthread_db enabled]
[New process 2148]
[New Thread -1208629488 (LWP 2148)]
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/ea/8072ce47bbe621338d7d78b5a928669ed731f1.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/43/f019db05b32979c7605a988adb185caa653649.debug

Program received signal SIGABRT, Aborted.
[Switching to Thread -1208629488 (LWP 2148)]
0x0012d402 in __kernel_vsyscall ()
#0  0x0012d402 in __kernel_vsyscall ()
#1  0x00d46150 in *__GI_raise (sig=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2  0x00d47a51 in *__GI_abort () at abort.c:88
#3  0x00be7db5 in _dbus_abort () at dbus-sysdeps.c:86
#4  0x00be3a46 in _dbus_warn_check_failed (
    format=0xbf07a0 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:283
#5  0x00bd7980 in dbus_message_new_method_call (
    destination=0x806b2b8 "org.freedesktop.NetworkManager", 
    path=0x88a3ad0 "/org/freedesktop/NetworkManager/Devices/wlan0/Networks/http_3a_//mattdm_2e_org/wifi", 
    interface=0x806b620 "org.freedesktop.NetworkManager.Devices", 
    method=0x806b41d "getProperties") at dbus-message.c:1071
#6  0x080572f7 in nma_dbus_device_update_one_network (applet=0x8652020, 
    dev_path=0x88a7004 "/org/freedesktop/NetworkManager/Devices/wlan0", 
    net_path=0x0, active_net_path=0x88a7100 "") at applet-dbus-devices.c:630
#7  0x0805842d in nma_dbus_device_properties_cb (pcall=0x878ece8, 
    user_data=0x8652020) at applet-dbus-devices.c:831
#8  0x00bd9751 in _dbus_pending_call_complete (pending=0x878ece8)
    at dbus-pending-call.c:198
#9  0x00bc9773 in complete_pending_call_and_unlock (connection=0x8789220, 
    pending=0x878ece8, message=<value optimized out>) at dbus-connection.c:2170
#10 0x00bcb369 in dbus_connection_dispatch (connection=0x8789220)
    at dbus-connection.c:4296
#11 0x009fee7d in message_queue_dispatch (source=0x878b238, callback=0, 
    user_data=0x0) at dbus-gmain.c:101
#12 0x00c6817c in IA__g_main_context_dispatch (context=0x861b8f8)
    at gmain.c:2061
#13 0x00c6b5bf in g_main_context_iterate (context=0x861b8f8, block=1, 
    dispatch=1, self=0x85f8498) at gmain.c:2694
#14 0x00c6b969 in IA__g_main_loop_run (loop=0x8650930) at gmain.c:2898
#15 0x0074e714 in IA__gtk_main () at gtkmain.c:1144
#16 0x0804efa1 in main (argc=Cannot access memory at address 0x864
) at main.c:67
#17 0x00d330f0 in __libc_start_main (main=0x804ee80 <main>, argc=1, 
    ubp_av=0xbf95a974, init=0x8069340 <__libc_csu_init>, 
    fini=0x8069330 <__libc_csu_fini>, rtld_fini=0x11e560 <_dl_fini>, 
    stack_end=0xbf95a96c) at libc-start.c:220
#18 0x0804edc1 in _start ()

Matthew Miller           mattdm at          <>
Boston University Linux      ------>              <>

More information about the fedora-devel-list mailing list