Deinstall kdesudo-trinity (sudo dpk --purge kdesudo-trinity). It has a bug under Debian that will need to be fixed for 3.5.13.Tim

On 16 October 2010 17:27, Bernd Mueffeler &lt;growanda(a)web.de <mailto:growanda@web.de>> wrote: At first my English is not so good, sorry for this. At secound this Project are wonderful News for me. But I have the same Problem than two other users When I will work with Krusader to Admin than he will have the root password. Thats the Problem, no chance to give him the password. Yes kdesudo-trinity is installed. The System is Debian Squezze and KDE 3.5.12 is the Standalone Desktop. What you say to the other with this Problem, I also do this. I hope you have a way for this Problem. My original post on this topic was really geared toward Debian users who do not want sudo enabled at all, preferring the traditional kdesu and the problem to do this in Trinity DE. As I wrote, I get dcop/klauncher errors. I have been able to reproduce this on more than one install, however cannot be 100% sure my machine is not at fault, also I have attempted a "minimal" install and may have something missing (although that should not be as deps are normally expected to get installed automatically. I am now using the --nonewdcop option (e.g. <kdesu kwrite --nonewdcop>) SO FAR this is working flawlessly and is the best workaround I can find. It would be simple to incorporate that in the menu for root gui stuff. It does require creating/editing ~.trinity/share/config/kdesurc as I wrote earlier and deinstallation of kdesudo-trinity. If I do kdesu without that option afterwards or use sux dcop still breaks. I have no claim to great knowledge of kde internals, perhaps someone better informed might investigate this or suggest any possible problems. Maybe it's a good clue to a proper fix, maybe it's also relevant to sudo users.