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 didn't fully understand the problem, but volunteered to add this bug report after discussing it here.
When dbus-broker-unitsare installed as opposed to dbus-daemon-units, then jackdbus prevents the machine from shutting down (without extra waiting time). It hangs until it gets killed by systemd.
I am not sure if that is indeed the underlying culprit (not responding to sigterm) or it simply getting stuck while shutting down.
I made an attempt to fix the 2nd issue in ac334fa but seems then unrelated then
Describe the bug
I didn't fully understand the problem, but volunteered to add this bug report after discussing it here.
When
dbus-broker-units
are installed as opposed todbus-daemon-units
, thenjackdbus
prevents the machine from shutting down (without extra waiting time). It hangs until it gets killed by systemd.It seems the reason for this is that
from comment 21.
jackdbus
is started using a generated systemd service, see comment 27.When properly defining a service like in comment 27:
jackdbus
does not hang on shutdown / reboot.I have no suggestion how to fix this but I would be pleased if you could. Thanks
Environment
Steps To Reproduce
Expected vs. actual behavior
When using
dbus-broker-units
,jackdbus
should respond toSIGTERM
properly and "quit" so that the system can shut down.The text was updated successfully, but these errors were encountered: