[rant]
Moral of the story: The Crucial BX500 series SSDs are utter crap.

Of that pair of SSDs, one is dead as a doornail (doesn't register on the bus), the other is clearly dying.
Both are less than a year old and still under warranty, but I'll be throwing them in the trash rather than returning them - the last thing I want is more of the same.
Both have history of hitting ~70c and thermal throttling under sustained write loads, despite the enclosure and the drives directly above them never breaking 26c.
The nasty plastic casing never even gets warm, and now that I've dissected one I see somebody at crucial thinks putting a thermal pad on the controller is a luxury. 70c is listed as max operating and they never exceeded it, but I'll bet a cookie heat is why they died.

Crucial, your budget SSD line gets a solid F from me. The Kingston A400 series is not only cheaper, it's also built properly and doesn't constantly try to cook itself.
I wanted budget SSDs for that filesystem, and expected budget performance. What I didn't expect was something so shitty it can't even sustain the already mediocre performance numbers without overheating.
FWIW, a BX500 reporting 70c writes at ~7MB/s.
[/rant]

Bathory - In Nomine Satanas

https://www.youtube.com/watch?v=8EsKxXcB9hU

How are you attempting to update your system?

I would use

# apt update
# apt upgrade
# apt full-upgrade

Or perhaps

# apt update
# aptitude safe-upgrade
# aptitude full-upgrade

Note that full upgrades are sometimes needed in testing/unstable because obsolete packages have to be removed. Also note that full upgrades can break testing/unstable systems if a transition is underway.

https://release.debian.org/transitions/

I just apt update/upgraded my system, and these all upgraded without incident. Except 3 python2 packages - there has been some funny business with python2 for a while.

I am happy to announce that iwd is now forked for Devuan! You can see the package information at pkginfo.devuan.org. I would like to thank Mark Hindley for guiding me on this.

And because we have to fork iwd to make it work for Devuan, it unfortunately means that both the upstream and Debian maintainer are not interested in supporting sysvinit. I hope they change their mind, not only because I don't want to maintain this fork forever, but also because this is a bad path for GNU/Linux.

Anyway, since this thread was supposed to be about my xfce4-alsa-plugin, I decided to package it for Debian. I'm currently finding a sponsor at mentors.debian.net. Once it gets accepted to the main archive, I will ask the xfce4 metapackage maintainers to consider not depending on xfce4-pulseaudio-plugin, but on xfce4-pulseaudio-plugin | xfce4-alsa-plugin, so that Xfce users have a choice between PA and Alsa on their panel. That's the main goal I had on mind when packaging xfce4-alsa-plugin.

brocashelm wrote:

I don't mean to hijack this thread, but I also use VeraCrypt and have a different problem at the moment.

As I like to tinker with security, I installed the LibPAM-TMPDIR package, only to find out that VeraCrypt can't "see" that I have mounted volumes, thus no ability to unmount them through the software. I could do it through the system, but it leads to a bit of a mess. How would I go about fixing this without removing the package? Do I need to set a specific mount path for VeraCrypt? If so, that would be appreciated.

Are they veracrypt volumes?

Maybe dont hijack this thread and create a new thread as your issue has nothing to do with the OP.