Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#25465 - [wpa_supplicant] Crashes parsing WPA IE + patch
Attached to Project:
Arch Linux
Opened by Mathijs Kwik (bluescreen303) - Monday, 08 August 2011, 22:16 GMT
Last edited by Thomas Bächler (brain0) - Saturday, 13 October 2012, 20:50 GMT
Opened by Mathijs Kwik (bluescreen303) - Monday, 08 August 2011, 22:16 GMT
Last edited by Thomas Bächler (brain0) - Saturday, 13 October 2012, 20:50 GMT
|
DetailsI couldn't get a connection going with networkmanager, it didn't even scan for nearby APs.
So I looked at the syslog and found that wpa_supplicant crashed every few seconds. So I started wpa_supplicant with -u -d myself to view the debug output. I saw it got wpa_parse_wpa_ie_wpa: ie count botch (pairwise), count 0 left 8 process 5326: arguments to dbus_message_new_error() were incorrect, assertion "reply_to != NULL" failed in file dbus-message.c line 1335 This is normally a bug in some applications using the D-Bus library. D-Bus is not built with -rdynamic so unable to print a backtrace Aborted googling for that error, I ended up at https://bugzilla.redhat.com/show_bug.cgi?id=678625 there is patch attached there, which I applied to the pkgbuild in abs. It applied cleanly, and my problems went away. Can someone please apply this patch officially? Thanks, Mathijs |
This task depends upon
Closed by Thomas Bächler (brain0)
Saturday, 13 October 2012, 20:50 GMT
Reason for closing: Fixed
Additional comments about closing: This is likely fixed in 1.0, if not, please send a reopen request.
Saturday, 13 October 2012, 20:50 GMT
Reason for closing: Fixed
Additional comments about closing: This is likely fixed in 1.0, if not, please send a reopen request.