Hide Forgot
Description of problem: Removal of ConsoleKit support from xinit (ck-xinit-session) caused NetworkManager to not allow use of any password-protected connection. As result, unless ck-launch-session is run manually, on F17/Rawhide machines one cannot use protected WiFi or VPN connections. https://bugzilla.redhat.com/show_bug.cgi?id=786157 is a similar bug for kdm case. https://bugzilla.gnome.org/show_bug.cgi?id=666783 is upstream bug for CK removal. It also contains the patch that was committed upstream to allow selecting systemd session provider. Please consider updating and rebuilding NetworkManager for F17/Rawhide or otherwise F17 is pretty useless as desktop environment without local hacks.
Please report NM version and/or test NetworkManager-0.9.3.997-0.7.fc17 from updates-testing repository.
(In reply to comment #1) > Please report NM version and/or test NetworkManager-0.9.3.997-0.7.fc17 from > updates-testing repository. Yeah, this should be fixed in recent builds for F17, at least since early March.
Thanks, I'll do update during weekend and check that. I'm changing status to MODIFIED as I can't keep it on needinfo.
I don't see any way to configure a VPN connection in the current f17 builds. I have the following packages and their deps installed: NetworkManager-glib-0.9.3.997-1.git20120321.fc17.x86_64 NetworkManager-openconnect-0.9.3.997-1.fc17.x86_64 NetworkManager-gnome-0.9.3.997-1.git20120321.fc17.x86_64 NetworkManager-openvpn-0.9.3.997-1.fc17.x86_64 NetworkManager-gtk-0.9.3.997-1.git20120321.fc17.x86_64 NetworkManager-0.9.3.997-1.git20120321.fc17.x86_64 NetworkManager-pptp-0.9.3.997-1.fc17.x86_64 NetworkManager-vpnc-0.9.3.997-1.fc17.x86_64 NetworkManager-debuginfo-0.9.3.997-0.7.fc17.x86_64
(In reply to comment #4) > I don't see any way to configure a VPN connection in the current f17 builds. I > have the following packages and their deps installed: > What kind of problem do you have? That should be fixed.
I just can't find any option/menu/setting to configure a VPN connection at all.
Updated to 0.9.4.0-1.git20120328.fc17 and everything works now in XFCE, LXDE, OpenBox, KDE, and GNOME, including existing VPN connections.
Which packages should I have installed to be able to set up a Cisco VPN here then? I used to have a menu entry for the VPNs in the NM menu in gnome-shell, but I don't see that any more.
I have openvpn and Cisco VPN working: NetworkManager-glib-0.9.4.0-1.git20120328.fc17.x86_64 NetworkManager-openvpn-0.9.3.997-1.fc17.x86_64 NetworkManager-gnome-0.9.4.0-1.git20120328.fc17.x86_64 NetworkManager-pptp-0.9.3.997-1.fc17.x86_64 NetworkManager-0.9.4.0-1.git20120328.fc17.x86_64 NetworkManager-vpnc-0.9.3.997-1.fc17.x86_64 NetworkManager-gtk-0.9.4.0-1.git20120328.fc17.x86_64 NetworkManager-openconnect-0.9.3.997-1.fc17.x86_64 vpnc-0.5.3-14.svn457.fc17.x86_64 vpnc-script-0.5.3-14.svn457.fc17.noarch
(In reply to comment #8) > Which packages should I have installed to be able to set up a Cisco VPN here > then? I used to have a menu entry for the VPNs in the NM menu in gnome-shell, > but I don't see that any more. The packages listed in comment #9 are fine. So are 0.9.3.997-1 ones. You may have an issue with gnome-shell. Are you able to configure VPNs using nm-connection-editor (Gnome-Shell Applications->Other->Network Connections and click VPN tab)? rpm -q gnome-shell rpm -q systemd
After creating a new VPN-connection with nm-connection-editor all is well again and the AnyConnect VPN is working. I was sure there was a way to create a VPN-connection from the shell NM menu earlier? Maybe I'm remembering wrong...
[kmaraas@localhost ~]$ rpm -q gnome-shell systemd gnome-shell-3.4.0-1.fc17.x86_64 systemd-44-4.fc17.x86_64
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.