Hello:

At fist glance, it would seem (to me) that your local config is doing something (?) that the live cd is not doing.
Hence the difference in behaviour.

See here.

You may want to consider following the procedure outlined in the linked page and see what gives.

That said, consider that cpu0 will always be on-line.
Check this and see what you get:

~$ cat /sys/devices/system/cpu/cpu1/online # <- 0 means off-line | 1 means on-line 
~$ cat /sys/devices/system/cpu/cpu2/online
~$ cat /sys/devices/system/cpu/cpu3/online

HTH.

Best,

A.

Hello:

See here for the available libxalan-c packages in Devuan.

I'd be wary of installing packages from outside the official repositories but if all dependencies are properly met, you may not run into any issues.

Best,

A.

See here.

Best,

A.

Hello:

It could well be.
The USB modem need to have the right firmware, matched to what services the telco offers through the SIM they sell you.

But, like I said, I've never used them.
You may need to check with the USB modem's OEM and also ask the telco issuing your SIM.

Again, cannot say.
I just found that bit of information and relayed it.

In my opinion, your best bet is to check with the telco/provider.
Sorry I cannot be of more help.

But please do let us know how you fared with this.
I'm sure it will be useful to someone further on.

Best,

A.

Hello:

I really could not say, I have only seen these once, long ago and on a friend's laptop, also with connectivity issues.

That said, a couple of the links I posted are from long ago and another from 2023.
So it would seem that that the problems you are having have been going on for the longest while but it also means that there may be more information out there.

I recall going through hell (ca. 1994) with a 14.4 USR Sportster dial-up modem and the undocumented AT commands I had to search for all over to get it to work properly, obviously not with today's web.

Not to mention the ridiculous amount of cash I had to pony up because of the endless amount of dropped dial-up calls caused (in this model) by a defective chip.

Best,

A.

Hello:

Happens ...

For Linux users, it is good practice and healthy for their billfold to avoid getting carried away with some apparently novel hardware, especially input hardware.
ie: keyboards/mice/touchpads/cameras

A constant example of this are the 'feature' buttons in some netbooks/laptops that, without the proper divers/modules, are mostly useless.
Even then, after a while the drivers/modules stop being maintained or supported and a kernel upgrade sends their usability down the loo.
An example I have at hand is my trusty ca.2009 Asus 1000HE and its hotkeys once supported in the Linux kernel.

The good practise I refer to above is best exercised before putting down the cash on the countertop.
ie: doing the due diligence and ascertaining that the device in question is Linux compatible and then checking in on-line fora if such claim is indeed true.

Bear in mind that most (if not all) that type of hardware is thought for and destined to MS Windows users, not the likes of us.

That said, after trying a great many known brand keyboards, in both MS and Linux environments, I ended up late in life with one of the first keyboards I ever used: a ca. 1995 IBM Type 'M' keyboard made by Lexmark.

I purchased it second (third/fourth?) hand, absolutely filthy but in good working order and with no missing kcaps.
After a very thorough cleaning plus the mandatory DIN/USB adapter graft it has been happily clicking away on my desk for the last 4 years or so.

It will surely outlast me.

Best,

A.

Hello:

Let me see ....
Yes, although it was not pertinent to the original subject matter, I did answer the question.

See?
Now, just to settle the confusion and nothing more:

Have a look here.

As you can see that package is WiCD only by name.

It is just a transitional package that works as a front end to any one of its listed dependencies:
ie: network-manager-gnome | network-manager | connman-gtk | cmst | connman-ui

From the README.Devuan file:

That said, it seems that Debian had a Python 3 version of WiCD in its experimental repository accepted in late 2019.

But it has not had any attention paid to it since then and something tells me that it will remain so.

Thanks for your input.

TG.

Hello:

Right ...

Another possible solution.
I'll have a look at that one too.

Thanks a lot for your input.

Best,

A.

Hello:

You're welcome.

I'd say completely remove KDE.
But cannot say much beyond that as I have never installed it, much less along another desktop.

Someone else here may have a suggestion on how to do that properly.

Best,

A.

Hello:

Good question.

I first came across Network-Manager long ago, when I moved around looking for a distribution that I felt comfortable with.
From what I have read on the forum lately, it seems it has only gotten worse.

Unfortunately, WiCD has been in abandoned state for the last 12 years or so.
There have been timid attempts to do something but without any result, like if it was a curse.

I'll have to see about something else.
But not Network-Manager.

So does xarchiver, it was a question of being able to 'Compress ...' from the PCManFM drop down menu and add a password just like you could do it when opening the application directly.

All it took was a suggestion to the maintainer who very rapidly acted on what he (also) thought was a good idea* and that was it.
* instead of replying something to the effect of why don't you do it yourself.   

Thanks for your input.

Best,

A.

Hello:

That sort of narrows things down a bit.

Right ...
Xserver definitely involved and may have an issue (?) with that xfce plug-in.
Not at all surprised.

When I first set up xfce, the first thing I discovered was that I had to get rid of anything xfce power management related.
But then I have a workstation, not a laptop.

That said, I don't think it anyone will be able to help past this preliminary evaluation unless you post some more data.
I certainly cannot.

You may want to consider posting:

1.
the dmesg printout

~$ sudo dmesg --level=alert,crit,err,warn

2.
the Xorg.0.log file

~$ cat /var/log/Xorg.0.log

You may also want to consider running a test by logging in as root and completely removing the xfce4-power-manager software package.

Then reboot and see if you can start the desktop without it.

~$ sudo apt-get purge --auto-remove xfce4-power-manager   

Using the purge options along with auto-remove, will get rid of everything regarding the xfce4-power-manager package.
That will be good for if/when you want to reinstall it again.
ie: (supposedly) no debris left behind.

Best,

A.

Hello:

You're welcome but it is really all IB's merit.

He is the one who has been keeping this very nice/useful (ca. 2005) application running and up to date for the last 9/10 years.

Best,

A.