MX-23 RC3 (Fluxbox) Feedback thread

[siamhie]

Dear @fehlix,

Thank you for your command "mxfb-menu-generator auto".

@Wallon You can also launch that command from the menu (root menu > all apps > update)

quickshot_230725_123746.png

This is what the menu entry looks like.

Code: Select all

[begin] (MX Fluxbox)
	    [submenu] (All Apps)
            [include] (~/.fluxbox/submenus/full_menu)
            [separator]
            [exec] (Update)  {/usr/bin/mxfb-menu-generator}
            [exec] (Disable) {mx-tweak --other}
   [end]

[Wallon]

Dear @fehlix ,

I'm not dreaming, your secret command line "mxfb-menu-generator auto" has an effect on Fluxbox applications.
@Melber noticed as I did that the "Common settings for MX-Linux Fluxbox" application was in English.
After your command line, the application was translated into French.
Do I have to do this manually after every MX installation?
You're really very good. It's magical!
Look at my printscreen, it's in French now! I wasn't dreaming.

Kind regards,
Wallon

[Wallon]

Dear @siamhie,

Yes, I had also done that in the menu (root menu > all apps > update) but I had written in this thread that it did nothing in my installation.
I think there's a bug in this menu line in fr_BE.
Nice font in your menu.

Kind regards,
Wallon

[Jerry3904]

Dear @fehlix ,

I'm not dreaming, your secret command line "mxfb-menu-generator auto" has an effect on Fluxbox applications.
@Melber noticed as I did that the "Common settings for MX-Linux Fluxbox" application was in English.
After your command line, the application was translated into French.
Do I have to do this manually after every MX installation?
You're really very good. It's magical!
Look at my printscreen, it's in French now! I wasn't dreaming.

Kind regards,
Wallon

Well, Adrian put out two updates yesterday to fix the problems, so IMO that might have had a slight effect...

[siamhie]

Dear @siamhie,

Yes, I had also done that in the menu (root menu > all apps > update) but I had written in this thread that it did nothing in my installation.
I think there's a bug in this menu line in fr_BE.

OK, cool. Hard to keep up with all issues during feedback. Will pay more attention next time.

Nice font in your menu.

Kind regards,
Wallon

Thanks. It's a font called monofur.

[Wallon]

Dear @Jerry3904

Good idea. I usually do these short help texts in 10 different languages, and will repeat that for this one by Final if still possible.

Here is the modified translation for fr_FR and fr_BE.
It's a modified translation because French speakers aren't as intelligent as English speakers. It's a little joke between you and me.

There are several pitfalls with DEEPL translations.

Example with lines;
1) Click Layout > Save as
You need to check in arandr how the word "Layout" has been translated.

4) Right-click the desktop > Settings > Configure > Startup
Check how the word "Startup" has been translated in the menu. In French, it is the word "Démarrage".
But I mentioned that the file that opens is called "Startup" in English.

Note;
When I installed MXFB, I had saved my "default.sh" file in the path wallon/.screenlayout/default.sh
I always do this when I install a Linux distribution.
I didn't know that with MXFB you had to save it in another directory.
So, this help file is really important and should be translated!

See you soon,
Wallon

[Wallon]

Dear @dolphin_oracle,

If the "compton-conf" package is installed on the MXFB ISO image, I recommend that you also add the "compton-conf-l10n" package for translations.

See you soon,
Wallon

[dolphin_oracle]

Dear @dolphin_oracle,

If the "compton-conf" package is installed on the MXFB ISO image, I recommend that you also add the "compton-conf-l10n" package for translations.

See you soon,
Wallon

got it.

[siamhie]

There's a post on the Facebook MX Linux group regarding the zenbleed vulnerability (https://www.phoronix.com/news/Linux-Mitigate-Zenbleed). Admin Andy replied that a patch was applied to all current versions MX Linux regarding the amd64-microcode package.

I see the package for Bullseye (https://packages.debian.org/bullseye/amd64-microcode) is dated for July but I've only got April's version.

quickshot_230728_172049.png

Seems Debian has moved this package from [security] [non-free] in Bullseye to [security] [non-free-firmware] in Bookworm (https://packages.debian.org/bookworm/amd64-microcode).


Here is what my debian.list shows in /etc/apt/sources.list.d/.

Code: Select all

# Debian Stable.
deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main contrib non-free
#deb-src http://deb.debian.org/debian bookworm main contrib non-free 

#debian backports
#deb http://deb.debian.org/debian bookworm-backports main contrib non-free

What's the best way to add the non-free-firmware to my debian-security list?

[dolphin_oracle]

There's a post on the Facebook MX Linux group regarding the zenbleed vulnerability (https://www.phoronix.com/news/Linux-Mitigate-Zenbleed). Admin Andy replied that a patch was applied to all current versions MX Linux regarding the amd64-microcode package.

I see the package for Bullseye (https://packages.debian.org/bullseye/amd64-microcode) is dated for July but I've only got April's version.


quickshot_230728_172049.png



Seems Debian has moved this package from [security] [non-free] in Bullseye to [security] [non-free-firmware] in Bookworm (https://packages.debian.org/bookworm/amd64-microcode).


Here is what my debian.list shows in /etc/apt/sources.list.d/.

Code: Select all

# Debian Stable.
deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main contrib non-free
#deb-src http://deb.debian.org/debian bookworm main contrib non-free 

#debian backports
#deb http://deb.debian.org/debian bookworm-backports main contrib non-free

What's the best way to add the non-free-firmware to my debian-security list?

open up a text editor and add it to the end of the deb security repo definition.

and thanks. I'm adding these to the build system. can't believe we missed that one!