I’ve got a show-stopping, SERIOUS problem that I didn’t expect: missing group authorizations.
It took me a while to realize what was going on as I’m new to KDE. However, I’ve now proven that at least Konsole has the flaw of not providing all the logged in user’s group privileges upon creation of windows and tabs. It ONLY provides TWO groups, the GID of the account and, for whatever weird reason “wheel”.
The other 45 groups that I have are missing! However, the system IS configured with these. But to get them, the user has to su into their own account, entering the password, in order to get them.
To prove this is drop-dead simple: In any account that has more groups than just its own GID and wheel, simply run the ‘id’ command, note the missing groups, then call su, either with or without the dash, doesn’t matter, and the same account username, enter the password, and run id again. Then, you’ll see the missing groups are now available.
Just calling bash or otherwise instantiating a new shell DOES NOT CURE THIS PROBLEM.
This MAY explain some other weird behavior I’ve seen from time to time in other KDE applications.
First, I’m shocked this could be the case, but it is, at least in my configuration:
Fedora Server 38
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.109.0
Secondly, if this isn’t something that’s resolved by a configuration option, well, then Konsole is a useless waste of time - what’s someone to do, SSH into their OWN box just to get their normal, garden-variety privileges?
Thirdly, if this applies to all of a running instance of KDE, and can’t be configured away, for all its good it does, KDE has a serious problem because it’s useless for serious people. In that case, it can’t be used for the deployment of sophisticated applications because it doesn’t grant privileges properly!
I SURE HOPE this is something that can be configured away.
About the ONLY thing I can think of that MAY bear on this regarding my configuration that KDE developers may not have considered is this:
There’s something seriously wrong with Wayland - it’s immature, apparently - and, nevermind all the detail, I’ve had to side-step it and use X11. However, I’m not able to use the login-desktop-choice feature because, for whatever reason(s), I’m not offered the option when logging in. It’s either Wayland, which seldom doesn’t crash right away, or nothing. So, the system boots as a non-graphical system, I log in, and THEN xinit pointing at the script that starts KDE and this has worked flawlessly. THUS: Instead of root launching KDE, it’s my own user account. Perhaps KDE is confused and decides to remove all my groups thinking that who launched it was root?! Seems unlikely, but maybe?
…I’m just looking for a way out because I like KDE, GNOME is unacceptable on MANY grounds and I’m not thrilled with the other desktop choices I see out there today. HELP!