Public bug reported:
If I have a brainfart and run `systemd --user` when I mean `systemctl
--user`, and then Ctrl+C it...
1. All terminals (not just the current one) start responding `Failed to
connect to bus: Connection refused` when running `systemctl --user`
2. Anything which tries to play audio and didn't already have a
connection to pipewire open errors out.
3. Applications which don't already have an open connection to the
session bus fail to connect to the bus. (I've confirmed that freshly
launched Flatpak applications fall back to their non-portalized file
pickers, which show the in-sandbox view of things.)
4. `ubuntu-bug` fails to open a new browser tab because Firefox's remote
can't connect to the existing browser instance.
5. qdbus returns `Could not connect to D-Bus server:
org.freedesktop.DBus.Error.NoServer: Failed to connect to socket
/run/user/1000/bus: Connection refused`
This has already happened to me twice, but it shouldn't happen again
because, now that I've realized the cause, I've written a systemd()
function for my .zshrc to guard against accidental invocations.
(In case the next step isn't prompting for more system information, I'm
on Kubuntu 24.04.3 LTS)
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2133883
Title:
Accidentally running `systemd --user` instead of `systemctl --user`
irrevocably breaks D-Bus session bus
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2133883/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
