Message: previous - next
Month: April 2012

Re: [trinity-devel] Bug report 927 Kate: Can't concurrently run kate with tdesu

From: Darrell Anderson <humanreadable@...>
Date: Mon, 9 Apr 2012 22:15:12 -0700 (PDT)
> Would somebody who does not use a sudo based distro please test whether this happens on your
> system?
> 1. Start kate as normal user.
> 2. Start a separate kate session as root using 'tdesu kate'.
> Two separate sessions should be open. In the second session
> you should be able to view the contents of /root.
> If only one session is open then you are experiencing the
> same problem.
> No other app seems affected by this behavior.
> Thanks much.

I found the problem. I don't know the correct long-term solution.

The problem is caused by the patch pushed in GIT hash 2b178a53, 2011-10-26 (SVN revision 1260900). The patch was pushed to resolve bug report 394.

I rebuilt tdebase with that patch reversed. Now I have no problems whatsoever using kate as normal user and concurrently as root through tdesu. The patches from bug report 692 have no ill effects either as I now have both my normal user kate and root's kate configured to use Calvin's patch for MDI usage. When I first start kate as root and then concurrently run kate from konsole as normal user, I no longer see the weird dcop warnings.

Thus far I do not notice any xsession "Klauncher could not be reached via dcop" errors as originally reported in the bug report.

Reversing the patch restores the code to 3.5.10 status. I run both KDE3 and TDE and in KDE3 I notice none of these problems. With the reversed patch, behavior is now the same in both desktops.

Yet as I mentioned, I don't know whether the patch is correct. If the patch is required, then the change has nasty effects and needs resolution elsewhere.