This bug was fixed in the package wpasupplicant - 0.6.6-2ubuntu1
---------------
wpasupplicant (0.6.6-2ubuntu1) jaunty; urgency=low
* Operate reasonably when /var is not yet mounted read-write (LP: #44194):
- 07_syslog.patch: Backport syslog logging support from upstream.
- 08_syslog_supplement.patch: Add a few more bits missing from the
upstream patch, based on
http://cvs.fedoraproject.org/viewvc/rpms/wpa_supplicant/OLPC-2/wpa_supplicant-0.5.7-use-syslog.patch.
Compile with -DCONFIG_DEBUG_SYSLOG if CONFIG_DEBUG_SYSLOG is set in
the configuration file.
- Enable CONFIG_DEBUG_SYSLOG.
- debian/ifupdown/functions.sh: Set WPA_SUP_LOGFILE to "syslog" by
default, and use the -s option in this case.
- debian/ifupdown/functions.sh: Silence wpa_log_* if /var/log is not yet
writable; there is little we can do in this case (logger is in /usr,
so may well also be unusable), and the user can always get more
information by reconnecting later.
-- Colin Watson <[email protected]> Thu, 09 Apr 2009 02:31:17 +0100
** Changed in: wpasupplicant (Ubuntu Jaunty)
Status: In Progress => Fix Released
--
wpasupplicant doesn't start when the network start
https://bugs.launchpad.net/bugs/44194
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
