Re: [trinity-devel] After "Super User Mode" - "Klauncher could not be reached via dcop"

  I have noticed this with Trinity throughout 3.5.13 development, but it never bubbled up in priority over CMake and build issues. The problem: If you use one of the "Super User Mode" apps like konqueror file manager. The desktop can no longer launch applications as a normal user until Trinity is restarted. You get a Klauncher error message that "Klauncher could not be reached via dcop".   It looks like after a super user app is run - the dcop is stuck in super user mode or something similar. I don't know how to go about chasing this down, but wanted to bring it to the lists attention. I also want to know if someone else can confirm this behavior.   Just open System->Super User->File Manager-Super User Mode   It will work fine. Then close it. No go try and open any other app as a normal user (i.e. kwrite). It won' work. You will get the error: "Klauncher could not be reached via dcop"   So what every gets changed when dcop runs a Super User mode app -- doesn't get undone when the app exits. -- David C. Rankin, J.D.,P.E.