Bug 365617 fixed this issue for Chromium, but the problem persists with other applications. Applications where the pinned icons still disappear are: - keepassx - pycharm there may be others, but these are the ones i use and found.
The fix was generic and not specific to Chrome/Chromium, so if it happens for those apps it might be for some other reason. Please post extremely exact steps to reproduce and xprop output for the windows involved.
Can't reproduce with KeePassX.
Ok, i will try to attach xprop output later... as for keepassx, it happens only if it is set to open database on startup. if no file is opened automaticaly the icon persists. Hope this helps with reproducing the problem
Your appletsrc (to get the stored launcher URL) would be great too. I created a database now and it's set to reopen it, but I still don't see the problem (although I could kind of see how this could cause similar behavior to Chrome ... which nevertheless should be fixed anyways ...).
Created attachment 103492 [details] xprop output before entering database password
Created attachment 103493 [details] xprop output after entering database password
xprop shows that NET_WM_NAME and WM_NAME changes after i enter the password and unlock the database file. As for the appletsrc, I'm not sure how to get you that information.
Thanks so far! The window title changing shouldn't be a problem as long as the WM_CLASS remains stable, which it does. BTW - it seems I have newer software: WM_CLASS(STRING) = "keepassx2", "Keepassx2" appletsrc is: $HOME/.config/plasma-org.kde.plasma.desktop-appletsrc
Let's also take a look at PyCharm, could you tell me what to download or so so I can have the same stuff as you?
Created attachment 103498 [details] plasma-org.kde.plasma.desktop-appletsrc
Sorry, nevermind pycharm, the problem is gone after the last update :) But if you are writing python code, i can recomand it, you can get it from: https://www.jetbrains.com/pycharm/download/#section=linux
BTW, i am using KeePassX 2.0.2
My distro has 2.0.3 it seems.
after update to plasma 5.9 the problem seems to have disappeared. closing bug.