Re: Guarding against use of Plasma with qt5ct
I would say the latter in most cases - distros set it. On Thu, Jan 23, 2020, 12:06 David Edmundson wrote: > >Some ideas could be adding an inline message in the Application Style kcm > when qt5ct is detected or just simply unsetting the qt5ct env variable on > start. > > Can you explain how users get this env set. Is it them manually doing > something or do some distros install some sort of hook that sets it? >
Re: Guarding against use of Plasma with qt5ct
>Some ideas could be adding an inline message in the Application Style kcm when >qt5ct is detected or just simply unsetting the qt5ct env variable on start. Can you explain how users get this env set. Is it them manually doing something or do some distros install some sort of hook that sets it?
Guarding against use of Plasma with qt5ct
Hi, Every once in a while I run into users who have inexplicably broken theming. Example: https://i.imgur.com/WpPwDcz.png What ends up being the cause is qt5ct and the fact that it themes Plasma instead of us. This probably only happens when users have GTK DE installs and then decide to install Plasma alongside it. I'm not sure of the extent of GTK distros that use qt5ct, but for example I know that Manjaro GNOME uses qt5ct + kvantum to theme Qt applications. Given that that the broken theming gives a bad first impression and that it's not obvious to the user how to fix it, does anyone have any ideas on how to address this? Some ideas could be adding an inline message in the Application Style kcm when qt5ct is detected or just simply unsetting the qt5ct env variable on start. Filip
