https://bugs.kde.org/show_bug.cgi?id=387974

Chris <chriswi...@hotmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chriswi...@hotmail.com

--- Comment #14 from Chris <chriswi...@hotmail.com> ---
If they feel it's so bad to run the whole process as su, I'm fine with it. 
Devs know best.  But why in the name of all that makes logical sense would you
disable it before implementing the new auth flow?  Now it just plain doesn't
work for creating, moving, copying setting permissions on system files!  Now
I'm just using a different su process that I like less simply because Dolphin
has no working method that I'm aware of anymore.  How does that make any sense?
 Get the user mode system to work, then disable sudo mode.  How is that not the
obvious strategy?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to