8th October 2016, 7:17
(6th October 2016, 11:19)kdemeoz Wrote: 3. ...since upgrading to 5.8.0 [though it did sometimes happen in 5.7.5], i've now learned that there's NO POINT in even bothering to log out & in again, if i'm trying to recover from some mad plasma misbehaviour, because... each time i logged back in, KWin would fail, with a "best-case" of destroying the system tray audio widget [its icon would be replaced by a small triangle which when clicked generated a blank popup, ie, impossible for me to control sound], then when i clicked on any other task bar items, the bar would entirely vanish, OR the "worst-case" post-login of the task bar never appearing at all. On these [MANY REPEAT] occasions, i found i simply had to reboot to recover, BUT...
5. Conky is in System Settings' Startup list, but never ever does auto-start after boot up; i always have to manually start it.
#3 [EDIT] -- On 2 occasions today, when i experimented with more logouts/ins, the Audio Widget was NOT destroyed, & actually worked normally. That's great... BUT... for me in 5.8.0 logouts are still no good compared to reboots, because sadly with a simple logout/in, KWallet breaks... it will not accept my password, hence all the programs relying on KWallet to supply their own passwords, fail. This is not a new fault, it's been this way since my 5.8.0 upgrade, but i forgot to include it in my earlier list.
#5 [EDIT] -- Today i found that if i remove Conky from the Autostart list, & have the "Restore previous session" option selected [which IS my normal setting], then Conky is active immediately [which is what i want, & how it used to be for me in Mint 17.3 KDE4]. The unexpected effect of having Conky in the Autostart list, was that this would actually stop it [as it was already running from the previous session]. IMO that logic is wrong; it would be better if Maui/Plasma5 would simply do nothing if an autostart-listed pgm is already running, rather than counter-intuitively stopping it.