The issue I am referring too is theoretically created upon the transition from Gnome to KDE Plasma6 on Fedora 40. (Maybe an issue with older versions as well, however that isn’t something I’m currently that familiar with.) The first issue starts with the Fedora homepage prior to install of an iso. Insufficient information regarding versions of the distro and packages. The only one described to come with KDE (the preferred choice in my and many’s case) was in a “Skins” download. Moreover, people like myself who read and did our research and decided that based off the publicized information regarding “Workstation”, it was the premier choice for us. Due to the unclear nature that “Spins” in-fact, the same os at its core as “Workstation”. Which leads me into the next issue. One that seems to come after the download and initialization of KDE, after the completion of Fedora 40 Workstation with Gnome. Many sources lead with it’s fine to have both technically, you just cannot delete the “essential” files from Gnome otherwise you’ll run into a slue of issues. Well, it happens regardless but in the form of permissions & access. Let’s take myself for example. My “user” account that was created on Gnome carried over perfectly with KDE. Even annotated my permissions as owner etc… However, now anytime anything that required sudo, konsole, dolphin installs (for most installs if the app, or what have you require any usability to the device), Flashdrives & HDD’s etc. etc., that require permissions, that you supposedly have. Currently, mine says admin. Will not let you make any changes, alter, read, write, edit, most cases view, some instances even install an app and so forth. All without the availability to even change the permissions nor ownership. Assuming, the system believing that you’re not the same user/owner, even if you were the one to make or install those changes. I am not exactly sure as to the majority of fixes/workarounds quite yet. However, I have found that giving root permissions may work, but that’s risky. I have read adding to the “wheel” group with the root and editing the pam file might, but I have yet to get that to even work properly even when I use the command “su”. Another option is to completely re-install KDE and wipe your drive. I have also not had any luck with making “user” a sudoer, useradd nor usermod commands. I will hold out hope for one more option whenever the development team can publish something that is clearly helpful in accessing the user’s setting tool or a similar GUI or even application, option, or program to aid in altering the user permissions. I have found my admin:/run/user/1000 core system file. However, that is NOT something I want to try to and alter, lol. So I will be scouring, trying to either find a way to manage those issues locally and without re-installation. If not, then I as a programmer will devote my time to taking an open sourced one and either create one. Or create a bot that can assist in error management and handling. Thank you for taking the time to read this, if this was helpful in any way, or if you even already have a way to fix this or suggestions to try. Please email or contact my profile. Thank you.
A long rant, no paragraphs to keep ideas together, nothing to specifically answer but a long winded spiel.
If you have a specific question please state it.
When you post please be concise and word your sentences and paragraphs so the reader can understand the issue.
I do not even understand what you have done.
Did you install workstation then add the KDE desktop?
Did you install the KDE spin?
What is the actual problem?
Please state it in a way we may understand and respond to .
Duly noted, and my apologies.
Yes, installed workstation
then KDE as described would be fine.
Aslong as who does that, keeps their core gnome files
and chooses plasma from log in screen to keep plasma seperate from Gnome desktop and shell.
No, KDE Spin, destributed by Fedora on their site has NO place for stand alone vs of Plasma or KDE. Only a full iso/install including Fedora 40 that i already had.
So I went to KDE’s Official website to get their version for Fedora 40.
Added f40
That may have been an error.
There are several threads about how to install the KDE desktop on a machine that was initially gnome only and use KDE. The KDE official website is not fedora and may do things differently, especially when it comes to keeping everything in sync with system upgrades.
In fact, I believe kde with plasma 6 could be installed and work properly on a workstation installed machine with sudo dnf group install "KDE Plasma Workspaces" It seems intended that using that group should give everything needed, with all dependencies, to run a kde DE with plasma 6 on fedora 40.
Remember that software from 3rd party sites may not operate properly on fedora, may not have the proper selinux context, and may have files that conflict with fedora provided packages.
On my desktop that command would install 258 additional packages and about 14 other dependent groups as well.
That is what I did. I used that command because that is what it said too, lol. However, I do see your point and I completely am aware that there could be accruing issues with implementations like this.
I am not upset nor “mad” at a choice I had made, knowing the implecations. I mean sure I’m frustrated, but that’s mainly due to the fact that I’ve tried so many things to clear up an issue that theoretically doesn’t seem like that difficult of an issue to fix,…on the surface lol.
I’ve found out that out since then lol. If I have too, this weekend I will set aside enough time to make an open sourced GUI to implement the permission changes and “hope” to add a bot to see any error codes of ‘missing’ or wrongfully placed files, into the right depo. Or just create them, and probably clone then attach another system filing bot.
Something that seems simpler to me.
install libvirt and the virtual machine manager then create a VM that you install the kde spin of fedora into. Play with it there and don’t mix the 2 very different DEs.
You could even reinstall the workstation on the host and only install kde into the vm so each has a clean environment for the DE in use.
So, I would. But I don’t really want to sub partition an entire portion of my laptop for that when I have the version I already want on here, lol. The latter one of those two seems like a more realistic option. However, none of those also will help others in our community who have accidentally found themselves in a similar or same situation as myself.
*Update: I have found the ultimate issue and (so-far, I will continue to monitor) how to give you complete control back for those who have had issue’s of “lost-permissions”.
+Recap.
-Expln of issue: “Dual booting”, Gnome & KDE on the same /:(Drive). Shows either ownership, or some form of accessible permissions. However, only “-r” in actuality.
-Sys Error: You “-u”, aka the user. May “technically” have ownership of those drives, directories, files etc… The error comes in when having both elements on the drive and the sys thinking the new element’s -u is new. Probably the new root thinking and telling the sys that.
-Even if you do own it, all files and more in the top directories for /Home/…etc. are only “shared”. Or Partially present. Pieces of run/exe/**** or other init files are in the /:(Drive). Not owned by the new you, but to sys and/or root.
**TLDR: You do own it, at least your UID does. Sys thinks you are new -u and took small parts of it all from you.
**Fix: So far the sudo find followed by directories comnd. Will locate all “owned” by root. The small bits stolen should appear. Then the same comnd followed by the proper chown cmnd to take ownership of those files.
This will find all the directories in your home owned by root:
sudo find ~ -type d -user root
You can then repeat the find command and add the action you want to do - recursively changing ownership of all the found directories and their contents to the current user:
sudo find ~ -type d -user root -exec sudo chown -R $USER: {} +