You can get the kernel messages from previous sessions like this: https://unix.stackexchange.com/questions/181067/how-to-read-dmesg-from-previous-session-dmesg-0#345978

I’m on Fedora so YMMV

Nobara is great distro that includes nvidia fixes and has a KDE spin

Be aware that kwallet will require you to enter your password if you auto-login. Kwallet usually saves your passwords for wifi etc. That’s why auto-login with KDE doesn’t make much of a difference in most use cases

It’s probably gone. But maybe you could have some luck looking for it in your BIOS like others suggested.

I haven’t used windows in quite a while, but while I did, on laptops sold with windows there was a recovery partition on them you could reinstall windows from. If you removed that partition you had no legal way of reinstalling, because no key was made available to you at any point.

MX Linux

Source: https://gitnux.org/most-popular-linux-distributions/

Is it just screensavers that are broken? Because I have set my screen to turn off instead of a screensaver and that is disabled while video is playing in FF. Maybe it’s an option in the mean time?

The command itself isn’t complex:

YDOTOOL_SOCKET="$HOME/.ydotool_socket" ydotool key 28:1 28:0

The hard part is getting ydotool to run on boot for your user (no sudo). I had to create a bash script to run on login with the following line:

ydotoold --socket-path="$HOME/.ydotool_socket" --socket-own="$(id -u):$(id -g)"

It’s a bit hacky but it works.

There’s still a bunch of little bugs in KDE6, they’ll get ironed out over time. For the KDE connect bug I use a ydotool command to emulate an enter key press to accept the remote command access from my bed.

Mullvad has DNS options that even block out some ads and trackers: https://mullvad.net/en/help/dns-over-https-and-dns-over-tls

I had a bunch of mild but annoying breakage since the update as well. What helped me is renaming .cache and .config, rebooting and just copying select things over to the fresh folders

A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4039

Bug reported: https://bugs.kde.org/show_bug.cgi?id=483210

I managed to track it down further. The issue is that some icons (Discover, Gajim, Steam) pull their light/dark info from the “Colours” instead of the “Plasma Style”. So If you mix and match like I did (Breeze Twilight, i.e. Breeze Dark Plasma Style with Light Colours), then most icons will appear light due to the Dark Plasma Style, but some will be dark because they get their Light/Dark info from the Light Colours.

That information seems to be cached in ~/.cache/plasmashell/qmlcache/. When I delete that folder I get the broken icons. I f I use the cached folder from my desktop it’s fixed. I’m guessing some apps just are broken currently in that regard and I’m just “lucky”, that my desktop didn’t correctly flush the plasmashell cache

deleted by creator

So I had some time to do some further testing into this issue and I made some “progress”.

On my desktop, who has the correctly displayed light icons for the dark plasma theme: if I straight up remove ~/.cache (rename it to ~/cache.bak) and reboot, several icons become black (update, gajim and steam). Meaning that somewhere in that cache (but not ~/.share/icon-cache.kcache, since I tried that already), the correct display of icons is located.

I’ll try to pinpoint it further and report back if I find anything.

I’ll try setting up a new user. Maybe I can just use a new profile and migrate some of configs from the old one.

dnf info plasma5support

Installed Packages
Name         : plasma5support
Version      : 6.0.1
Release      : 1.fc39
Architecture : x86_64
Size         : 432 k
Source       : plasma5support-6.0.1-1.fc39.src.rpm
Repository   : @System
Summary      : Support components for porting from KF5/Qt5 to KF6/Qt6
URL          : https://invent.kde.org/plasma/plasma5support
License      : CC0-1.0 AND GPL-2.0-or-later AND LGPL-2.0-or-later
Description  : Support components for porting from KF5/Qt5 to KF6/Qt6.

It’s unusual that no default wallet was created for you. Did you disable loging in with a password? The wallet always needs a password, but default behaviour is to pull the user password from the login.