11th generation Intel graphics need a newer version of Mesa than is available in beowulf.

I don't think the Raspberry Pi should be used by anybody who values hardware freedom — not only does it depend on a blob for booting but they also switched to a proprietary Broadcom video card just as Panfrost was being finalised. Bastards. The entire platform is locked down by design.

And in respect of Talos the new POWER10 chips look to be fundamentally incompatible with their open hardware philosophy:

https://www.talospace.com/2020/08/power … t-but.html

Those are the only saved files. Upgrade to the new kernel, reproduce the error then reboot into the working kernel and post the .old file.

My search engine tells me you should check /var/log/lightdm or /var/log/slim.log.

Okay folks here's some rumour control:

https://github.com/audacity/audacity/pull/835 ← pull request that caused the issue

https://github.com/audacity/audacity/discussions/889 ← official response

Important points:

• the telemetry was always optional and disabled by default, it would never have made it into any packages[0]

• the telemetry has already been removed upstream along with some analytics for the big G

So no need for any fork at all really.

Several telemetry features are disabled via /usr/lib/firefox-esr/browser/defaults/preferences/firefox.js, with some patching to support this.

[0] Except perhaps for those poor fools trusting "universal" packaging "solutions" like snap & flatpak.

Have some faith in the developers, they won't let telemetry in the official repositories.

Devuan chimaera is based on Debian bullseye and that is currently frozen so the package versions won't ever change for that branch, only bug & security fixes from now on.

It would be created manually. How to add it depends on the installer used and I'm not sure how Devuan's works (sorry). I don't even know if the Devuan installer uses tasksel at any stage.

I'm running Debian buster on a ROCK Pi S as a media renderer front-end for mpd and I've managed to get that and upmpdcli running under supervision:

# sv check mpd
ok: run: mpd: (pid 1223) 561s
# sv check upmpdcli                                         
ok: run: upmpdcli: (pid 2054) 202s
# pstree
runit─┬─runsvdir─┬─runsv─┬─svlogd
      │          │       └─upmpdcli───13*[{upmpdcli}]
      │          └─runsv─┬─mpd───2*[{mpd}]
      │                  └─svlogd
      ├─sshd───sshd───sshd───mksh───pstree
      └─udevd───udevd
#

I followed the instructions in this thread:

• create /etc/sv/$service/log and the associated (executable) run files

• symlink the service directory to /etc/service/

• copy & divert the /etc/init.d/ script

• symlink /usr/bin/sv to /etc/init.d/

Here are the service run files if anybody's interested:

$ cat /etc/sv/mpd/run                                       
#!/bin/sh -e
if ! [ -d /run/mpd ]; then
        mkdir /run/mpd
        chmod 0755 /run/mpd
        chown -R mpd /run/mpd
fi
exec chpst -u mpd mpd --stdout --no-daemon /etc/mpd.conf
$ cat /etc/sv/upmpdcli/run                                  
#!/bin/sh -e
exec chpst -u upmpdcli upmpdcli -c /etc/upmpdcli.conf
$

The log run files are as described earlier (also executable).

Switched to runit in Debian bullseye:

It was surprising simple once I navigated the dependency maze caused by runit-init no longer being part of the init metapackage.

The only manual change I have to make is to write a runit script for iwd...

Almost:

# apt install -y kde-plasma-desktop plasma-nm

No but you can add a custom entry to tasksel with this file at /usr/share/tasksel/descs/kde-minimal.desc:

Task: KDE-minimal
Relevance: 2
Parent: desktop
Key:
Packages: list
   kde-plasma-desktop
   plasma-nm
Section: user
Description: Minimal KDE desktop
 .

Not sure if the installer actually uses tasksel but if it does then you could perhaps remaster it with this addition.

EDIT: 3-space tabs ftw.

If you want to keep Devuan booting into the latest kernel version without having to remember to update the bootloader configuration from MX then you can add this stanza to the end of the file at /etc/grub.d/40_custom in MX (replace $actual_uuid with the actual UUID of the Devuan root partition):

menuentry 'Devuan' {
   search --fs-uuid --set=root $actual_uuid
   linux /vmlinuz root=UUID=$actual_uuid ro quiet
   initrd /initrd.img
}

^ That boots the kernel & initramfs symlinks in the root partition that always point to the latest versions.

Run update-grub after saving the file to add the new menuentry. To remove the auto-generated menuentry for Devuan either uninstall the os-prober package or add this line to /etc/default/grub (in MX):

GRUB_OS_PROBER_SKIP_LIST=$actual_uuid

Then run update-grub again to update the menu.

It might be worth considering switching to Devuan for GRUB because their version supports Secure Boot whereas MX's does not. See my Secure Boot guide on the MX forums for more on this.

Only a fool learns from their own mistakes

The hardening-runtime package will apply several of those parameters automatically.

Note that the kernel tuning can be applied via /etc/sysctl.d/ if a bootloader-independent configuration method is required.