Description of problem: Because of a dbus bug which doesn't update policies when new files are places in /etc/dbus-1/system.d, NetworkManager has to allow VPN plugins one by one Version-Release number of selected component (if applicable): How reproducible: Install NetworkManager-ssh (still not in repositories, because it depends on these bug): yum install NetworkManager-ssh Steps to Reproduce: 1. Start a new NetworkManager SSH VPN connection Actual results: Fails with the the following error in /var/log/messages: --- system] Rejected send message, 1 matched rules; type="method_call", sender=":1.5" (uid=0 pid=852 comm="/usr/sbin/NetworkManager --no-daemon ") interface="org.freedesktop.NetworkManager.VPN.Plugin" member="NeedSecrets" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager.ssh" (uid=0 pid=2546 comm="/usr/libexec/nm-ssh-service ") Apr 2 11:23:42 localhost dbus[729]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.5" (uid=0 pid=852 comm="/usr/sbin/NetworkManager --no-daemon ") interface="org.freedesktop.NetworkManager.VPN.Plugin" member="NeedSecrets" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager.ssh" (uid=0 pid=2546 comm="/usr/libexec/nm-ssh-service ") --- Expected results: NetworkManager-ssh should actually start the connection Additional info: Please have a look also at https://bugzilla.redhat.com/show_bug.cgi?id=923564 for some more information as this patch alone will not solve this problem. This patch will require a restart of NetworkManager for the changes to take effect. The patch to solve this situation is here: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=edd1ebe8a0f6703f7863684566011e34a9715186
This should have made it into NM 0.9.8.1 which is currently in Fedora 18 testing, F19, and rawhide. Can you test that out and see if they fix the issue?
Yep. All good. It's there. Bug closed I guess.
Since I depend on NetworkManager going into stable (to support f18 and 19), is it possible to make this bug depend on a bug that moves NetworkManager from testing to stable?
(In reply to comment #3) > Since I depend on NetworkManager going into stable (to support f18 and 19), > is it possible to make this bug depend on a bug that moves NetworkManager > from testing to stable? Dan, (Fruehauf) the package will pass to stable after a week more or less (if packager wants) or if the people give karma in bohdi.
I think this can close. Any objections?
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.