Score:0

understanding and fixing dbus session/access

tn flag

on a default ubuntu 20.04 setup, accidentally ran systemd instead of systemclt, without parameters, and now some gnome things do not work.

for example, launching the terminal app gives me

"Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0:Could not connect: Connection refused"

ctrl+alt+f1 also wasn't working to swtich tty. not sure if dbus was impacting my input device... managed to get a shell by opening gvim and executing one. tried dbus-update-activation-environment with sorts of parameters. nothing helped. systemctl restart dbus.socket crashed my X session but at least i was able to change tty after that.

in the end the reboot fixed everything, as expected.

But i'd like to understand what exactly executing systemd as my user broke on the live system, and how i'd go about fixing it if a reboot is not desirable at that time.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.