GNOME Bugzilla – Bug 694768
NetworkManager might use different libexecdir than gnome-shell
Last modified: 2013-04-20 05:55:17 UTC
+++ This bug was initially created as a clone of Bug #693590 +++ In openSUSE, for example (debian seems to do similar things), gnome-shell is condifured with configure --libexecdir=/usr/lib/gnome-shell and NetworkManager accordingly with configure --libexecdir=/usr/lib/NetworkManager => gnome-shell fails to understand this and looks for the NM vpn agents in /usr/lib/gnome-shell A patch against gnome-shell was rejected and a fix on NM-pptp proposed (similar patches would be needed for all NM specific VPN modules).
Created attachment 237474 [details] [review] nm-pptp.service: use absolute paths for all helpers
Yeah, this patch makes sense (of course we'd want it for all the vpn types), but I think we should also add a NetworkManager.pc variable as discussed in bug 693590
I agree that the combination of the .pc variable and the absolute paths would be the best indeed... I can create patches for the NM-vpn modules, no problem there... I have on my radar: - pptp (attached) - openconnect - openvpn - strongswan - vpnc Would you prefer one bug each or can I attach them all here?
(In reply to comment #2) > Yeah, this patch makes sense (of course we'd want it for all the vpn types), > but I think we should also add a NetworkManager.pc variable as discussed in bug > 693590 +1 from me on this and 693590
fixed in all VPN modules in master
*** Bug 679225 has been marked as a duplicate of this bug. ***
*** Bug 679212 has been marked as a duplicate of this bug. ***