This bug was fixed in the package openvpn - 2.1~rc11-1ubuntu2
---
openvpn (2.1~rc11-1ubuntu2) intrepid; urgency=low
* debian/openvpn.init.d:
- Revert fix from #454371 that was merged at 2.1~rc7-4 to prevent
openvpn prompts from blocking the boot (LP: #280428)
- Fix VPN
Proposed fix
Also includes a fix for VPNs always reported as starting [ OK ] (log_end_msg
sent too early)
openvpn (2.1~rc11-1ubuntu2) intrepid; urgency=low
* debian/openvpn.init.d:
- Revert fix from #454371 that was merged at 2.1~rc7-4 to prevent
openvpn prompts from blocking the boo
I agree, and I realized that the problem persists for users upgrading to
Intrepid and using OpenVPN (I mean, the behaviour has not been changed
yet): I upgraded from Hardy to Intrepid on another machine and had to
remove OpenVPN from the autostarted-at-boot apps list. I also realized,
while still u
This should probably be considered as a bug.
** Changed in: openvpn (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Thierry Carrez (tcarrez)
Status: Invalid => Confirmed
--
Prompted for VPN (openvpn) user info at boot-up
https://bugs.launchpad.net/bugs/280428
Yo
Though the right solution is to do some /etc/default/openvpn
configuration (see related answer), it might be a good idea to preserve
hardy's behavior in that case.
This difference in behavior was introduced when we merged the fix for the
following Debian bug :
http://bugs.debian.org/cgi-bin/bugre
Indeed, this might be the case: "the reporter is confused, and an
explanation is needed." Thanks in advance!
** Changed in: openvpn (Ubuntu)
Status: New => Invalid
** bug changed to question:
https://answers.launchpad.net/ubuntu/+source/openvpn/+question/47501
--
Prompted for VPN (ope
