Will this mean that relogging in within 4s will still result in no sound?

In D1961#29623, @sunnyflunk wrote:

Will this mean that relogging in within 4s will still result in no sound?

Yes but with this value it always worked - at least on my system - even with autologin.

This feels like it's solving the symptom rather than trying to actually find the underlying issue. I've only seen this be reported for users that are using Solus Budgie, not GNOME or MATE.

In D1961#29640, @JoshStrobl wrote:

This feels like it's solving the symptom rather than trying to actually find the underlying issue. I've only seen this be reported for users that are using Solus Budgie, not GNOME or MATE.

This is exactly why I used the word mitigate rather than solve or fix. I have indeed done my tests on a Budgie machine but I am not so sure it is only limited to this specific DE because when I did some reseaches about this problem, I found this bug report on Red Hat which mention GNOME (randomly) and KDE (every time). I will do some checks on MATE when I'll be back from work.

It is not up to me to decide of course, but imho, the patch could be applied until a better solution is available.

EDIT: The problem also occurs on MATE and the same workaround works.

In D1961#29640, @JoshStrobl wrote:

I've only seen this be reported for users that are using Solus Budgie, not GNOME or MATE.

I think it's broader, definitely impacting on Plasma. I am for the mitigation given how annoying it is to lose the sound device.