You are not logged in.
Still having issues after removing old nivida drivers and installing mesa-git verified with pacman -Qs I have all needed systemd packages as well as dbus.
If I run $DBUS_SESSION_BUS_ADDRESS I get
"zsh: no such file or directory: unix:path=/run/user/1000/bus".
I can see in my /run/user/1000 there is a bus file but it cannot be opened with any text editor and nano doesn't recognize that it is present either.
I tried to run systemctl --failed previously but it doesn't show anything has failed and it successfully shows all working units.
I recently installed replay-sorcery and I used to be able to enable and start the program in systemd but I can no longer do that after updating today.
I run: "systemctl --user enable --now replay-sorcery" and get the output: "Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined"
Any help is appreciated tremendously attaching journal and specs/version below.
Journal
specs/version
Systemctl status(I didn't know if this would be helpful or not)
Systemctl --failed
Last edited by lorddickfist (2020-12-28 17:29:21)
Offline
DBUS session is there and things are connecting to it. What are you doing in your shell? any custom zsh profiles plugins/ oh my zsh or something? What's your
env
output?
Offline
DBUS session is there and things are connecting to it. What are you doing in your shell? any custom zsh profiles plugins/ oh my zsh or something? What's your
env
output?
Only plugin for zsh is Oh My Zsh for changing the CLI look and autocomplete, nothing special in shell other than that.
my output for env is this
Offline
And omz is a broken hack, If you drop omz and try with a normal zsh does it also not work? Is your systemctl aliased to something that might break here?
Offline
And omz is a broken hack, If you drop omz and try with a normal zsh does it also not work? Is your systemctl aliased to something that might break here?
Can confirm is still broken on bash, omz, and regular zsh. How would I check if it is aliased?
Offline
zsh: no such file or directory: unix:path=/run/user/1000/bus
That's perfectly normal.
The value of $DBUS_SESSION_BUS_ADDRESS is "unix:path=/run/user/1000/bus" and you're trying to issue that a command, but it's not command and it's also not a path (if you enter "/etc", zsh will enter that path)
I can see in my /run/user/1000 there is a bus file but it cannot be opened with any text editor and nano doesn't recognize that it is present either.
Because it's hopefully a socket.
~ ·> file /run/user/1000/bus
/run/user/1000/bus: socket
Again: perfectly normal.
I run: "systemctl --user enable --now replay-sorcery" and get the output: "Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined"
Aha.
echo $DBUS_SESSION_BUS_ADDRESS
ps aux | grep dbus
journalctl session-status
Offline
zsh: no such file or directory: unix:path=/run/user/1000/bus
That's perfectly normal.
The value of $DBUS_SESSION_BUS_ADDRESS is "unix:path=/run/user/1000/bus" and you're trying to issue that a command, but it's not command and it's also not a path (if you enter "/etc", zsh will enter that path)I can see in my /run/user/1000 there is a bus file but it cannot be opened with any text editor and nano doesn't recognize that it is present either.
Because it's hopefully a socket.
~ ·> file /run/user/1000/bus /run/user/1000/bus: socket
Again: perfectly normal.
I run: "systemctl --user enable --now replay-sorcery" and get the output: "Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined"
Aha.
echo $DBUS_SESSION_BUS_ADDRESS ps aux | grep dbus journalctl session-status
I ran that command at the end of your post and got this.
However regarding the ~ ·> file /run/user/1000/bus
/run/user/1000/bus: socket you said its fine for it to 0 bytes and un-openable and not be recognized as there?
Offline
/run/user/1000/bus: socket you said its fine for it to 0 bytes and un-openable and not be recognized as there?
It's a socket, so yeah, 0 bytes and unopenable in a text editor is normal. As for not recognized as there, it is recognized as there, the problem is in how you're checking that. You can't run what you're trying to run.
Last edited by Scimmia (2020-12-28 15:23:27)
Offline
loginctl session-status
Also the other commands, please.
Offline
seth meant to have wrote:loginctl session-status
Also the other commands, please.
command "echo $DBUS_SESSION_BUS_ADDRESS
ps aux | grep dbus
loginctl session-status
prints this
Offline
That's only "loginctl session-status", but you do have an active session.
Offline
So twice how seth has given you 3 commands and you only do the last one.
Offline
That's only "loginctl session-status", but you do have an active session.
Oh you wanted them as seperate.
echo $DBUS_SESSION_BUS_ADDRESS gives unix:path=/run/user/1000/bus
ps aux | grep dbus gives this
Offline
I wanted them at all.
If you want to curl them together, you've to group the output
(cmd1; cmd2; cmd3) | curl …
So the address is ok and you've a session bus process.
systemctl --user status
yields the same error?
What about
dbus-send --session --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
Offline
I wanted them at all.
If you want to curl them together, you've to group the output(cmd1; cmd2; cmd3) | curl …
So like this
So the address is ok and you've a session bus process.
systemctl --user status
yields the same error?
What aboutdbus-send --session --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
EDIT: I don't know why dbus-send was blank it worked by itself but here is a working link
Last edited by lorddickfist (2020-12-28 15:52:07)
Offline
No erro, session dbus responds and has a systemd service…
Do you actually still get the original error?
Offline
... You didn't try to run the systemctl --user command as root/with sudo did you?
Last edited by V1del (2020-12-28 15:59:01)
Offline
No erro, session dbus responds and has a systemd service…
Do you actually still get the original error?
No I do not have any of the original errors, only issue is one service not auto-starting, but it might be best to go to the github page for support on that.
Offline
... You didn't try to run the systemctl --user command as root/with sudo did you?
After checking my command history, no I did not run that command with sudo.
Offline
So a three staged x-y-z-problem…
systemctl --user status replay-sorcery
Offline
So a three staged x-y-z-problem…
systemctl --user status replay-sorcery
I did a fresh reboot since I already manually enabled. Here is the result of that commmand
Offline
It's enabled but not (longer) active and there're no errors.
I frankly have no idea what it's supposed to do but looks like a transient service (ie. not a permanently running daemon)
Can you
systemctl --user restart replay-sorcery
and does that do something you desire?
Offline
It's enabled but not (longer) active and there're no errors.
I frankly have no idea what it's supposed to do but looks like a transient service (ie. not a permanently running daemon)Can you
systemctl --user restart replay-sorcery
and does that do something you desire?
That command does the same as me doing
systemctl --user enable --now replay-sorcery
which is fine for now, like I said I can get support on the github page instead.
It's supposed to be a constant running service as its supposed to allow you to create a 30 second replay using the keybind ctrl+super+r
Offline
I'd say check your logs
journalctl -b --user-unit=replay-sorcery
Offline
I'd say check your logs
journalctl -b --user-unit=replay-sorcery
Here is the output of that
This is not after a fresh reboot
Offline