Hide Forgot
Description of problem: See description and solution at http://unix.stackexchange.com/questions/112224/allow-rygel-to-talk-to-networkmanager-over-dbus. To sum up, if rygel is run as a system user under networkmanager <0.9.9.1 it fails to bind to any network interfaces and thus remains inaccessible. Version-Release number of selected component (if applicable): rygel 0.20.3-1.fc20 networkmanager 0.9.9.0-42.git20131003.fc20 How reproducible: Always. Affects multiple people. Steps to Reproduce: 1. Create rygel system user and group 2. Create rygel systemd service 3. Configure rygel (interface= makes no difference) 4. Start rygel 5. Can't access rygel Actual results: Rygel only binds to 127.0.0.1, so is remotely inaccessible. Expected results: Rygel binds to all or specified interfaces.
nm >0.9.9.1 removes at_console dbus policy, thus allowing rygel to connect as a system user.
I'm not sure what you're asking me to do here? What is your proposed fix?
Upgrade networkmanager to 0.9.9.1+ (a version without at_console) in F20. If possible the networkmanager maintainers should be notified.
(In reply to secondary from comment #3) > Upgrade networkmanager to 0.9.9.1+ (a version without at_console) in F20. That might be a major change that could affect other packages, ultimately though it's a decision that needs to be made by the NM maintainers
Obviously with f21 this can now be closed.