On 2/23/24 13:11, pete wrote:
if running plasma wayland the vlc Kaffeine
Firefox and Discord all cause issues
That is the rub with wayland. Depending on what the apps use, you may run into
issues that wayland doesn't support. Discord places quite a bit of demand on
the graphics/video subsystem, as does FF depending on what you are viewing --
especially if you are running web-apps like discord within FF. I've had much
better luck sticking to X11.
On your install with the borked Plasma, since this is KDE, you can always
delete the config file directory and then login again and have plasma recreate
its config. However, this is made much more difficult due to the stoke of
brilliance the KDE-team had to dispense with a traditional config directory
and dump all files under $HOME/.config is a willy-nilly manner. You will need
to carefully select the KDE config files to delete (or move to another
location, e.g. cd ~/.config; md tmp; mv ..... tmp;)
Your other traditional option for testing a borked KDE is to create a new user
and then login as that user and see what KDE does on a freshly generated
config. This can eliminate any version mismatches in config files, etc.. that
may have crept in under you normal user. Either way, they are reasonable tests
to conduct.
KDE should be doing this, but you can rebuild the system config cache with:
kbuildsyscoca5 --noincremental
(short for: "kde build system config cache", --noincremental tells it to
regenerate all cache files)
(double check that kbuildsycoca5 is the correct number, KDE3 was kbuildsycoca,
KDE4 was kbuildsycoca4, and early plasma was kbuildsycoca5, but I haven't used
it in a couple of years)
I suspect a fresh Arch install will work fine -- as it will start with a fresh
config.
--
David C. Rankin, J.D.,P.E.
