MX-21 beta 2 feedback thread (xfce)

[dreamer]

@JayM
You should try your problematic apps with the normal Xfce panel plugin called "Window Buttons". We need to know that they work correctly there before we assume it is a Docklike problem. Maybe you already checked that, I don't know.

@asqwerth
In Xfce 4.16 Thunar is always controlled by the window manager. A CSD version of Thunar doesn't exist as far as I know.

[asqwerth]

@asqwerth
In Xfce 4.16 Thunar is always controlled by the window manager. A CSD version of Thunar doesn't exist as far as I know.

The MAIN window of Thunar 4.16 should normally be controlled by xfwm window manager. But note that if you open Thunar's Edit Preferences, you can see that dialogue window is CSD.

The problem with the beta1 and beta2' Thunar was that gtk3-nocsd was installed. Once installed, the default position in MX was to disable noCSD (in MX-Tweak), meaning CSD was enabled. It made Thunar not show the xfwm theme, but instead the window decoration that comes from within the gtk theme. In MX-Comfort, both window decorations are very similar, but you can tell the difference by the window buttons on the top right.

Check the Thunar screenshot from JayM in this thread. viewtopic.php?p=652525#p652525

Compare the window buttons with mine below.

ksnip_20210914-022955.png

Anyway, gtk3-noscd won't be preinstalled with MX21, and Thunar's main window will be back to using xfwm themes.

[entropyfoe]

So many posts on these threads, hard to keep track.

I am running the beta2, and wanted to remove the gtk3-nocsd package.

I did not know about the tweaks option.
So I removed in with synaptic, and rebooted.

Behavior seems normal, including that annoying firefox right click anomaly is gone.

-Jay

[dreamer]

Anyway, gtk3-noscd won't be preinstalled with MX21, and Thunar's main window will be back to using xfwm themes.

I never understood why MX team bothered with gtk3-nocsd when libxfce4ui-nocsd exists and is superior in any way. It was even packaged for Xfce 4.16 temp repo in MX-19. Including gtk3-nocsd is probably the weirdest thing I have seen MX devs do during my time here. It's a relief it will be gone from final. MX is about quality, not hacks - and if hacks are used at least choose the best hacks available. The inclusion of gtk3-nocsd was a mystery to me.

[BasicSloth]

Hei @SwampRabbit I'm glad that you care and try to help. I know the problem with the busy days :-)

Yeah I tried it. It works. But honestly, acpi=off is not an option. I did not spend so much money on a 8 core CPU to just use one.

Unfortunately i did not process very well in my subject to analyze segfaults. (busy days problems :-))
I noticed, that i'm not able to reach a GUI when i start in non-uefi. In fact i do not even reach a terminal. Just a blank screen. I guess, the GPU is not working there, cause the screen is looking for a source. That happens also with acpi=off.

I just will give it another try with acpi=ht.

Edit: acpi=ht doesn't work. I reach the GUI. But Fall back to the login screen. Entering demo user and pw leads to black screen (but GPU working as there is the score blinking in the left top corner)

[dolphin_oracle]

Anyway, gtk3-noscd won't be preinstalled with MX21, and Thunar's main window will be back to using xfwm themes.

I never understood why MX team bothered with gtk3-nocsd when libxfce4ui-nocsd exists and is superior in any way. It was even packaged for Xfce 4.16 temp repo in MX-19. Including gtk3-nocsd is probably the weirdest thing I have seen MX devs do during my time here. It's a relief it will be gone from final. MX is about quality, not hacks - and if hacks are used at least choose the best hacks available. The inclusion of gtk3-nocsd was a mystery to me.

we bothered because there was a movement to have such a thing for apps other than xfce apps. its null and void now, but apparently those libs are nuts even if you have them "disabled:. kind of ridiculous that they are even in the debian repo TBH. they were only included on beta 2 by accident concerning a syncing of our git repos and wasn't caught till after release.

[manyroads]

For virtualbox, I am able to get a dark theme by starting it with command line args "-style kvantum", and by having ~/.config/kvantum.kvconfig be:

Code: Select all

[General]
theme=KvSimplicityDark

This also seems to work for mx-tools. It does not work for any of the mx-tool components either via addind the start argument to the desktop files or by adding the applications to kvantum. Oh well. It is some progress.

[dreamer]

@dolphin_oracle
You are a great guy that do a ton of work and seem to be able to do anything. I'm not here to argue. I guess you do know that third party apps are easy to use with xfwm in Xfce 4.16 with:

Code: Select all

$ xfconf-query -c xsettings -p /Gtk/DialogsUseHeader -s false

My feeling is that MX devs maybe took it too far by letting Xfce put headerbars on LibreOffice and other third party applications.

[dolphin_oracle]

@dolphin_oracle
You are a great guy that do a ton of work and seem to be able to do anything. I'm not here to argue. I guess you do know that third party apps are easy to use with xfwm in Xfce 4.16 with:

Code: Select all

$ xfconf-query -c xsettings -p /Gtk/DialogsUseHeader -s false

My feeling is that MX devs maybe took it too far by letting Xfce put headerbars on LibreOffice and other third party applications.

What was wanted was a solution that didn’t require xfce but thanks for the info.

@dreamer is that xfconf-query code supposed to do anything without libxfce4ui-nocsd installed or is libxfce4ui-nocsd required?

[dolphin_oracle]

I think that really just affects dialog windows, and not even all of those. take a look at the "configure custom actions" dialog in thunar vs. the regular thunar preferences dialog for an example.