-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning message "D-Bus socket address not found", even if command itself works #180
Comments
It's probably for the system bus address. You might have an env I'm not anticipating. Maybe the warning is too much. Set |
There doesn't seem to be much, but maybe you'll see something I do not :) (btw. the blank line before warning is there every time, I didn't add that):
|
The error indicates you either have an env variable called Since neither bus type should actually be required, I think I'll change this to a debug message and maybe only fail if it doesn't connect to either. |
I must start by saying that I have no idea about how dbus actually works and I use it only with playerctl to control mpv from scripts :). The problem seems to be that I have dbus-daemon running only under my user, not as a system service. If I start the system service (dbus-daemon running as root), the warning disappears. When I stop it, it is back again :). Your "socket address" request probably works only with the system service, but should not be needed, if the action itself works with user-run dbus. Btw. the file you mention doesn't exist on my system (Gentoo) even when the system service is running:
|
Related to #107 - I was affected by the problem there and blacklisted all 2.x versions as result; now I tested 2.2.1 (latest at this time) and it works OK, it just shows "D-Bus socket address not found, unable to list player names" warning every time (every single command I tested works and displays this message).
Not a big problem :), but hopefully can be fixed easily. Small shell-example (playerctl-0.6.1 is version 0.6.1 binary I was using until today):
If you need any other info, just let me know (including code modification and recompile).
The text was updated successfully, but these errors were encountered: