On Sunday, January 21, 2018 10:07:20 PM CET Albert Astals Cid wrote: > El dijous, 18 de gener de 2018, a les 10:44:04 CET, Milian Wolff va escriure: > > Hey all, > > > > We've recently integrated kdesu into hotspot [1] to be able to record > > profile data as root. This is required to get access to some "advanced" > > performance counters and trace points, most notably the sched:sched_switch > > tracepoint required for off-CPU profiling. > > > > Now, my colleague originally used kdesudo which doesn't seem to be alive > > (?) upstream. I've seen there's some bzr repo that the kubuntu people > > seem to use. But in KDE proper, only kdesu is available. So I used that > > instead but it has a severe limitation: I cannot show the command output > > _and_ enable password keeping: > > > > $ man kdesu > > . > > > > -t > > > > Enable terminal output. This disables password keeping. This is > > > > largely for debugging purposes; if you want to run a console mode app, use > > the standard su instead. > > . > > > > I don't quite get why one would want to use standard su - we want to show > > a > > graphical dialog to the user and enable password keeping. Can someone > > explain this limitation? Is there some other alternative we could use? > > I guess the suggestion would be to use the polkit stuff?
Hm then I'll have to take another look at KAuth/polkit. Nate did that already but gave up after quite some time - it was too complicated for him to get done. But my question to kdesu remains, I wonder why -t disables password keeping... -- Milian Wolff m...@milianw.de http://milianw.de
