MX-23 beta 2 feedback thread

[dolphin_oracle]

Dear @Jerry3904,

You need to review the localisation for [fr_BE].

When I save information from the Quick Info PC program, I get a window that opens and asks "Open with zzzFM"?
zzzFM is used by antiX and not by MX Linux.
I don't know if zzzFM is compatible with MX Linux.
I have used SpaceFM a lot with MX Linux but not zzzFM.

Even the "Exit Options" button is not translated into [fr_BE]!

the exit-options tooltip on the tint2 panel is coded into the tint2rc file. I'm not sure that file supports localization.

as for the "open file in zzzFM". apparently that's in the translation file. It should just be "Open Folder". Likely the translation was automatically pulled from antiX string source.

** fixed now. apparently the translations were updated on transifex the day after the last packaging. all good.

[dolphin_oracle]

Hello Everyone,

Today I bought a very good Samsung "Champagne Silver" 128GB - 400MB/s USB key to install MX Fluxbox 23 in the fr_BE language.

My day had started well but... it's not ending well. I have to stay calm because Eadwine Rose is keeping an eye on the forum.

I created the Live USB stick with Rufus as always. My stick is recognised straight away. I chose the language fr_BE and the time zone "Brussels". I run the md5 check and all the files are OK. My Belgian Azerty keyboard is recognised. It's different from the Azerty keyboard for France and that's a good thing.

I discover a Live key that mixes English and [fr] translations. I don't see many things translated into [fr_BE].

Three icons at the top of the screen don't work (Videos - Software - Install MX).

On the left of the screen, I have a dock with 3 icons. The tooltips are in English for;
1) MX Tools
2) Help
3) Settings Manager

If I click on the "Settings Manager" icon, the new window is all in English.
It's discouraging to translate...

If I click on the desktop, I get a half-English / half-French menu (see screenshot). It's really Pfffooouuuuu.

As the "Install MX" icon doesn't work and I couldn't find an option in the menu to launch the installation, I wasn't able to install MX FluxBox on my new Samsung USB key.

Honestly, what's going on?

Wallon

the side panel tool-tips do not support localization. the tool-tips are not produced from the desktop files, but from the entries in the .fluxbox/scripts/DefaultDock.mxdk file.

I believe we have already fixed the non-working links.

the "settings manager" is custom-toolbox. not sure why its not localizing. @Adrian . In my test some parts localize and some parts don't with fr_BE, but es_ES works much better.

[dolphin_oracle]

MX-23beta2 Fluxbox updated!

I like the new MXFB-tour, but I'm a little bit skeptical about its new fully transparent icon with the fully transparent description in the Polish localization...


https://imgur.com/S4rtV3F.png



Moderator: image changed to link, please read the forum rules

thanks, fixing the icon and dekstop file now.

[dolphin_oracle]

So what change do we need to make?

conky change made.

000000 ffffff

[maci01]

This error occurred during the first update. Just announcing. It should be a bluetooth driver.

Nastavuje se balík rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) …
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Done.
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)

8821cu.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-amd64/updates/dkms/

Sorry, this is my first bug report and I'm a beginner. Have a nice day.

[Joseph DeGarmo]

Testing the beta 2 live session for KDE. Thanks for fixing the gamepad bug as well as editing the system info screen and adding the Wayland session. One minor bug: When a USB gamepad is connected or has been disconnected and then logging out and starting a new Wayland session, the attemped login kicks me back to the login screen. WORKAROUND: After SDDM loads, wait 10 seconds without touching the keyboard, then input the password to login. That will fix the Wayland login issue. Rebooting may also fix the issue, but I cannot really test that in a live session. I'm not sure how to fix this bug, but it's nothing major as long as you perform the workaround.

It's also worth noting that when the USB gamepad remains connected and you log in by inputting the password without clicking on the password field, then you should be fine.

[Stevo]

I've ported over a PPA's GTK 4 current Celluloid,version 0.25 of an mpv frontend for MX 23 test, since I haven't installed it yet and don't know how it interacts with our GTK 3 theming in XFCE and compatibility in KDE. Also we can check out installing from MXPI's test repo tab now. Currently, Celluloid is the only application in the TR.

I don't know if there are any other GTK 4 apps in Debian at all, but it is supposed to be the future, and we might need a whole discussion thread on its theming issues if it's anything like GTK 3.

[dolphin_oracle]

I've ported over a PPA's GTK 4 current Celluloid,version 0.25 of an mpv frontend for MX 23 test, since I haven't installed it yet and don't know how it interacts with our GTK 3 theming in XFCE and compatibility in KDE. Also we can check out installing from MXPI's test repo tab now. Currently, Celluloid is the only application in the TR.

I don't know if there are any other GTK 4 apps in Debian at all, but it is supposed to be the future, and we might need a whole discussion thread on its theming issues if it's anything like GTK 3.

I believe file-roller is also gtk4. we learned alot about its themeing, and make sure to set the dark-mode switch in gconf to accommodate it.

and its nice to have things in test now...

[Stevo]

This error occurred during the first update. Just announcing. It should be a bluetooth driver.

Nastavuje se balík rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) …
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Done.
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)

8821cu.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-amd64/updates/dkms/

Sorry, this is my first bug report and I'm a beginner. Have a nice day.

I'm sorry, but I can't see any error...those messages are what we get with a successful module build and install!

[fehlix]

This error occurred during the first update. Just announcing. It should be a bluetooth driver.

Nastavuje se balík rtl8821cu-dkms (5.12.0+git20230215-1~mx23+3) …
Loading new rtl8821cu-5.12.0 DKMS files...
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Building initial module for 6.1.0-9-amd64
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
Done.
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)
/usr/sbin/dkms: řádek 2497: echo: chyba zápisu: Roura přerušena (SIGPIPE)

8821cu.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-9-amd64/updates/dkms/

Sorry, this is my first bug report and I'm a beginner. Have a nice day.

I'm sorry, but I can't see any error...those messages are what we get with a successful module build and install!

This issue is about the reported broken pipe "Error" within the dkms script itself at line 2497 with /sbin/dkms.
They do use "smart" logic to check whether /proc is mounted or not:

Code: Select all

# The <(cmd) idiom does not work if /proc is not mounted
if [ ! -e <(echo) ]; then
    warn $"dkms will not function properly if /proc is not mounted."
fi

I guess something changed in bash - but despite bash's broken pipe the test seems to work.