MX-23 beta 2 feedback thread

[Jerry3904]

Fluxbox:

Opening Settings Manager then clicking Edit results in a terminal prompt for root. (sudo password doesn't work.)

If running live, the root password (root) does open the config file (mxfb-settings.list) in Featherpad OK.

Chris

@Adrian Also: it might be better to generalize as well by using xdg-open instead, and there are a couple of error messages;

Code: Select all

About to execute /usr/bin/featherpad /etc/custom-toolbox/mxfb-settings.list.
This command needs root privileges to be executed.
Using su...
Enter root password at prompt.
Password: 
QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 1000
Gtk-Message: 10:09:37.747: Failed to load module "gail"

[dolphin_oracle]

Fluxbox:

Opening Settings Manager then clicking Edit results in a terminal prompt for root. (sudo password doesn't work.)

If running live, the root password (root) does open the config file (mxfb-settings.list) in Featherpad OK.

Chris

the edit button is still using su-to-root instead of pkexec. thanks.

[fehlix]

How to repair this broken pipe?

Code: Select all

/usr/sbin/dkms: Zeile 2497: echo: Schreibfehler: Datenübergabe unterbrochen (broken pipe).

You can repair like this:

Code: Select all

sudo sed -i.orig  '2497s/^/#/; 2497aif [[ $(stat -c %d%D /proc) == $(stat -c %d%D /) ]]; then'  /sbin/dkms

and check with re-installing the same package

Code: Select all

sudo apt reinstall rtl8821ce-dkms

and send a bug-report with the potential fix to debian/upstream
Or

Or could this be ignored?

You can ignore the message, and wait until someone else have fixed it.

[fehlix]

Fluxbox:

Opening Settings Manager then clicking Edit results in a terminal prompt for root. (sudo password doesn't work.)

If running live, the root password (root) does open the config file (mxfb-settings.list) in Featherpad OK.

Chris

@Adrian Also: it might be better to generalize as well by using xdg-open instead, and there are a couple of error messages;

Code: Select all

About to execute /usr/bin/featherpad /etc/custom-toolbox/mxfb-settings.list.
This command needs root privileges to be executed.
Using su...
Enter root password at prompt.
Password: 
QStandardPaths: runtime directory '/run/user/1000' is not owned by UID 0, but a directory permissions 0700 owned by UID 1000 GID 1000
Gtk-Message: 10:09:37.747: Failed to load module "gail"

No need to open featherpad as root, b/c User get authentication popup-prompt when trying to save anyway.
@Adrian
The Failed to load module message indicates a missing package:

Code: Select all

sudo apt install libgail-common

@m_pav

[Jerry3904]

@peter_li @fehlix That broken pipe caused totay's update to take up more than 30 mins and run the CPU at 100% on my little AAP 722 until I finally killed it. That is pretty much unacceptable in my book...

[fehlix]

I installed beta 2 in VirtualBox. Everything worked until I tried to remove all the locales I don't need.
In System Locales I unchecked everything except en_US.UTF-8.
Then I set that to be the default.
It fails and gives this error.

Code: Select all

Generating locales (this might take a while)...
en_US.UTF-8...[error] cannot open locale definition file `en_GB': No such file or directory
done
Generation complete.
*** update-locale: Error: invalid locale settings:  LANG=en_US.UTF-8
"Configure System Locales" canceled: exit [255]

I don't know why it's looking for `en_GB'. when that isn't selected.
It seems like this also happend earlier this year when I installed MX 21 but I don't remember how I fixed it.

what would this show:

Code: Select all

cat /etc/default/locale

and

Code: Select all

locale 

and

Code: Select all

locale -a

I fixed it before I read this reply.
I ran those yesterday but don't remember what was missing.
I do remember that /etc/default/locale only had LANG=en_US.UTF-8 but it was commented out.
I also had the same thing happen on Debian 12. Both installed with US English as the default language but it couldn't find `en_GB' for some reason. I ran sudo apt install --reinstall locales and then sudo dpkg-reconfigure locales on both MX 23 and Debian 12 and it generated the en_US.UTF-8 locale with no errors and without commenting out anything in /etc/default/locale.

Maybe you remember, how you "managed" to get this error. What settings have been selected when booted live
and when you run the installer. Anything changed like timezone and/or locale/language?
Also maybe mention what beta2 ISO you have installed, b/c we have some more than just one.
So anything like this would potential help first to reproduce and maybe also to fix the cause of the issue.

[fehlix]

@peter_li @fehlix That broken pipe caused totay's update to take up more than 30 mins and run the CPU at 100% on my little AAP 722 until I finally killed it. That is pretty much unacceptable in my book...

Maybe try the mentioned fix and re-install the *-dkms package involved. Also to proov (or not) the fix changed that not only the message is gone. Otherwise it maybe just the long dkms-build

[fehlix]

@peter_li @fehlix That broken pipe caused totay's update to take up more than 30 mins and run the CPU at 100% on my little AAP 722 until I finally killed it. That is pretty much unacceptable in my book...

Maybe try the mentioned fix and re-install the *-dkms package involved. Also to proov (or not) the fix changed that not only the message is gone. Otherwise it maybe just the long dkms-build

It takes here about 1 minute to install /reinstall

Code: Select all

sudo bash -c 'time apt reinstall rtl8821ce-dkms'
real	0m59.740s

either with or without the mentioned fix (to get away with the broken pipe message)

[Jerry3904]

I meant unacceptable for MX, not just for me.

[richb]

Whenever I see those updates to those rtl*** files I cringe. knowing that it will take an inordinate amount of time. I always wonder if the system has frozen but experience tells me it has not, Cringe worthy nonetheless.