MX-23 beta 1 feedback thread

[dolphin_oracle]

Ok

[siamhie]

we seem to no longer have this working to get to the page that handles the theme

Code: Select all

mx-tweak --theme

Tried on two different machines with MX-21 and MX-23 @dolphin_oracle

@Jerry3904 Works for me just not on the fly anymore. Only applies to newly opened windows. Tested with Thunar open.
The Window Manager section does work on the fly. MX-23. Haven't tested MX-21.

[dolphin_oracle]

Now that we have this working in MXFB to get to the page that handles the All Apps disable

Code: Select all

mx-tweak --other

we seem to no longer have this working to get to the page that handles the theme

Code: Select all

mx-tweak --theme

Tried on two different machines with MX-21 and MX-23 @dolphin_oracle

found the problem. dumb logic on my part. will have fixed tonight.

[Jerry3904]

[siamhie]

Thanks @dolphin_oracle


@Jerry3904 When I use the traditional toolbar (Appearance > Toolbar > Fluxbox) I have a new message in .xsession-errors.

Code: Select all

Failed to read: session.screen0.systray.pinLeft
Setting default value
Failed to read: session.screen0.systray.pinRight
Setting default value

Following this thread (#168 Feature: Make systray icon pinning (ordered) available https://sourceforge.net/p/fluxbox/patches/168/)

I found this in the fluxbox.txt document. Line 1290 (https://github.com/fluxbox/fluxbox/blob ... luxbox.txt)

Code: Select all

*session.screen0.pin{Left|Right}*: 'classes'::
Sort the system tray icons according to order specified in 'classes', which is
a comma-separated list of CLASSCLASS properties of the X clients (The second
field of WM_CLASS from the output of the *xprop(1)* utility).
+
Consider a system tray "A C B D E F". With pinRight set to "A, B" and pinLeft
set to "E, F" it will look like "E F [C D] A B" while the icons in [] are
unordered as usual.

All of the 'location' resources following require a pathname to their specific
files. This is where you can specify different files. Most of the defaults will
be located in the user's *~/.fluxbox* directory.

I added these two variables (as a default) to my init file and the error message disappears.

Code: Select all

session.screen0.pinLeft: E, F
session.screen0.pinRight: A, B

[Jerry3904]

Got it, thanks.

[oldandtired]

Hi. I just installed the beta on my old Dell Latitude E6220, with 8GB RAM and ~120GB root partition using btrfs.

The nala upgrade sticks on unpacking papirus-icon-theme (20230601-0.1-mx23+1 over 20230104-2), at 5.3%. The same happens on apt upgrade, apt-get upgrade etc, unsurprisingly.

After ctrl-c-ing out of nala I had to kill the stuck dpkg process.

I then marked papirus-icon-theme as held with apt-mark, and the update continued as expected.

So at first glance it looks like an issue with that icon package. Hope this helps.

[siamhie]

Got it, thanks.

@Jerry3904
Disregard that init post. I can't seem to replicate it anymore.
I removed those extra entries and have either logged out and in or rebooted several times for the past 15 minutes but the message doesn't reappear.
I don't know what could have triggered it but maybe it has something to do with MX Tweak because I was testing all the settings when I saw your initial post to dolphin.

I am getting a new message but I will wait for the update to MX Tweak.

Code: Select all

tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes
Usage: tint2 [OPTION...]

Options:
  -c path_to_config_file   Loads the configuration file from a
                           custom location.
  -v, --version            Prints version information and exits.
  -h, --help               Display this help and exits.

For more information, run `man tint2` or visit the project page
<https://gitlab.com/o9000/tint2>.

[dolphin_oracle]

Hi. I just installed the beta on my old Dell Latitude E6220, with 8GB RAM and ~120GB root partition using btrfs.

The nala upgrade sticks on unpacking papirus-icon-theme (20230601-0.1-mx23+1 over 20230104-2), at 5.3%. The same happens on apt upgrade, apt-get upgrade etc, unsurprisingly.

After ctrl-c-ing out of nala I had to kill the stuck dpkg process.

I then marked papirus-icon-theme as held with apt-mark, and the update continued as expected.

So at first glance it looks like an issue with that icon package. Hope this helps.

the papirus icon theme takes forever to update. its highly compressed. so you very likely just didn't wait long enough. I mean it takes a loooonnnnnngggggg time.

[markol]

Just wanted to say (again) I'm running MX23KDE beta in two VMs and one laptop... and no problems so far. Thank you!