ifupdown.sh relies on env not available on boot time

Bug #51493 reported by Laurent
4
Affects Status Importance Assigned to Milestone
wpasupplicant (Debian)
Fix Released
Unknown
wpasupplicant (Ubuntu)
Fix Released
Low
Reinhard Tartler

Bug Description

Binary package hint: wpasupplicant

the script /etc/wpa_supplicant/ifupdown.sh uses the command env. Or this command is in /usr/bin which might be not available at boot time. In this case interfaces using wpa_supplicant are not started at boot time

Revision history for this message
Laurent (laurent-goujon) wrote :

Replacing env by set (sh builtin) should fix it

Revision history for this message
Reinhard Tartler (siretart) wrote :

well spottet.
However, since libssl is as well on /usr, fixing this issue wouldn't be sufficient

Changed in wpasupplicant:
importance: Untriaged → Low
status: Unconfirmed → Confirmed
Revision history for this message
kelmo (kelrin) wrote :

Thanks for reporting that Laurent, nice spot.

Changed in wpasupplicant:
status: Unknown → Unconfirmed
Revision history for this message
Reinhard Tartler (siretart) wrote :

fixed in debian, which has already been synced to ubuntu

Changed in wpasupplicant:
assignee: nobody → siretart
status: Confirmed → Fix Released
Changed in wpasupplicant:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.