I've reported this bug (with patch included) to the gnome bugzilla. http://bugzilla.gnome.org/show_bug.cgi?id=328390
On Tue, 2006-01-24 at 16:13 +0800, Lachlan Pease wrote: > Okay, interestingly enough, it crashes inside GConf: > > (gdb) run > Starting program: /usr/bin/nm-applet > [Thread debugging using libthread_db enabled] > [New Thread -1224325440 (LWP 19442)] > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread -1224325440 (LWP 19442)] > gconf_unescape_key (escaped_key=0x8249000 <Address 0x8249000 out of > bounds>, len=25) at gconf.c:2747 > 2747 gconf.c: No such file or directory. > in gconf.c > (gdb) bt > #0 gconf_unescape_key (escaped_key=0x8249000 <Address 0x8249000 out of > bounds>, len=25) at gconf.c:2747 > #1 0x08053f61 in nmwa_gconf_info_notify_callback (client=0x808b818, > connection_id=4110417923, entry=0x8239b85, > user_data=0x8095090) at applet.c:2239 > #2 0xb7377a45 in notify_listeners_callback (listeners=0x808bc20, > key=0x821e1d8 > "/system/networking/wireless/networks/[EMAIL PROTECTED]@Library/timestamp", > cnxn_id=136551301, > listener_data=0x80f1fa0, user_data=0xbfacf2f0) at > gconf-client.c:2368 > #3 0xb7366530 in gconf_listeners_notify (listeners=0x808bc20, > all_above=0x821e1d8 > "/system/networking/wireless/networks/[EMAIL PROTECTED]@Library/timestamp", > callback=0xb73779b0 <notify_listeners_callback>, > user_data=0xbfacf2f0) at gconf-listeners.c:588 > #4 0xb7377b55 in notify_one_entry (client=0x808b818, entry=0x82386f0) > at gconf-client.c:2393 > #5 0xb7377d9a in notify_idle_callback (data=0x808b818) at > gconf-client.c:2433 > #6 0xb71fcf21 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0 > #7 0xb71f9cf4 in g_main_context_dispatch () > from /usr/lib/libglib-2.0.so.0 > #8 0xb71fb6a4 in g_main_context_acquire () > from /usr/lib/libglib-2.0.so.0 > #9 0xb71fb9ca in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 > #10 0xb7b70e11 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 > > I'll find what's wrong and post a patch upstream - will link the > bugzilla in here when I've done so. > > On Mon, 2006-01-23 at 22:12 +0800, Lachlan Pease wrote: > > I'm seeing this behaviour too (the exact same - nm-applet crashing and > > then restarting on the appropriate connection status), on my school's > > APs. > > The APs in question are both Apple Airports, named "MKIS ITS" and "MKIS > > Library" - if I get the time tomorrow, I'll do some debugging (against > > an old build, but the cause should be the same). > > > > Regards, > > Lachlan Pease > > > > On Sun, 2006-01-22 at 22:16 -0500, Will Dyson wrote: > > > On 1/22/06, Dan Williams <[EMAIL PROTECTED]> wrote: > > > > On Sun, 2006-01-22 at 21:35 -0500, Will Dyson wrote: > > > > > On 1/20/06, Ian Campbell <[EMAIL PROTECTED]> wrote: > > > > > > A wireless network I use has a space in the essid. Every > > > > > > time > > > > > > NetworkManager tries to associate to it, it crashes. The association > > > > > > succeeds, NetworkManager restarts, and everything continues as it > > > > > > was > > > > > > before. > > > > > > > > > > > > Is there any reason NetworkManager would crash on a network > > > > > > with a > > > > > > space in the essid? > > > > > > > > > > Resend to the list: > > > > > > > > > I also see this behavior, only on networks with a space embedded in > > > > > the ESSID. I'm running a CVS checkout from yesterday (1/21) > > > > > > > > Is there any chance that the problem is a non-UTF8 character rather than > > > > a space? I checked out spaces today with my WRT54G and NM appeared to > > > > deal with them just fine. It's known to crash with some non-UTF8 ESSIDs > > > > though. What's the essid that crashes for you? > > > > > > "dyson homenet" is what it was associating to when the applet was > > > crashing tonight at my parents' place. It didn't appear to be > > > detecting any other networks either. > > > > > > I just realized it was not clear I'm seeing applet crash only, not the > > > networkmanager daemon. > > > > > > When associating to that network, the applet would crash when the > > > association was complete and the icon was about to switch to the > > > "connected, displaying signal strength" mode. The interface remained > > > up, and nothing interesting is reported by the daemon to the syslog. > > > > > > -- > > > Will Dyson > > > _______________________________________________ > > > NetworkManager-list mailing list > > > [email protected] > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > _______________________________________________ > > NetworkManager-list mailing list > > [email protected] > > http://mail.gnome.org/mailman/listinfo/networkmanager-list _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
