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?
Kind Regards,
Jay
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
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.comwrote:
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
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.
Okay, Yeah, I forgot you use Slackware too. :-)
I'm using 13.1 32-bit. As mentioned, no such problems here.
I build 13.37 32-bit and 64-bit (Current too) but don't use. I could use them if I took the time to configure the systems but 13.1 has been my system for a while now and I'm slow to change. (I probably will move from 13.1 to 14.0.)
Regardless, I'm using a similar system to help troubleshoot.
Darrell
On Saturday 30 of June 2012 02:45:55 Jay wrote:
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.comwrote:
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
I tested it in version 3.5.13.1 on Debian Squeeze. I tried both of kdesu from kdebase and kdesu replaced by kdesudo. In both cases it works without problems.
Slávek --
-
Darrell Anderson -
Jay -
Slávek Banko