On 02.09.2017 at 10:32 +0200, James Lu wrote:
Hi again, With some experimentation, I replaced the contents of /etc/X11/Xsession.d/99qt5ct with the following: # Enable qt5ct by default unless another PLATFORMTHEME option is set # or KDE is running. if [ -z "$QT_QPA_PLATFORMTHEME" ] && [ "$XDG_CURRENT_DESKTOP" != "KDE" ] then export QT_QPA_PLATFORMTHEME=qt5ct fi This seemed to work: the end result is that qt5ct is enabled on Xfce, GNOME and Budgie, but not enabled on Plasma 5. I also went ahead and removed the QT_PLATFORMTHEME and QT_PLATFORM_PLUGIN defines because they aren't necessary based on the upstream readme and my own testing. A git-style patch with this change is attached. Best, James On 01/09/17 07:31 AM, Lisandro Damián Nicanor Pérez Meyer wrote:On 27 August 2017 at 17:03, James Lu <bitflip3@gmail.com> wrote:Hi everyone, From what I read at https://forum.antergos.com/topic/6487/qt5ct-has-priority-over-standard-plasma-settings-app/2, Lisandro's concerns are correct and qt5ct does appear to override Plasma's settings entirely. However, since qt5ct requires an Xsession file[1] to be enabled by default, could one solution be having the script exit silently if it finds any KDE environment variables? (This is assuming that the order at which vars are set make this possible, but I haven't verified that)This is definitely something to try, yes.Alternatively, would it make sense for qt5ct to Break or Conflict with Plasma, at least until these issues are worked around?And a nice way around it in case the above fails. If you are interested in trying this I'll be more than happy to sponsor you. Dmitry/team: any comments from you?
Merged: https://github.com/mati75/qt5ct/commit/bfee1ceabefe20ffb8a6086f1f4cf0f26632e483
Here are sources: https://mentors.debian.net/debian/pool/main/q/qt5ct/qt5ct_0.33-1.dsc
-- .''`. Mateusz Łukasik : :' : https://l0calh0st.pl `. `' Debian Member - mati75@linuxmint.pl `- GPG: D93B 0C12 C8D0 4D7A AFBC FA27 CCD9 1D61 11A0 6851