Page 1 of 1

[Solved]Multiple instances of ktimer at boot, KDE Mageia 7

PostPosted: Aug 22nd, '20, 21:03
by newmo
I cleaned installed a few months back on top of 6. I vaguely remember getting a single ktimer at boot when running Mag6. But I now have seem to have four (they pop up at launch and are now sitting in the system tray). They don't seem to be configured to launch anything.


I was hoping someone could help me troubleshoot it. Security is a concern, if I can eliminate that I can live with the symptoms. Googling for more generic KDE resources hasn't got me anything yet.

KAlarm is enabled in Sytsem Settings>Startup and Shutdown no sure if that's related.

I cannot remember ever setting up a ktimer for anything.

I am running Mageia 7
5.6.14-desktop-2.mga7
64 Bit KDE Plasma (plasmashell 5.15.4)

Re: Multiple instances of ktimer at boot, KDE Mageia 7

PostPosted: Aug 23rd, '20, 00:32
by doktor5000
If you look in ktimer, are there any timers configured ? Also, did you try to quit all the running ktimer instances ?

Also, what do you have listed in systemsettings under startup and shutdown -> autostart ?
You could also try to start with an empty session, configured under startup & shutdown -> session management

Re: Multiple instances of ktimer at boot, KDE Mageia 7

PostPosted: Aug 25th, '20, 20:31
by newmo
Thank you doktor5000

With an empty session they do not appear

autostart lists just kalarmautostart kalarm --tray

I have not set any ktimers myself, and the four instances that open don't seem to be configured to run anything when I open them. I can close them ok, one by one.

Ktorrent launched with my boot before this one (which is expected - not sure if related)

Re: Multiple instances of ktimer at boot, KDE Mageia 7

PostPosted: Aug 25th, '20, 21:12
by newmo
Thanks again. Resolved now. User error/ignorance. I did experiment trying to set up some alerts some time ago and looked at ktimer amongst other things. Combine that with hazy knowledge about persistence between sessions. I quit everything ktimer related I could see and then rebooted fine in a normal session.