I spent a bunch of time pulling my hair out on this one this morning,
and I think I have a theory. :-)
I, like Steffen, couldn't get the vpn to fail this morning, no matter what I
did to the policy files. However, if I purged and then re-installed the
packages, the problem returned:
$ sudo dpkg -P network-manager-vpnc vpnc
$ sudo apt-get install network-manager-vpnc vpnc
It seems like installing didn't trigger dbus to re-read the files in
/etc/dbus-1/system.d. Even doing 'sudo touch /etc/dbus-1/system.d'
didn't make it work. If however, I edited this file with vi and saved it
(even without making changes), everything started to work.
At any rate, there's no need to get too hung up on what triggers dbus to
re-read the policy files (although I am curious), since we can just
force this in postinst by adding:
# Force dbus to re-read its config files
if which invoke-rc.d >/dev/null 2>&1; then
invoke-rc.d dbus reload
else
/etc/init.d/dbus reload
fi
Of course the workaround with the current packages is just to reboot,
but that sounds way too much like Windows. :-(
If folks could confirm (or debunk) my theory, I'd appreciate it. If it's
confirmed, I'll put together a debdiff and see if I can get it sponsored
.
** Attachment removed: "nm-vpnc-service.conf.patch"
http://launchpadlibrarian.net/14024435/nm-vpnc-service.conf.patch
--
VPNC / Network-Manager couldn't connect
https://bugs.launchpad.net/bugs/179239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
