screensaver settings [Solved]

[fishface]

So, installed 5.18 kernel, after installing, reboot, wifi auto-connected, however, 3 successive reboot afterwards it fails to auto connect, so same sort of pattern, works after first boot, subsequent reboots it doesn't, now trying 5.10.

Another oddity, but not an issue, since updating to kernel 5.18 every time I hit the logout button/icon (top left) I now get a system beep!

[fishface]

Tried 5.10, same pattern, installed, reboot select 5.10 (non systemd), it boots, wifi connects, subsequent reboots it doesn't.

[Huckleberry Finn]

... Maybe you'd like to try ConnMan instead of the Network Manager , at least to see how it is there .. Up to you, in case you'd like to try we'll go on.

[fishface]

I leave as is at the moment, it's no big deal, and it does sometimes connect and it's not exactly a show stopper.

I was greeted with this message this morning though.

https://drive.google.com/file/d/1ff0aAk ... sp=sharing

[Huckleberry Finn]

Light-locker and the Xscreensaver may be conflicting.

[fishface]

Update, still have the issue, but I also have another issue, after the screen goes to sleep, lid shut etc, I wake the laptop up, I get the login screen, enter credentials, I then get a blank screen, almost as if the screen has power-off again, it does this around 50% of the time. Only way out is to hard reboot.

If I switch to KDE, as I had zero issues with it on 19.1, will it make any difference? i.e, is the underlying system for power/screen different in KDE?

[fishface]

For the record, I did not ever get this fixed, today, I downloaded and installed the Plasma desktop via the MX Package Installer, rebooted logged into KDE Plasma desktop and all has been working fine, no WiFi disconnected any more after retruning from sleep, no blank screen after login etc.

Side note, I believe that during the download and install of Plasma one of the prompts was to use kdm which I answered the default of "yes", maybe this is what fixed it.