1 Dec 2006 01:02
Bug#385599: madwifi-source: ap_scan seems to be the problem
Carlos Moffat <carlos.lst <at> eldiabloenlosdetalles.net>
2006-12-01 00:02:09 GMT
2006-12-01 00:02:09 GMT
Package: madwifi-source
Followup-For: Bug #385599
Hi Ken,
You've probably noticed I've been all over trying to find a solution for
this. I made a bit of progress today. Following advice from the NM
mailing list, I did:
wpa_supplicant -i ath0 -Dwext -c wpa_supplicant.conf -d
with wpa_supplicant.conf:
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="Atlantic"
key_mgmt=NONE
auth_alg=OPEN
}
The output of this seemed pretty similar to the one obtained by NM.
wpasupplicant would just keep trying to associate, and then keep
scanning. Finally, I decided to try ap_scan=0. Then, wpa_supplicant
would say connected and I could (most times) get an IP using dhclient -1
ath0.
Does this give you any clue why the problem exist in newer versions of
(Continue reading)
Not only does vim lose the unnamed register's content when it is
restarted, but it does so every time one switches between TeX files
(e.g. with :n).
On Thu, Nov 11, 2004 at 07:52:33PM +0100, martin f krafft wrote:
> The bug still exists. Apparently now though it uses the 'a' buffer
> to restore the primary paste buffer.
Same here.
> To reproduce:
>
> echo Hello world > test.tex
> echo Second line >> test.tex
> vim test
> yyj"ayy:q
> vim test
> Gp"ap
I think the procedure above is not suitable to trigger the bug, but
works just like expected -- the second yank command sets the registers
"" and "a.
> This should output "Second line" twice when in fact it should
> duplicate the contents of the file in lines three and four.
RSS Feed