linuxmint / mint19.3-beta

BETA Bug Squah Rush
10 stars 3 forks source link

cinnamon: Screensaver freezes #6

Closed MichalKolesinski closed 4 years ago

MichalKolesinski commented 4 years ago

When I lock the screen myself, all is working perfect, while trying to unlock it. Unfortunately, when screen locks after computer is not being used, the screen is totally unresponsive. I'm not able to use the virtual keyboard, or see the password signs. Login is possible though. Only the graphical side "freezes".

mtwebster commented 4 years ago

Can you go into your Power settings, and disable the 'Turn off the screen when inactive for' (if it's enabled at all) - and then allow the computer to idle again to see if this recurs.

Thanks

MichalKolesinski commented 4 years ago

I turned it off. As long as screen is "on", there's no problem. But I have also manually turned off the screen, and then, after turning on it freezes again.

clefebvre commented 4 years ago

Only the graphical side "freezes".

So when you move the mouse or start typing... you can see the screensaver and its input password field... but the characters in it don't show up.. and everything's fine again after you press Enter?

clefebvre commented 4 years ago

I remember we had this issue in 19.2 already. I could reproduce it easily with a laptop connected to a TV with HDMI:

I think it's triggered by display changes. Here on the OP's computer it's probably the screen turning itself off completely.

MichalKolesinski commented 4 years ago

That’s the problem I have. As you mentioned, I can unlock the computer, but I can’t see the input. It would not be a big deal, but it also renders the virtual keyboard useless. Maybe 99% of times one does not use it, but this 1% when a button stops to work and you can’t unlock your device may happen one day :D

mtwebster commented 4 years ago

Could I get you to try the packages I've mentioned here: https://github.com/linuxmint/muffin/issues/530#issuecomment-563476189

And see if you still have this issue? Thanks

clefebvre commented 4 years ago

We'll tackle this as an update post-release.