Bug 888068 - network: gnome-shell should re-register to NM after restarting NetworkManager (else VPN doesn't work)
Summary: network: gnome-shell should re-register to NM after restarting NetworkManager...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-17 23:20 UTC by Cole Robinson
Modified: 2014-02-05 13:58 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 13:58:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Cole Robinson 2012-12-17 23:20:38 UTC
$ rpm -q NetworkManager
NetworkManager-0.9.7.0-9.git20121004.fc18.x86_64

Establishing an openvpn connection works fine, but if you do a 'service NetworkManager restart' (I did it to pick up a change in NetworkManager.conf) any subsequent vpn attempts fail with this in /var/log/messages:

Dec 17 18:19:25 colepc NetworkManager[3019]: <info> Starting VPN service 'openvpn'...
Dec 17 18:19:25 colepc NetworkManager[3019]: <info> VPN service 'openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 18476
Dec 17 18:19:25 colepc NetworkManager[3019]: <info> VPN service 'openvpn' appeared; activating connections
Dec 17 18:19:25 colepc NetworkManager[3019]: <error> [1355786365.585580] [nm-vpn-connection.c:1410] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request.
Dec 17 18:19:25 colepc NetworkManager[3019]: <info> Policy set 'Auto Ethernet' (p14p1) as default for IPv4 routing and DNS.

Comment 1 Peter Robinson 2013-01-02 09:52:28 UTC
I'm seeing the same problem with the vpnc until I reboot the machine. Never use to have to do this.

Jan  2 09:50:24 neo NetworkManager[15701]: <info> Starting VPN service 'vpnc'...
Jan  2 09:50:24 neo NetworkManager[15701]: <info> VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 15910
Jan  2 09:50:24 neo NetworkManager[15701]: <info> VPN service 'vpnc' appeared; activating connections
Jan  2 09:50:24 neo NetworkManager[15701]: <error> [1357120224.429425] [nm-vpn-connection.c:1410] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request.
Jan  2 09:50:29 neo NetworkManager[15701]: <info> VPN service 'vpnc' disappeared

Comment 2 Jirka Klimes 2013-01-08 17:39:00 UTC
The problem is that gnome-shell network secret agent doesn't re-register with NM when it is restarted.

When trying LXDE (where secret-agent is part of nm-applet) everything works.

Comment 3 Tore H. Larsen 2013-02-08 21:35:11 UTC
cc

Comment 4 Arun S A G 2013-04-10 13:49:57 UTC
Is there a workaround?

Comment 5 Fedora End Of Life 2013-12-21 09:57:28 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.

Comment 6 Fedora End Of Life 2014-02-05 13:58:40 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


Note You need to log in before you can comment on or make changes to this bug.