No sound in flatpak apps after wake-up from sleep [Solved]

[twister]

I've got a couple of apps installed from flatpaks ie. ungoogled-chromium, FreeTube.
Everytime when I wake-up the system from sleep there is no sound in those apps.
If I play a YouTube movie in the mentioned ungoogled-chromium it acts as it was on mute.
The same with FreeTube. Closing and re-opening the app restores the sound.
The native and repo apps maintain the sound through sleep and wake-up cycles.

I'm on MX-21.1_ahs_x64.
I've upgraded kernel from 5.16 to 5.17.0-3mx-amd64 x86_64 recently but it didn't help.

[AdamK]

There is some bug introduced in mx 21 where the lock screen breaks audio of running apps.

Have a look at this: www.reddit.com/r/MXLinux/comments/s9m45 ... &context=3

Also relevant: https://forum.mxlinux.org/viewtopic.php ... 64#p675264

[twister]

Yes, that's the thing.
I wasn't even aware that it also happens after simple locking the system (ctrl-alt-del).
I tested it and the sound has gone as it happened after resuming from sleep.
I will try the suggested solution (replace light-locker WITH i3lock and i3lock-fancy) later today.
Thanks for that @AdamK

[Huckleberry Finn]

First make it sure what happens if you just suspend without locking the screen:

Code: Select all

sudo pm-suspend

Then if it's fine (if it's seen that the culprit was the locker) you can replace it. But there are even simpler and lighter ones in the forum. Like slock or i3lock only (...fancy locks the screen a bit late (lagging) .. not so prompt)

[twister]

I did the test and light-locker is a culprit.

I've changed xfce4-session/general/LockCommand to i3lock and it's working fine now.

However I miss a switch user, reboot etc. functionality.
As far as I know slock doesn't provide it either.

What can I replace light-locker with in order to have it?

[Huckleberry Finn]

These are simplistic ones (in fact i3lock is also a fork of slock).. there are other lockers but since they are for specific DEs they may pull many dependencies .

[AdamK]

Honestly it's a really annoying bug which affects the real world usability of MX. I'm thinking of leaving just because of this. Maybe I'll start using the KDE spin.