Skip to content
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

dbus-launch is probably not needed in systemd environment #112

Closed
Vladimir-csp opened this issue Jun 8, 2024 · 1 comment
Closed

dbus-launch is probably not needed in systemd environment #112

Vladimir-csp opened this issue Jun 8, 2024 · 1 comment
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@Vladimir-csp
Copy link

I do not have dbus-launch in my system (part of dbus-x11 package which is not installed).
From emptty log:

2024/06/08 12:06:10 Starting dbus-launch
2024/06/08 12:06:10 Could not find command 'dbus-launch' on PATH
2024/06/08 12:06:10 No output from dbus-launch

Dumping env via ~/.config/emptty script shows that it already contains DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus, which was probably set by systemd-related pam modules.

Perhaps it would be prudent to not even try to run dbus-launch if this var is already set.

@tvrzna tvrzna self-assigned this Jun 11, 2024
@tvrzna tvrzna added enhancement New feature or request bug Something isn't working labels Jun 11, 2024
@tvrzna
Copy link
Owner

tvrzna commented Jun 11, 2024

It should not start, if ALWAYS_DBUS_LAUNCH is not set to true and by default it is set to false. So first step is to fix the bug that ignores config and second is to check a value of DBUS_SESSION_BUS_ADDRESS env.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants