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).
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.
Cheers
Slávek Banko via tde-users wrote on 9/26/20 4:58 PM:
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
Nope.
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?
No obvious thing changed at all. I was working all morning without a problem. After lunch, I was getting the error.
I'll try to remember to look in ~/.xsession-errors next time (it was overwritten when I rebooted today).
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.
OK, I'll make a note of those things to try next time it happens.
Thanks muchly.
Doc
On Saturday 26 September 2020 06:50:25 pm D. R. Evans wrote:
No obvious thing changed at all. I was working all morning without a problem. After lunch, I was getting the error.
I'll try to remember to look in ~/.xsession-errors next time (it was overwritten when I rebooted today).
~/.xsession-errors becomes huge and doesn't have any timestamps. I tend to add something like this to a 5 minute cron:
echo `date` >> ~/.xsession-errors
It'll keep you from reading the whole thing...
Best, Michael
Michael via tde-users wrote on 9/26/20 6:10 PM:
~/.xsession-errors becomes huge and doesn't have any timestamps. I tend to add something like this to a 5 minute cron:
echo `date` >> ~/.xsession-errors
It'll keep you from reading the whole thing...
Mine seems to have plenty of timestamps in it; as of right now the last five entries are:
----
[2020/09/27 09:45:35.847] TQGDict::hashKeyString: Invalid null key [2020/09/27 09:45:35.848] [kicker] ERROR: : couldn't create slave : Unable to create io-slave: tdelauncher said: Unknown protocol ''. [2020/09/27 09:45:35.848] [kicker] [2020/09/27 09:46:21.071] [kate] WARNING: Pixmap not found for mimetype inode/directory
----
so there are plenty of timestamps there.
One wonders why there are so many entries in it. To me, the word "error" (in the filename) implies that something really bad happened and it should be dealt with immediately. But the entries in this file seem to be more in the nature of vague informational messages that apparently don't reflect any kind of danger to the stability of the system.
Doc
-
D. R. Evans -
Michael -
Slávek Banko