I researched this issue a bit. I don't have it on my machine.
The "Access Denied" is an error that comes from sd_bus_call, aka
I think. Here's the source:
You can trace the D-Bus stuff like so:
# SYSTEMD_LOG_LEVEL=debug systemctl
Sent message type=method_call sender=n/a
cookie=1 reply_cookie=0 error=n/a
Got message type=method_return sender=n/a destination=n/a object=n/a
interface=n/a member=n/a cookie=1 reply_cookie=1 error=n/a
LOAD ACTIVE SUB DESCRIPTION
loaded active running Arbitrary Executable File Formats
File System Automount Point
loaded active plugged
loaded active plugged Haswell-ULT HD Audio Controller
Why would D-Bus give Access denied to your call? I didn't find an answer.
On Sun, May 28, 2017 at 10:44 AM, stan <stanl-fedorauser(a)vfemail.net> wrote:
On Mon, 25 May 2015 07:36:12 +0100
Russel Winder <russel(a)winder.org.uk> wrote:
> I am guessing all of my Fedora Rawhide machines are in a "broken"
> state as whenever I try to use systemctl, I get:
> # systemctl
> Failed to list units: Access denied
> but this is root, access can never be denied. Huh?
I don't have this issue in Rawhide. I just finished updating to the
latest updates (at least those that weren't skipped), and systemctl
works just fine. Are there any messages in journalctl when you try to
run the command? journalctl -r will show the most recent messages
first, and journalctl -f will follow (tail) the messages, showing them
as they arrive.
test mailing list -- test(a)lists.fedoraproject.org
To unsubscribe send an email to test-leave(a)lists.fedoraproject.org