MX Linux Forum

chrispop99 wrote: Sun Jun 18, 2023 9:59 am 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

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"

chrispop99 wrote: Sun Jun 18, 2023 9:59 am 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

peter_li wrote: Sun Jun 18, 2023 4:11 am How to repair this broken pipe?

Code: Select all

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

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

sudo apt reinstall rtl8821ce-dkms

peter_li wrote: Sun Jun 18, 2023 4:11 am Or could this be ignored?

Jerry3904 wrote: Sun Jun 18, 2023 10:17 am

chrispop99 wrote: Sun Jun 18, 2023 9:59 am 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"

sudo apt install libgail-common

BV206 wrote: Sat Jun 17, 2023 8:46 am

fehlix wrote: Fri Jun 16, 2023 8:08 pm

BV206 wrote: Fri Jun 16, 2023 7:37 pm 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.

Jerry3904 wrote: Sun Jun 18, 2023 12:22 pm @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 wrote: Sun Jun 18, 2023 12:38 pm

Jerry3904 wrote: Sun Jun 18, 2023 12:22 pm @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

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