You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I primarily use AwesomeWM. I have a script that repeatedly checks if Volctl has been launched and attempts to start it three times in succession. Despite this, it often fails to launch. Specifically, it might successfully launch only 2 out of 5 times. The success rate seems dependent on Pipewire or some other services, but I cannot pinpoint the exact cause of the issue.
I have been encountering this problem for at least six months; previously, I had no such issues. I would appreciate any assistance to resolve this, as I'm puzzled about what could be causing these launch failures. When I manually start it after the system has booted up, it launches immediately without any issues.
The text was updated successfully, but these errors were encountered:
Sounds like some race condition. volctl depends on PulseAudio (or the pipewire-pulse service) and the system tray/dbus to be available, depending on the systray protocol you are using.
It would be helpful if you could provide a console log of volctl to be sure what the underlying issue is.
Is this different from #81 (comment)? If no, then we should continue the discussion in the original issue #56 to keep things tidy.
I primarily use AwesomeWM. I have a script that repeatedly checks if Volctl has been launched and attempts to start it three times in succession. Despite this, it often fails to launch. Specifically, it might successfully launch only 2 out of 5 times. The success rate seems dependent on Pipewire or some other services, but I cannot pinpoint the exact cause of the issue.
I have been encountering this problem for at least six months; previously, I had no such issues. I would appreciate any assistance to resolve this, as I'm puzzled about what could be causing these launch failures. When I manually start it after the system has booted up, it launches immediately without any issues.
The text was updated successfully, but these errors were encountered: