MX Linux Forum

Confirmed. Does the same thing here. Definitely a theming issue, since it will start up with: oror

@Stevo:

Stevo wrote:(...) I don't get any of those glib errors at all, but I'll have to test this on a generic install.

Thanks! Greetings, Joe

Confirmed on a generic install, and that Tim's fixes work. You could edit the menu entry to add one of those lines before the "showfoto".

@Stevo:

Stevo wrote:Confirmed on a generic install, and that Tim's fixes work. (...)

Is it possible to implement the fix in a new version of the package? Greetings, and a nice Sunday, Joe

MX-16_fan wrote:@Stevo:

Stevo wrote:Confirmed on a generic install, and that Tim's fixes work. (...)

Is it possible to implement the fix in a new version of the package? Greetings, and a nice Sunday, Joe

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.

@Stevo:

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.

Just noticed that (unsurprisingly) this issue prevails in MX-17.1.

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

MX-16_fan wrote:@Stevo:

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.

Just noticed that (unsurprisingly) this issue prevails in MX-17.1.


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

Different qt and gtk versions. There were some.fairly major changes in both.

@dolphin_oracle:

dolphin_oracle wrote:

MX-16_fan wrote:@Stevo:

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.

Just noticed that (unsurprisingly) this issue prevails in MX-17.1.


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

Different qt and gtk versions. There were some.fairly major changes in both.

I see. And why is this dependent on the theme? Greetings, Joe

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.

if you want, you can override the default qt theming in mx by modifing (or even deleting) /etc/X11/Xsession.d/98qtconfig , then loggin in/out.

@Stevo,
@timkb4cq:

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.

So is this a "WON'T FIX" case then? Greetings, Joe