Hello:

Welcome back ...
I was wondering what happened to your USB sticks. 8^°

Hmm ...
Could be, but then it would imply a severe hardware malfunction or BIOS problem.
USB ports have (should have) protection to avoid excess current draw and damage, particularly those that can be used for charging.
It is part of the design parameters of any on-board / external USB socket.

I see.

For the sake of completion to this thread, I think that it would be of interest to the forum (and you) to know some details.
[please humour me]

Reason?
Although not by any means the same quality of the legendary IBM T43 Thinkpad, today's Lenovo Thinkpad T400 is not a toy laptop on which such a thing would just happen, so it would be good to check a couple of things which may be of interest.

What brand and model are the USB sticks you used before and use now?
What does the dmesg printout say after you plug in one of the non-functioning sticks?

Please post the output.

With that same stick plugged in, please bring up gparted.
Does the stick show up? ie: /dev/sdx
If so, can you format it to 'cleared' first and then to 'fat32'?

Let's see if we can get to the bottom of this within a reasonable time frame.  8^D!

Best,

A.

Hello:

- no one really needs bleeding edge, choose your hardware carefully
- new & shiny is always expensive and isn't necessarily the best choice *
- avoid any and all NVidia stuff like the plague.
- AMD video cards are excellent and have much better Linux support

* I run Devuan on a ca. 2007 Sun Microsystems U24 WS purchased used and upgraded 11/2015

Best,

A.

Hello:

I got severely burned using rsync once, most probably my fault as it is really tricky to get right.
So I stopped using it but I rely on BackInTime which uses it without any issues.

Same here
NC was my preferred tool in those DOS/W3.11 days.

Best,

A.

Hello:

Indeed ...

As you can see, there does not seem to be a jami package in Debian stable:
https://packages.debian.org/search?keywords=jami
No idea why ...
But it is in unstable and experimental.

As a result, there is no jami package in Devuan Excalibur:
https://pkginfo.devuan.org/cgi-bin/poli … 1.84.27.71
ie: not in the Debian repositories? Then it will not be in the Devuan repositories.

Will the Daedalus version install/run on Excalibur?
Can't say, never used it.

That said, if it was in the Debian repositories and it is not there now (-> degraded to testing), there must be something going on.

Best,

A.

Hello:

Hmm ...
You may want to consider the possibility of the Excalibur installer becoming self-aware.
And as a result, defending itself from XFCE.

Just taking the piss ...

Best,

A.

Hello:

Of course ...  8^°

--->

Tech *bros* have to make a living. 
Make ends meet, if you will.
Have you not been observing?
There are still many landfills to fill.

<---

Yes, he would.

I take small confort in the fact that Civilisation (in general) has always had an incredibly over-abundant supply of [braindead / stupid / DHs / AHs]*.
That little snippet from the debian_dev only confirms it.

* choose one, a combination of two or even three. But a combination of four is not an option, lest depression set in.

Best,

A.

Hello:

I had thought of doing that but decided not to bother the chap with this.
But seeing that I have not made much progress, I just fired a short one asking.

Hopefully he will pitch in.

Best,

A.

Hello:

Yes, I'm quite sure of that as it seems (?) to be of their own production.
And it is part of the #! installation, at least for Bookworm.

But I have not seen it available for download or found it within the live i386 *.iso.

Thanks for your input.

Best,

A.

Hello:

Indeed.  8^D
And a just reward for your volunteer work too.

Best,

A.

Hello:

Yes.
A non-zero chance of there being extra obstacles is to be expected with a testing Suite.
ie: Maintained but Not Released status

+1

Best,

A.

Hello:

Same for my Daedalus installation with the exception of it not being a VM.

$ uname -a
Linux devuan 6.1.0-40-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.153-1 (2025-09-20) x86_64 GNU/Linux
$ 

For whatever reason, I have quite a few of those packages ...

$ apt list '~o' 
--- snip ---
libssl1.1/now 1.1.1w-0+deb11u1 amd64 [installed,local]
libswresample3/now 7:4.3.6-0+deb11u1 amd64 [installed,local]
######  <--- would have been listed here
libvpx6/now 1.9.0-1+deb11u2 amd64 [installed,local]
libwebp6/now 0.6.1-2.1+deb11u2 amd64 [installed,local]
--- snip ---
$ 

...  but libupower-glib1 is not one of them.

$ apt list '~o' | grep libupower-glib1
--- snip ---
$ 

That said, I do have libupower-glib3 installed ...

$ apt list | grep installed | grep libupower
--- snip ---
libupower-glib3/stable,now 0.99.20-2 amd64 [installed,automatic]
$ 

$ aptitude why libupower-glib3
i   task-desktop   Depends    xorg                                                              
i A xorg           Depends    xinit                                                             
i A xinit          Recommends xterm | x-session-manager | x-window-manager | x-terminal-emulator
i A xfce4-session  Provides   x-session-manager                                                 
i A xfce4-session  Depends    xfce4-settings                                                    
i A xfce4-settings Depends    libupower-glib3 (>= 0.99.0)                                       
$ 

... but no upower:

$ apt list | grep installed | grep upower
--- snip ---
libcpupower1/stable-security,now 6.1.153-1 amd64 [installed,automatic]
libupower-glib3/stable,now 0.99.20-2 amd64 [installed,automatic]
linux-cpupower/stable-security,now 6.1.153-1 amd64 [installed]
$ 

$ apt-cache policy upower
upower:
  Installed: (none)
  Candidate: 0.99.20-2
  Version table:
     0.99.20-2 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages
$ 

That upower package is a recommends from the hw-probe package which I do have installed ...

$ apt list | grep installed | grep hw-probe
--- snip ---
hw-probe/stable,stable,now 1.6.5-1 all [installed]
$ 

$ aptitude why upower
i   hw-probe Recommends upower
$ 

... but I do not allow recommends in my system.

Unless I am mistaken, your 'Installed' version is the same as your 'Candidate' version:
ie: apt says that is the correct version to have in your system.

Installed: 1:0.9.23-2+devuan1.3
Candidate: 1:0.9.23-2+devuan1.3

Being a recommends and not a hard dependency, you probably don't need it.
You may want to try purging the upower package and see if the obsolete package gets purged along with it.

Then if you get complaints from the system, just reinstall it and see what gets dragged in along with it.

Please let us know how you fared.

Best,

A.