Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request to own name refused by policy when you add a policy at runtime #69

Closed
ghost opened this issue Oct 18, 2017 · 5 comments
Closed

Comments

@ghost
Copy link

ghost commented Oct 18, 2017

On a running system with dbus-broker when you install a package that acquires a name on the bus and installs a system.d/ policy.conf then access is denied (probably because dbus-broker isnt aware of the newly installed policy file):

DBusException: org.freedesktop.DBus.Error.AccessDenied: Request to own name refused by policy

To reproduce:

dnf install tuned
systemctl enable tuned
systemctl start tuned

(watch it hang until it times out trying to get a name on the bus)

A reboot fixes the issue (probably because dbus-broker re-reads /etc/dbus-1/

@Keruspe
Copy link
Contributor

Keruspe commented Oct 18, 2017

I think this is a duplicate of #57

@ghost
Copy link
Author

ghost commented Oct 18, 2017

Okay, if that is the case then please close this one

@dvdhrm
Copy link
Member

dvdhrm commented Oct 18, 2017

Yes, this is a duplicate of #57. Thanks!

@dvdhrm dvdhrm closed this as completed Oct 18, 2017
@ideepika
Copy link

ideepika commented Feb 8, 2021

I am seeing this issue in dbus-broker 26 but the duplicate issue command works fine, environment: fedora 33

journalctl does not record any related failure

❯ dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
method return time=1612768223.656476 sender=org.freedesktop.DBus -> destination=:1.30588 serial=4294967295 reply_serial=2
sudo ./hsphfpd.pl
org.freedesktop.DBus.Error.AccessDenied: Request to own name refused by policy

@dvdhrm
Copy link
Member

dvdhrm commented Feb 8, 2021

@ideepika The underlying issue of this report was fixed. If you think you hit an actual bug, please open another report (so the others are not needlessly notified of the new discussion), and please include as much information as you can. I will gladly look into to, but given that the old issue was identified, I need a hole lot more information to know what exactly is going on in your case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants