MX-23 beta 1 feedback thread

[dolphin_oracle]

This is on KDE Plasma. The VM is a full install. I check the settings on the application launcher settings panel. By default, it does not even apply Plasma's default application launcher settings used in distros like Kubuntu and Arch Linux. And I tried both X11 and Wayland with the issue not being resolved.

I can confirm the power and session buttons do not stay expanded. they are present in the pull out menu, but they don't stay expanded. that is weird. might be an issue with debian's build, which is what we are using. the application launcher widget itself stays changed though.

I can confirm that Debian 12 release candidate does not exhibit this strange behavior on Plasma's application launcher. Not sure why this is an issue on MX-23.

Ok I figured it out. small conflict in our defaults setting package. can fix. thanks for the report.

[Melber]

...I'm getting a slew of new init errors in my .xsession-errors log...
This is due to double keybinding for same action

Code: Select all

Keys: Invalid key/modifier on line 59): Control Mod1 Bksp :Exit

I think it just doesn't like Bksp. Change line 59 in the fluxbox keys file to

Code: Select all

Control Mod1 BackSpace :Exit

[siamhie]

On the subject of the fluxbox init file, is anybody else seeing this behavior?
- manually edit init file and save (eg. change session.screen0.slit.autoHide: false to true)
- fluxbox menu > leave > refresh
- edit to init file gets overwritten/reverted

Changing the fluxbox-remote commands in the menu-mx file from
fluxbox-remote reloadstyle; fluxbox-remote reconfigure
to the old command
fluxbox-remote restart
leaves the edited init file as is.

Yes. I can duplicate it. Reverting back to fluxbox-remote restart fixes it.

[siamhie]

...I'm getting a slew of new init errors in my .xsession-errors log...
This is due to double keybinding for same action

Code: Select all

Keys: Invalid key/modifier on line 59): Control Mod1 Bksp :Exit

I think it just doesn't like Bksp. Change line 59 in the fluxbox keys file to

Code: Select all

Control Mod1 BackSpace :Exit

That did the trick. I thought it was due to 2 bindings for one action. Didn't think of it as a spelling message as both bindings (backspace and del) worked.

[Gaer Boy]

did you install grub? the log indicates no. so how did you try to boot the mx23 installation

:bagoverhead: Stupid error! I don't install grub - I want the MX21 grub to retain control. I just forgot to update grub - twice!

[Joseph DeGarmo]

OK, so I managed to edit the KDE info center to show MX Linux instead of Debian/GNU Linux. I added a config file by using this command:
sudo nano /etc/xdg/kcm-about-distrorc

Then I entered the following into the new config file:

[General]
Name=MX Linux
LogoPath=/usr/share/gazelle-installer-data/logo.png
Website=https://mxlinux.org
Version=23

I rebooted and the KDE info center was updated. Now the trick is that the version number will need to be updated with each new version release.

zzzMX KDE Info Center.png

[Jerry3904]

MXFB-Font does not work well. Selecting font for GTK does not work at all, for Fluxbox it is impossible to change the font to any non-regular style (bold, italic etc.) Are you sure this is the last version of the script from pre-Beta? (BTW - The "about" button with some information about the version of the app will be helpful.)

Looks like the last version didn't make it into the beta - have to wait for the next update of mxfb-accessories.

Sorry, missed this. It's already up on MX-Linux with both your PRs so will ask DO to package.

[siamhie]

Here are some initial remarks re MX-Fluxbox beta1
...
Default dock (wmalauncher)
-------------
Default dock is NOT showing up on session start. following errors appear (one by one) in ~/.xsession.errors

Code: Select all

--background-color: Argument '<COLOR|GRADIENT>' is missing.
--border-color: Argument '<COLOR|GRADIENT>' is missing.
--hover-background-color: Argument '<COLOR|GRADIENT>' is missing.
--hover-border-color: Argument '<COLOR|GRADIENT>' is missing.

These arguments could instead be added to the TTIPS+ items

Also, mxdk script is missing a sed command...

Can confirm.
DefaultDock.mkdk isn't right.
- pkill wmalauncher command is missing
- Hex colour definitions need to be quoted, otherwise they are being read as comments.

Also, mxdk script is missing a sed command...

?? sed command is there and working for me


To fix replace contents of ~/.fluxbox/scripts/DefaultDock.mxdk with this

Code: Select all

#!/bin/bash
pkill wmalauncher

#set up slit location
sed -i 's/^session.screen0.slit.placement:.*/session.screen0.slit.placement: TopLeft/' $HOME/.fluxbox/init

fluxbox-remote reconfigure; sleep 1

# TOOLTIPS
TTIPS+=" --tooltip-show-delay       250"
TTIPS+=" --tooltip-text-padding     3"
TTIPS+=" --tooltip-border-size		3"
TTIPS+=" --tooltip-foreground-color #ffffff"
TTIPS+=" --tooltip-background-color #1d2324"

#commands for dock launchers

wmalauncher --desktop-file mx-tools.desktop --tooltip-text "MX Tools" --background-color "#1d2324" --border-color "#1d2324" --hover-background-color "#29353b" --hover-border-color "#0f56d9" --window-size 48 $TTIPS & sleep 0.1
wmalauncher --desktop-file custom-toolbox-mxfb.desktop --background-color "#1d2324" --border-color "#1d2324" --hover-background-color "#29353b" --hover-border-color "#0f56d9" --window-size 48 --tooltip-text "Settings manager" $TTIPS & sleep 0.1
wmalauncher --desktop-file mxfb-help.desktop --tooltip-text "Help" --background-color "#1d2324" --border-color "#1d2324" --hover-background-color "#29353b" --hover-border-color "#0f56d9" --window-size 48 $TTIPS & sleep 0.1

@Melber I got the dockmaker to run after removing all of the #'s.

Before

Code: Select all

#!/bin/bash

#set up slit location
sed -i 's/^session.screen0.slit.placement:.*/session.screen0.slit.placement: TopLeft/' $HOME/.fluxbox/init

fluxbox-remote restart; sleep 1

# TOOLTIPS
TTIPS+=" --tooltip-show-delay       250"
TTIPS+=" --tooltip-text-padding     3"
TTIPS+=" --tooltip-border-size		3"
TTIPS+=" --tooltip-foreground-color #ffffff"
TTIPS+=" --tooltip-background-color #1d2324"

#commands for dock launchers

wmalauncher --desktop-file mx-tools.desktop --tooltip-text "MX Tools" --background-color #1d2324 --border-color #1d2324 --hover-background-color #29353b --hover-border-color #0f56d9 --window-size 48 $TTIPS & sleep 0.1
wmalauncher --desktop-file custom-toolbox-mxfb.desktop --background-color #1d2324 --border-color #1d2324 --hover-background-color #29353b --hover-border-color #0f56d9 --window-size 48 --tooltip-text "Settings manager" $TTIPS & sleep 0.1
wmalauncher --desktop-file mxfb-help.desktop --tooltip-text "Help" --background-color #1d2324 --border-color #1d2324 --hover-background-color #29353b --hover-border-color #0f56d9 --window-size 48 $TTIPS & sleep 0.1

After

Code: Select all

#!/bin/bash

#set up slit location
sed -i 's/^session.screen0.slit.placement:.*/session.screen0.slit.placement: TopLeft/' $HOME/.fluxbox/init

fluxbox-remote restart; sleep 1

# TOOLTIPS
TTIPS+=" --tooltip-show-delay       250"
TTIPS+=" --tooltip-text-padding     3"
TTIPS+=" --tooltip-border-size		3"
TTIPS+=" --tooltip-foreground-color #ffffff"
TTIPS+=" --tooltip-background-color #1d2324"

#commands for dock launchers

wmalauncher --desktop-file mx-tools.desktop --tooltip-text "MX Tools" --background-color 1d2324 --border-color 1d2324 --hover-background-color 29353b --hover-border-color 0f56d9 --window-size 48 $TTIPS & sleep 0.1
wmalauncher --desktop-file custom-toolbox-mxfb.desktop --background-color 1d2324 --border-color 1d2324 --hover-background-color 29353b --hover-border-color 0f56d9 --window-size 48 --tooltip-text "Settings manager" $TTIPS & sleep 0.1
wmalauncher --desktop-file mxfb-help.desktop --tooltip-text "Help" --background-color 1d2324 --border-color 1d2324 --hover-background-color 29353b --hover-border-color 0f56d9 --window-size 48 $TTIPS & sleep 0.1

[Jerry3904]

I've already uploaded Melber's changes and I'd like to see if that makes a difference before I return to this. Thanks.

[Joseph DeGarmo]

About the application launcher bug I reported on the KDE version, I installed the "Labeled Application Launcher" widget and applied that in place of the original application launcher. Functions like normal now. Temporary workaround until the original launcher gets fixed.