Code: Select all
QT_QPA_PLATFORMTHEME=gtk3 showfoto
Code: Select all
QT_QPA_PLATFORMTHEME=qt5 showfoto
Code: Select all
QT_QPA_PLATFORMTHEME=qt4 showfoto
Code: Select all
QT_QPA_PLATFORMTHEME=gtk3 showfoto
Code: Select all
QT_QPA_PLATFORMTHEME=qt5 showfoto
Code: Select all
QT_QPA_PLATFORMTHEME=qt4 showfoto
Thanks! Greetings, JoeStevo wrote:(...) I don't get any of those glib errors at all, but I'll have to test this on a generic install.
Is it possible to implement the fix in a new version of the package? Greetings, and a nice Sunday, JoeStevo wrote:Confirmed on a generic install, and that Tim's fixes work. (...)
Well, I could modify the desktop launcher file to include one of those settings, but no matter what one of those I picked, it would cause problems on other desktops or themes.MX-16_fan wrote:@Stevo:
Is it possible to implement the fix in a new version of the package? Greetings, and a nice Sunday, JoeStevo wrote:Confirmed on a generic install, and that Tim's fixes work. (...)
Just noticed that (unsurprisingly) this issue prevails in MX-17.1.Stevo wrote:(...) I could modify the desktop launcher file to include one of those settings, but no matter what one of those I picked, it would cause problems on other desktops or themes.
Different qt and gtk versions. There were some.fairly major changes in both.MX-16_fan wrote:@Stevo:
Just noticed that (unsurprisingly) this issue prevails in MX-17.1.Stevo wrote:(...) I could modify the desktop launcher file to include one of those settings, but no matter what one of those I picked, it would cause problems on other desktops or themes.
Trying to understand the nature of this problem. Why didn't it occur in MX-16?
Greetings, and thanks in advance for your answer, Joe
I see. And why is this dependent on the theme? Greetings, Joedolphin_oracle wrote:Different qt and gtk versions. There were some.fairly major changes in both.MX-16_fan wrote:@Stevo:
Just noticed that (unsurprisingly) this issue prevails in MX-17.1.Stevo wrote:(...) I could modify the desktop launcher file to include one of those settings, but no matter what one of those I picked, it would cause problems on other desktops or themes.
Trying to understand the nature of this problem. Why didn't it occur in MX-16?
Greetings, and thanks in advance for your answer, Joe
dolphin_oracle wrote:because the way the themes are applied varies by qt version, and what gtk/qt version the theme is written to.
under jessie, qt could be set to follow the gtk themes and it generally worked ok. In stretch, you can do something similar, but there are occasions when it doesn't work as well as before.