| Summary: | Network Manager fails to save new VPN connections - No session found for user | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikko Tiihonen <mikko.tiihonen> |
| Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | dcbw, erik-fedora, esammons, ikke, mclasen, rkhan |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | NetworkManager-0.9.3.995-0.4 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-20 12:10:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Mikko Tiihonen
2012-02-10 10:03:59 UTC
Could be the death of ConsoleKit; we've got some upstream code to use systemd instead (which replaced CK session tracking) which we'll pick up in a new build of NM. We had temporarily lost CK session registration - it should be back in todays gdm build, which should make CK users like nm work again. Of course, enabling the systemd code is still a good idea. NetowkrManager now works correctly when I installed gdm-3.2.1.1-12 Should also be fixed by NM 0.9.3.995-0.4 Still not fixed... Connection Add failed No session found for uid 1000 (unknown Reopening. Version installed / tested: NetworkManager-vpnc-0.9.8.2-2.fc20.x86_64 NetworkManager-vpnc-gnome-0.9.8.2-2.fc20.x86_64 NetworkManager-0.9.9.0-28.git20131003.fc20.x86_64 This is on a LXDE install of Fedora 20, running lxdm and xfce. This issue appears to be related to selinux. # setenforce 0 Created VPN connections appear and creating new connections works. I confirm this on fedora 20 and: $ rpm -qa NetworkManager* NetworkManager-openvpn-0.9.9.0-0.1.git20140128.fc20.x86_64 NetworkManager-0.9.9.0-41.git20131003.fc20.x86_64 NetworkManager-openconnect-0.9.8.4-1.fc20.x86_64 NetworkManager-vpnc-gnome-0.9.8.2-2.fc20.x86_64 NetworkManager-vpnc-0.9.8.2-2.fc20.x86_64 NetworkManager-openvpn-gnome-0.9.9.0-0.1.git20140128.fc20.x86_64 NetworkManager-pptp-0.9.8.2-3.fc20.x86_64 NetworkManager-glib-0.9.9.0-41.git20131003.fc20.x86_64 NetworkManager-pptp-gnome-0.9.8.2-3.fc20.x86_64 while creating pptp with nm-connection-editor. The setenforce 0 does not make a difference. I have to note that I've added NM_CONTROLLED=no to all my interfaces, due this is a desktop server. There is no way to add pptp conection with the nm tools, the add won't do anything but complain about the no session found for user. BTW, I'm using the normal gnome3 session from fedora. I disabled the selinux only for the time of restarting network manager service and trying the connection editor, after failure I re-enabled the selinux. I didn't disable selinux from the boot. Never the less, there is nothing in audit.log that would claim it's selinux. Oh, this is resurrection of an old bug. The code will be quite different now. Would you tell exactly what is the problem and how to reproduce that in order we could find what might be wrong. I use just openbox myself and don't have problems with saving VPNs. Also LXDE, XFCE and Gnome-Shell work for me. Thanks Jirka, I have up to date fedora 20. I have had network-manager disabled, due that I use static ip configuration and otherwise network manager sets my thunderbird & friends to offline. Interfaces are set with NM_CONTROLLED=no. 1. systemctl start NetworkManager.service 2.1 in gnome-shell, go to right-top corner -> settings -> network 2.1 or do nm-connection-editor 3. add new vpn -> pptp 4. fill in at least the gateway tab 5. try press save or add button What should happen: dialog should go away successfully, and I should have VPN menu in top corner of my gnome-shell What happens: In gnome-shell configs the dialog will not go away, the save button doesn't react. In connection-editor I get the complaint in dialog: "Connection add failed\n No session found for uid 8100 (unknown)" and on command line I see the nag: "(nm-connection-editor:28270): dconf-WARNING **: failed to commit changes to dconf: Could not connect: Connection refused" This leaves me out of having VPN handy in gnome menu bar. Thanks Jirka, I have up to date fedora 20. I have had network-manager disabled, due that I use static ip configuration and otherwise network manager sets my thunderbird & friends to offline. Interfaces are set with NM_CONTROLLED=no. 1. systemctl start NetworkManager.service 2.1 in gnome-shell, go to right-top corner -> settings -> network 2.1 or do nm-connection-editor 3. add new vpn -> pptp 4. fill in at least the gateway tab 5. try press save or add button What should happen: dialog should go away successfully, and I should have VPN menu in top corner of my gnome-shell What happens: In gnome-shell configs the dialog will not go away, the save button doesn't react. In connection-editor I get the complaint in dialog: "Connection add failed\n No session found for uid 8100 (unknown)" and on command line I see the nag: "(nm-connection-editor:28270): dconf-WARNING **: failed to commit changes to dconf: Could not connect: Connection refused" This leaves me out of having VPN handy in gnome menu bar. This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23 This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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. |