When I try to mount the VPN from NetworkManager I only got an error oct. 26 23:09:04 ivy gnome-shell[1553]: JS LOG: Invalid VPN service type (cannot find authentication binary) oct. 26 23:09:04 ivy gnome-shell[1553]: JS LOG: Invalid VPN service type (cannot find authentication binary) oct. 26 23:09:04 ivy NetworkManager[23294]: <error> [1477516144.9688] vpn-connection[0x56539e16d500,f449b554-222f-4544-975f-dd1bf5f790f7,"XXXXXXXXXX",0]: Failed to request VPN secrets #3: No agents were available for this request. Setting up the VPN in the openfortissl client works fine.
did you install NetworkManager-fortisslvpn-gnome package? Does it work if you use nm-applet?
(In reply to Thomas Haller from comment #1) > did you install NetworkManager-fortisslvpn-gnome package? yes I did. Nevermind today it works, I don't understand why. Meanwhile I just rebooted my workstation. Does nm require specific actions after a plugin is installed (that was not in the packages post-install script) ? Regards
I think gnome-shell loads the VPN plugins in an early phase. If you happen to install the plugin after that, it will not be picked up until you restart gnome-shell. Reassigning.
(In reply to Thomas Haller from comment #3) > I think gnome-shell loads the VPN plugins in an early phase. No, but you are right that plugins are only loaded once (when the first VPN request comes in). We could install a file monitor and invalidate the cache on changes, so we properly pick up installed/uninstalled plugins ...
(In reply to Florian Müllner from comment #4) > (In reply to Thomas Haller from comment #3) > > I think gnome-shell loads the VPN plugins in an early phase. > > No, but you are right that plugins are only loaded once (when the first VPN > request comes in). We could install a file monitor and invalidate the cache > on changes, so we properly pick up installed/uninstalled plugins ... possibly... the plugins consist of a .name file that contains all informations about the plugin. There are also paths to helper programs (e.g. "GNOME.auth-dialog"). Reloading a .name file and the GNOME.auth-dialog is probably fine. But one part are shared libraries (GNOME.properties and libnm.plugin). Once you dlopen these shared library, you cannot dlclose() them and reload them again, because their glib type name will clash. So, at least after doing a dlopen, I think reloading should be prevented. Another note: with new libnm there is now NMVpnPluginInfo which should be preferred over reading the .name file directly: https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/libnm-core/nm-vpn-plugin-info.h?id=0fa2cf19e52167f17dbe43fb1a162ce885f00fc9
(In reply to Thomas Haller from comment #5) > the plugins consist of a .name file that contains all informations about the > plugin. There are also paths to helper programs (e.g. "GNOME.auth-dialog"). > Reloading a .name file and the GNOME.auth-dialog is probably fine. External executables are the only VPN plugins handled by gnome-shell, so the patch on the upstream bug should work. > Another note: with new libnm there is now NMVpnPluginInfo which should be > preferred over reading the .name file directly: > https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/libnm-core/ > nm-vpn-plugin-info.h?id=0fa2cf19e52167f17dbe43fb1a162ce885f00fc9 That looks useful, thanks!
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.