On Wed, 2007-03-28 at 19:54 +1200, Simon Geard wrote:
> On Tue, 2007-03-27 at 14:49 +0300, Tambet Ingo wrote:
> > Can you debug it and see why and where it aborts? It's been working
> > fine for me and Dan for the whole time so it's not going to get
> > magically fixed unless we know what's going on.
>
> My C debugging skills are a little rusty, but I'll see what I can
> find...
Ok, I don't think this is the problem I saw last time, but the current
failure is that in real_write_supplicant_config(), the call to
nm_ap_security_get_key() is returning NULL, causing a segmentation fault
on the call to strlen() on line 162.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1212537152 (LWP 27036)]
0xb7c321d3 in strlen () from /lib/libc.so.6
(gdb) bt
#0 0xb7c321d3 in strlen () from /lib/libc.so.6
#1 0x08070748 in real_write_supplicant_config (instance=0x809c4c0,
config=0x80c1740, adhoc=0)
at nm-ap-security-wpa-psk.c:162
#2 0x0805cb25 in real_act_stage2_config (dev=0x80c0088, req=0x80bf7c8)
at nm-device-802-11-wireless.c:2705
The reason for the NULL appears to be that nothing has ever called
nm_ap_security_set_key(). Is this a consequence of the nm-applet issues
you mentioned? I'm not manually doing anything, but I assume the applet
is what's telling NM to actually connect to my AP...
Interestingly, a message printed out a little earlier indicates it
thinks my AP is unencrypted, which is not the case. Could that be
relevant?
NetworkManager: <info> Activation (ath0/wireless): access point 'XXXXX'
is unencrypted, no key needed.
Simon.
Attachment:
signature.asc
Description: This is a digitally signed message part