https://bugs.kde.org/show_bug.cgi?id=179678
--- Comment #38 from Bo Weaver <b...@boweaver.com> --- (In reply to Bo Weaver from comment #37) > (In reply to Nate Graham from comment #36) > > Let me make sure I understand: > > > > - With GNOME, you log in as the root user with a Wayland session OR an X > > session and in both cases you can run Gedit and Dolphin as the root user > > Yep with Gnome running a X session Gedit and their File Manager (Natulius) > (Spelled wrong) work just fine when logged in as root. By default Kali is > set up with only a root account. > > > > > - With KDE Plasma, you log in as the root user with a Wayland session OR an > > X session and in both cases you can't run Kate or Dolphin > > Yep they just "don't work" no error no nothing. Since I am an advance user > I did know to run the executable from the command line and then got the > error can't run as root. Breaks your heart when you click on Dolphin like > you have 10,000 times and after an update nothing happens. > > Even in KDE when logged in as root LeafPad and Gedit will open an run and > change files just fine. This is my point you haven't stopped editing files > you've only stopped me from using Kate. Midnight Commander also works just > fine. I just don't like going back to 1980. > > Yep just checked Gnome on both Wayland and Xorg the default text editors and > file manager work fine when logged in as root. This is a KDE problem. > > > > > If that is the case, then I think we have found the actual bug and I agree > > that it should be fixed. This ticket just tracks general Polkit adoption, so > > we should track that issue with a new bug report. > > Thank you! yes this is a bug. When logged in as root there should be no > restrictions on anything. That's the reason for the root account. Now days > this account is locked and rightly so. Really Polkit from what I have read > is for system changes from a normal user account like of like sudo to > elevate privileges for a single action (good thing) Such as changing a > configuration file. I'm all for this. What I am saying is when an advanced > user enables the root account and logs in there should be no restrictions on > anything. You guys are in control of the desktop not the underlying OS. > The PolicyKit should have no control when logged in as root. Your root. > > If you want to restrict Kate and Dolphin from a normal user account go right > ahead but leave the root account alone. BTW I just tried Kate and Dolphin from a normal user account on a Kali machine. When I went to edit a system file it did give me a proper password prompt. Kate worked just fine in this manner. It appears this problem is when only logged in as root. This is fine from the normal user account. Kate won't fire at all from root. -- You are receiving this mail because: You are watching all bug changes.
