Are you using Ubuntu or a derivative?
No it's a stripped slackware 13.37 32bit. I'll rebuild tdebase with reversed patch and see how she goes. Thanks.

Jay

On Fri, Jun 29, 2012 at 3:30 PM, Darrell Anderson <humanreadable@yahoo.com> wrote:
> Pretty sure this is upstream and not distro
> specific.
>
> It is exactly the same as 'solved' bug number 394
> but under latest git build.
> http://bugs.trinitydesktop.org/show_bug.cgi?id=394
>
> Running tdesu (from guest console or superuser menu item)
> kills klauncher and nothing from tmenu or tray will launch,
> instead receiving the error message: "Klauncher could
> not be reached via dcop"
>
> Running tdeinit fixes the error.
>
> To reproduce open a guest console and run 'tdesu
> kwrite' then close and launch something from tray.
> My build is from latest git. Can someone confirm this
> behaviour? Regression?

I'm using the latest GIT as my primary desktop. I used tdesu many times a day. I have not seen the problem.

I wonder whether there is some obscure difference among operating systems or profile configuration files that cause.

Are you using Ubuntu or a derivative? I ask only because of the sudo nature of those systems.

If you want to troubleshoot, you could rebuild tdebase with the commit 3d7141e5 reversed (which is the same as reapplying the patch from commit 2b178a53).

Darrell


---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting