My biggest problems, in order, are these:
1. I make heavy use of the compositing function Desktop Grid, and it frequently stops working. Sometimes when it stops (but not usually) I can restore it by executing a kwin_x11 --replace from the alt-F2 launcher. Usually though I have to log out and back in.
2. at times kwin_x11 runs away, looping continually and filling one core of my CPU, and becoming nonresponsive. When this happens, I can get to a console so I usually do a ctrl-alt-F2, log in, kill kwin_x11, then return to the desktop and restart kwin_x11 using the alt-F2 launcher.
3. I can no longer pull a tab from a tabbed window and have it in its own window. This just no longer works, and is sometimes causing me some serious heartburn. Seems to me that has to be a setting someplace but so far I have not figured it out.
3. xembedsniproxy persistently will not start. I always have to start it manually after logging in.
I have been searching for relevant information that might help me sort this out, and I have run across something that might be relevant.
I was getting many error messages of the form:
- Code: Select all
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/jiml/.local/share", "/var/lib/plasma5-profiles/common/share", "/usr/local/share", "/usr/share")
Now, I still get this particular error because I have not found any plasma-popupapplet.desktop, or a plasmapopupapplet.desktop.
However, I was getting this type of error referring to kwin-decoration.desktop, kwin-desktopswitcher.desktop, kwin-effect.desktop, kwin-script.desktop, and kwin-windowswitcher.desktop, all of which looked potentially relevant to me. Kwin should default properly, but who knows for sure?
So, I visited /usr/share/kservicetypes5 and I found the following files: kwindecoration.desktop, kwindesktopswitcher.desktop, kwineffect.desktop, kwinscript.desktop, and kwinwindowswitcher.desktop, among many others that were not hypenated and some that were hyphenated.
This looks to me like a packaging error.
I have symlinked these five files, and those error messages are gone. I have also restarted my session (for about the 4th time today) and so far I have not had trouble...though I am not optimistic that will last. I don't know if my symlinks will survive an upgrade, but I symlinked rather than renaming files in the hope that either (1) a future upgrade will properly name the files and overwrite my symlinks or (2) the symlinks will survive an upgrade that rewrites the files they link to.
In any case, I do not know whether this will help with any of the issues I've been seeing (the first two are the ones I hope the symlinking helps with...those are a really big problem given that logging out and back in requires me to suspend a bunch of VMs and often give up some sshfs mounts).
If anyone has any idea how to handle (3) I would love to hear it. I can live with (4) though I do need to add a command to start that to some script somewhere.
