After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728564 - NetworkManager-vpnc does not work with passwords stored in gnome-keyring
NetworkManager-vpnc does not work with passwords stored in gnome-keyring
Status: RESOLVED DUPLICATE of bug 728681
Product: NetworkManager
Classification: Platform
Component: VPN: vpnc
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-04-19 17:23 UTC by fabian.schmid
Modified: 2014-05-01 13:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description fabian.schmid 2014-04-19 17:23:32 UTC
NetworkManager fails to activate vpnc connections when using "Saved" passwords. The credentials are successfully stored in the gnome-keyring but activating the connection yields:

Apr 19 19:17:32 VAIO NetworkManager[395]: <info> Starting VPN service 'vpnc'...
Apr 19 19:17:32 VAIO NetworkManager[395]: <info> VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 3417
Apr 19 19:17:32 VAIO NetworkManager[395]: <info> VPN service 'vpnc' appeared; activating connections
Apr 19 19:17:32 VAIO NetworkManager[395]: <error> [1397927852.558253] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request.
Apr 19 19:17:38 VAIO NetworkManager[395]: <info> VPN service 'vpnc' disappeared

Steps to Reproduce:
1) Add a vpnc network connection in the "Network" settings dialog using "Saved" passwords
2) Enable the connection

Actual Results:
The connections switches off immediately and an error is logged (see above).

Expected Results:
The vpnc connection being active.

Additional Information:
Arch Linux
networkmanager-vpnc 0.9.8.6-1
networkmanager 0.9.8.8-3
gnome-keyring 3.12.0-1
Comment 1 Danny Wood 2014-04-24 11:12:05 UTC
This bug effects me also (Also running Arch).

Version information (differs slightly):
networkmanager-vpnc 0.9.8.6-1
networkmanager 0.9.8.9-1
gnome-keyring 3.12.0-1

Storing VPN passwords via the keyring worked fine in Gnome 3.10 but since the resent upgrade to 3.12 I have been unable to connect to my VPN with stored passwords (entering the passwords manually works fine).

Log from the journal after failed VPN attempt:

Apr 24 11:47:34 danny-arch NetworkManager[406]: <info> Starting VPN service 'vpnc'...
Apr 24 11:47:34 danny-arch NetworkManager[406]: <info> VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 1171
Apr 24 11:47:34 danny-arch NetworkManager[406]: <info> VPN service 'vpnc' appeared; activating connections
Apr 24 11:47:34 danny-arch gnome-session[528]: (gnome-shell:649): Gjs-WARNING **: JS ERROR: error while reading VPN plugin output keyfile: GLib.KeyFileError: Key file does not have group 'VPN Plugin UI'
Apr 24 11:47:34 danny-arch gnome-session[528]: VPNRequestHandler<._showNewStyleDialog@resource:///org/gnome/shell/ui/components/networkAgent.js:520
Apr 24 11:47:34 danny-arch gnome-session[528]: wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Apr 24 11:47:34 danny-arch gnome-session[528]: VPNRequestHandler<._readStdoutNewStyle/<@resource:///org/gnome/shell/ui/components/networkAgent.js:499
Apr 24 11:47:34 danny-arch NetworkManager[406]: <error> [1398336454.623653] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request.
Apr 24 11:47:34 danny-arch gnome-session[528]: Window manager warning: Log level 16: AT-SPI: Error in GetItems, sender=org.freedesktop.DBus, error=The name :1.11 was not provided by any .service files
Apr 24 11:47:39 danny-arch NetworkManager[406]: <info> VPN service 'vpnc' disappeared
Comment 2 jack gurulian 2014-04-27 10:55:44 UTC
I am affected by this issue as well. Happened both on Fedora (after upgrading from Gnome 3.10) and on Arch Linux (after a clean installation).
Comment 3 Dan Winship 2014-05-01 13:00:26 UTC

*** This bug has been marked as a duplicate of bug 728681 ***