Message: previous - next
Month: September 2020

[trinity-users] Re: "TDE launcher could not be reached via DCOP"

From: Slávek Banko via tde-users <ml-migration-agent@...>
Date: Sun, 27 Sep 2020 00:58:28 +0200
On Saturday 26 of September 2020 22:54:52 D. R. Evans wrote:
> Every few weeks/months I suddenly start to receive the message in the
> subject line when trying to start programs from the quicklauncher, the
> TDE main menu or the "Open with..." menu item.
> Usually, logging out and back in "solves" the problem. Today it did not,
> and I had to reboot.
> Is there some less catastrophic way to get things working again when I
> start to see this message?
> � Doc
> PS I suspect that some process dies and for some reason TDE doesn't have
> a watchdog on it to force it to restart (if that guess is correct, it
> sounds like two bugs to me: one that the process can crash, one that TDE
> doesn't notice and do something about it).

Hi Doc,

do you observe any common thing that precedes it? For example, to update 
Trinity packages during an active session? Or does it happen by accident? 
You can examine ~/.xsession-errors to see if there is reported any crash 
when it occurs?

As an attempt to resolve the situation without logging out / logging in, 
without restarting you can try running /opt/trinity/bin/tdeinit. This will 
replace the existing tdeinit with a new one. Next to this, you can 
use "dcop tdelauncher MainApplication-interface quit" - this will 
terminate tdelauncher and then a new one will be started. In addition, you 
can restart the kicker: "dcop kicker kicker restart". I use it when I do 
updates of packages during an active session.

tde-users mailing list -- users@...
To unsubscribe send an email to users-leave@...
Web mail archive available at