My only problem with sudo-rs is that unlike the other rust rewrites. Compatibility isn’t a goal. I use the -E flag for some very specific programs and trying to manually pass in a bunch of different variables from my user environment has proven both tedious and in some cases doing so still results in programs not launching as I don’t know exactly which variable it needs.

I’ve used rustdesk off and on. It is pretty good. I use it to help my aunt with “computer stuff”.

Had to scroll down this far just to get to markdown files. Although I write with a bit of a delay. Once I get something working. Then I document what worked and what didn’t. Alternative methods and issues I had with the alternatives.

So something disabled your monitors and you were able to get them back by quickly enabling them during the brief period of time that they were visible. The monitors should still be listed in the display configuration even if disabled. May be worth filing a bug with kde. Seems like a massive oversight if that isn’t the intended behavior.

My brother used to use enterprise windows 10 until he started having that vary issue with trying to play COD.

It certainly isn’t a permission issue like others are claiming at least for the window rules. It could be a bug, but as far as I know the steam deck does not use the latest version of kde, so it may already be fixed and isn’t worth reporting.

As for onlyoffice, if I had to guess. It is forcing its own window decorations and therefore you don’t get all of the same options as with windows that use the breeze decorations from kde. However you can still create window rules for these window. If I recall correctly. The default shortcut is alt + F3 which should work regardless of which decoration the window is using.

What does the kwin rule for evolution look like?

Lastly, the password thing is the only one that could be related to a permission issue. I however don’t believe you should start mixing keyrings. kwallet is probably already installed and running. Like I replied to one other person already. Both gnome-keyring and kwallet use the secret service standard. The only reason it could not work is if evolution hardcoded gnome keyring instead of relying more generally on secret service. However, I doubt that. You could even use keepassxc as a secret service provider if you wanted to. Although it is a bit more annoying in practice.

We’re basically already there. KDE has already moved to the secret service standard that is used by gnome keyring. The real issue in my experience has been applications hard coding a dependency on gnome-keyring and not secret service. Some applications such as mailpring have fixed that hard coded issue, but it is still an issue in other applications.

Honestly, it seems pretty similar to cockpit which should be available in most distros repos.

The reason most distros don’t do this is because they usually try to steer users to their preferred desktop. I don’t mean that in a bad way, but often they call it the flagship edition. This is usually the desktop environment that they develop and test. Think Linux Mint with Cinnamon, popOS with Cosmic, Zorin, etc. Pretty much every other distro that has options do exactly what you are showing through the use of the venerable calamares installer that you see in your screenshot.

Dolphin should be qt6 for quite some time now. So you should need qt6ct. Also I’m not sure if either qt5ct or qt6ct is maintained. Their is a fork in the aur that I have been using https://aur.archlinux.org/packages/qt6ct-kde, but not sure what to do outside of arch.

I will use old machine until the damn thing quits on me and be happy.

Hell, if you had gone from an arch derived distro like EndeavourOS and just clicked the nvidia option. It would have been solved.

I recently installed it on a one plus 6t (about a month ago) cause that seemed to be what a lot of videos were using and I read it had great compatibility. Never ran into any issues with the hardware buttons not functioning since that is a big part of tampering with mobile devices.

You aren’t meant to use them for managing your system. They are mainly there for development. For example, I often use them for a debian chroot on arch.

Mint doesn’t even support kde, so at best you would be grabbing it from Ubuntu’s repos which is probably out of date. Which leads to the problem of people on fixed release distros reporting problems that have already long since been fixed, so In addition to others suggestions of testing it out on a full plasma installation. I would also recommend testing it out on a distro known to be up to date in the first place.

First Arch and malware in the AUR now a ddos on Fedora. This is an attack on FOSS.

Or all of the above while still not being “as secure and private as promised”.

This article confirms my own experiences with AI. I spend a lot more time reviewing, reprompting, and tweaking than I save on coding. Having to double check or fight it to get what I want is not a time saver. Not to say that it doesn’t save time when it is right, but the thing that I never seem to get across to proponents of AI is that anytime I need to reprompt or refine, I have lost. I have officially wasted time at this point compared to simply referencing the documentation. Unless I’m generating a significant portion of code which only needs minor tweaks. I’m generally not saving time.

The only options when dealing with governments is comply or get out.