You are not logged in.
I'm still confused as to how this even happened, but earlier an update to archlinux-keyring came down the pipe, I tried installing with the graphical pamac, but got an authorization denied error, so I did it by console with sudo pacman -Syu like normal and it went through just fine. It disabled some revoked keys, didn't throw up an error. But now polkit and/or systemd and/or dbus are throwing up errors left and right about privilege and I cannot do anything without sudo. Not even allowed to reboot or logoff without doing it via console with sudo. I honestly don't even know where to begin debugging this because I literally didn't change or do anything other than installing the archlinux-keyring update. A systemctl --all produces this:
polkit.service loaded active running Authorization Manager
... a ton of other entries that I have removed now...Starting at the polkit entry, which is supposedly fine. I need to remove the radeon entry because I got rid of that package, but it has nothing to do with this and has been dead for a while now. When I try to kill or restart or just plain start up anything with systemctl, I am greeted with this error or one similar:
Action org.freedesktop.systemd1.manage-units is not registeredOddly enough, that error returns exactly one Google result - this very post.
I am guessing either systemd or polkit got fucked somehow, but I legitimately have no idea how. I have not done anything outside of opening Chromium, watching a movie, and updating archlinux-keyring in the past several hours. Before I go and rip out systemd and/or polkit and reinstall everything, is there something simple I'm missing here? Why would this happen with a keyring update?
Edit: removed identifying details like my username from the output.
Edit 2: running loginctl show-session $XDG_SESSION_ID --property=Active returns a Yes and checking whether or not I have multiple sessions active tell me I do not. In other words, there's only a single session and it is active.
SOLVED EDIT:
I really wish I could give a step-by-step of precisely what fixed this, but I did four things that seem to have resolved this, but I'm not sure if it was ONE of the four or the combination:
First, saw the front page warning about properly installing the new .crt from ca-certificates, did that. Very unlikely this was related though.
Second, removed systemd-sysvcompat (sudo pacman -Rn systemd-sysvcompat) and then reinstalled it. Still unlikely this did it.
Third, removed temp systemd files (sudo systemd-tmpfiles --remove) which clears /tmp. This very well could be the key.
Fourth, force reinstalled systemd (libsystemd) and dbus completely and rebooted. Most likely the fix.
Polikit now prompting as usual, logged in as usual and can reboot, and no cryptic GDbus or systemctl errors.
Last edited by nannerpussy (2017-03-24 00:45:37)
Offline
I neither don't know what messed your system nor what solved it since I'm quite new to arch. My humble advise is to always check the home page before a system upgrade (one of the first things I remember from some installation guide): I did see the "ca-certificates-utils 20170307-1 upgrade requires manual intervention" and followed the instructions and nothing bad happened here. Bottom line is, if we play by the book, many situations can be avoided.
Offline
I neither don't know what messed your system nor what solved it since I'm quite new to arch. My humble advise is to always check the home page before a system upgrade (one of the first things I remember from some installation guide): I did see the "ca-certificates-utils 20170307-1 upgrade requires manual intervention" and followed the instructions and nothing bad happened here. Bottom line is, if we play by the book, many situations can be avoided.
TBH I'm still hoping someone sees this post and can let me know what the hell happened. There have been quite a few updates in the past few days and for anything outside of core I will usually just run the update and go about my business. I know that's not the best thing to do, but if I manually checked updates one at a time (like I do with core or critical stuff like xf86-*) I'd spend half my time on it. So perhaps something slipped by me in an update earlier this week and just now became an issue, but it was weird timing with it breaking immediately after the archlinux-keyring update.
Last edited by nannerpussy (2017-03-24 05:59:39)
Offline