Torrenting/seeding works great with Mullvad, which doesn’t have port forwarding

What’s the use case for a history merger?

I never understood how movie-web got so popular when services like FMovies exist.

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/

This won’t help you, but I wanted to chime in and say that I do not experience this bug. OS is Nobara, KDE 6, FF from repo. I have a KWin command to open FF with a specific size at a specific location and can resize it just fine.

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?

I think the reaction comes from the baking part, not so much the ingredients. Imagine someone saying beef tartar wedged between two balls of uncooked dough tastes like a hamburger. You’d probably be sceptical too.

I use Jami for video chat

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.

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

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.