By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 703

Summary:	KLauncher/DCOP issue persists a while after installation
Product:	TDE	Reporter:	Damiano <Mazzarot>
Component:	debian	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED WONTFIX
Severity:	critical	CC:	bugwatch, darrella, dzfixes-box1
Priority:	P5
Version:	3.5.13 [Trinity]
Hardware:	amd64
OS:	Debian Squeeze
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Damiano 2011-11-30 11:12:07 CST

I don't know where it's coming from, i'm no developer and i have no idea what these components are responsible for. But in half an hour of usage or bit later i keep getting either "KLauncher could not be reached via DCOP" or even worse "cannot talk to klauncher", which means i can't do anything if that happens. Whatever my attempts are, it just keeps bring this up and that's usually it. I can only restart everything or go to console. If i restart it's gone for a little while, but then it comes back anyway. And usually i do nothing special to cause this to happen, i just configure desktop themes and styles. I hope that helps.

Comment 1 Darrell 2011-11-30 19:46:38 CST

This sounds like bug 394 has returned?

Comment 2 David Hare 2011-12-01 14:45:31 CST

This could be su/sudo-related although bug 394 seems sorted

I'm getting this if "gksu" is run. I have not done a specific bug report for that yet

Some packages, e.g. synaptic, have gksu in their .desktop file, a quick fix is edit the tde menu

The klauncher problem can usually be fixed by calling "kdeinit" as user with no need for relogin/reboot (another quick fix, not solution)

Comment 3 Damiano 2012-01-03 09:42:29 CST

Thank you very much. That sounds very similar to what i was doing. Although of course i'd never have guessed that it's su/sudo related or any gnome components... so i guess it's just better to get rid of gnome completely for not to mash things up.

Comment 4 David Hare 2012-02-09 07:37:44 CST

Any attempt to use "su-to-root -X -c" for an application (or if that is included in any script) results in the same problem as it will invoke gksu

in addition to, some standard applications which have that in their .Desktop files

Comment 5 Darrell 2012-04-28 13:51:41 CDT

Is this a Trinity problem or a gksu problem?

Comment 6 Timothy Pearson 2012-06-12 23:20:12 CDT

I'm going to guess that it is a bad interaction between gksu and TDE, most likely caused by gksu somehow temporarily causing parts of TDE to run as root, modifying permissions and causing the failure.  This mechanism alone would make me discount the bug as something we really can't fix on this end.

Additionally, I cannot replicate the failure with gksu in my installation from GIT.  If anyone can replicate this bug when they are running TDE from GIT please reopen this report, and add a sequence of commands that is known to cause the problem reliably.