MX Linux Forum

I've been following the recent flurry of news on the critical+ vulnerability in xz-utils, and it seems like the affected version (xz-utils V5.6.0, V5.6.1) hasn't made it into MX23 at this time. Furthermore, it looks like the version of openssh-server that's provided with MX23 doesn't link in xz ...

https://www.openwall.com/lists/oss-security/2024/03/29/4

Seems it does not to affect Debian stable, but does affect testing / unstable.

"openssh does not directly use liblzma. However debian and several other distributions patch openssh to support systemd notification, and libsystemd does depend ...

Also, now that I think about it, the whole approach is misguided, because (1) not everything under /home is the homedir of a user, (2) not every user has their $HOME under /home, (3) it's probably not a good idea to modify random files without user's approval.

For example, some users could have ...

Well, yeah. My last bit of advice above was to use a simple glob (for i in /home/*/config/menus/applications-merged/mx-tools.menu) and ditch "find". Then you wouldn't have had any problems. Anyway, good luck.

To @delphin_oracle or whoever wrote the postinst script of desktop-defaults-mx-common, I can't reply to the announcement, so I'm posting here. Here's what that piece of... beauty (/var/lib/dpkg/info/desktop-defaults-mx-common.postinst)... looks like, and how to fix it (see "# ME:" comments ...

I did a strace and the system is reading (unpacking?) thousands upon thousands of file access requests

This package (papirus-icon-theme) takes an immense time to upgrade. Even on SSD. And it is inconsequential. How can I most easily avoid it being marked for an upgrade ?

I've been waiting for this problem to go away (for the repos to catch up) for a couple of days already.

netix.net is the mirror that MX selects upon a default install. I've never messed with MX package / MX repo manager stuff, and I don't really want to; I just use plain Debian commands. Do I now ...

Hm... I am not sure what you're talking about WRT NTFS trouble but I am using frugal installs (first MX18.3, now 19.3) on three PCs, with all frugal files stored on standard NTFS partitions, and have never run into any problems (not to mention minutes-long delays :confused: ). I also had TLP ...

Yes, there is no other way that runs smoothly WRT rollbakcs. I understand that.

Problem is, you may run out of space on the mx-frugal partition (though you may have plenty elsewhere). It would be nice to have a simple `--target-dir` CLI option to save the remaster & new rootfs elsewhere (and deal ...