MX Linux Forum

the new version 3.12.1 works for me also

EDIT UPDATE: after reboot I still get...... Whoops! /run/nordvpn/nordvpnd.sock not found
This still is my normal way to get it to work. "sudo service nordvpn restart" then enter my password, then nordvpn c

I added the delay to the init script following all the instructions in post #19, then rebooted. I also still get the whoops sock error when using "nordvpn c"

I can still restart service to make it work, which is my new normal way to get it to work.

Just sharing what works and what doesn't work for ...

I am still not comfortable with the "auto login" as I have always been a password kind of guy
You may be able to lock your screen automatically immediately after login ( add sh -c 'sleep 3 ; xflock4' & to startup ). This isn't secure and is a temporary workaround.

You may be able to write ...

Thank you for the fast response. I was able to do more testing this AM, and did make some progress.
I switched to auto login.
After the desktop fully loads... I switch the foldable keyboard power switch to ON, and it connects as it should.

I am still not comfortable with the "auto login" as I have ...

Bluetooth Keyboard doesn't work at login screen. I have to use Bluetooth Devices to connect each time.

I am not even sure this is possible? I have no experience with Bluetooth Keyboards.
I have to use a different keyboard to connect to the foldable keyboard if I want to use the bluetooth wireless ...

I will wait until it is in the MX Test Repo since I don't see myself as a "Tester"... seeing how I still struggle as a "User".
Jim

No pressure intended, but how will I know when this is ready to try out? Where will I find it, "MX Test Repo"?
Jim

Open a terminal in the directory containing the unetbootin binary then run
./unetbootin-linux64-677.bin
and it will prompt you for your root password then its GUI comes up. I didn't test it further than that as I have no need or desire for unetbootin. The USB tools that MX comes with or have ...

"didn't work" tells us nothing. How exactly did you run the application, and what exactly happened?


"didn't work for me" really just means I have a low skill level. I didn't really mean to imply that anything was wrong with MX19, sorry if it sounded that way. At that time I would just get ...

I tried it again, chmod +x ... did work.
If you go into Properties->Permissions and check the box ... Allow this file to run as a program ... didn't work for me.
Thanks