A couple of additional notes:

If you don't have the kernel metapackage installed (e.g. linux-image-amd64) then you won't get the new kernel automatically on dist-upgrade and will need to install linux-image-4.9.0-4-<arch> or install the metapackage and dist-upgrade again. After installing the new kernel, you should reboot, so you're running the new kernel.

You might lose policykit-1 on the dist-upgrade. Unless you're a stoic minimalist, you'll want to reinstall it.

If you're upgrading from debian jessie or stretch, you'll need to remove systemd and systemd-shim after the upgrade. You might need to reinstall some other packages, too.

If you're upgrading from debian with gnome, you are a glutton for punishment, and you are heading for a big adventure. It can be done, but a fresh install would be easier and faster.

You need the ascii-backports kernel. (4.10 or newer, so plain ascii won't do it.) I did put an iso up, but it was meant for one person. It was only there for a few hours. Been thinking about putting up another one. (One that doesn't have a copyrighted desktop background) But I wanted to wait until after the regular ascii isos were up before I do the bpo. Guess that's not helpful for all you razor-edge ryzenistas.

Lemme figure out which VM has the right system, whether or not 'less' is installed, add the bpo kernel, and upload it. I guess it'll happen later today.

If /dev/sda15 contains an encrypted filesystem, then fsck should not be trying to check it. Instead, it should be checking the decrypted filesystem, which would be /dev/mapper/sda15_crypt or some other label.

What's in your /etc/fstab and your /etc/crypttab?
What's the output of blkid?
Is devuan the only operating system on the computer?

Wasn't that fixed a year ago?
https://security-tracker.debian.org/tra … -2016-5195

Yeah, I see this frequently. I use pmount/pumount for removables. I think I get leftover directories under /media when I pull the usb out without unmounting it. It might be something else I'm doing, too. When it happens, I just delete the dir (as root.)

You probably should have come here before anwering Yes to that. To fix it, you can boot a live CD or usb, chroot into the installed system and re-install or do whatever to get those packages back. There's not enough information in your post to know what caused the problem. How was that system different from the others you upgraded?

I think you overestimate my abilities. I've heard some talk about recompiling for alsa, and also that packaging firefox is difficult. After a quick look at the source package, I believe it. Doesn't apulse work anymore?

BTW, noscript is ready for 57. Support for noscript in firefox-esr52 will continue until June, when it will shift to 59.
https://noscript.net/getit

I ran into similar problems when I tried to use my conkyrc from jessie on a new ascii install.

Add conky.config = {and put the rest in braces}
Add a space after the =
Add a comma at the end of each line except the last.
Values go in single quotes, booleans don't.

Do that much, and you'll probably get rid of most of the errors. Some of the options may have changed. Here's what's working for me:

conky.config = {
    alignment = 'bottom_left',
    background = true,
    border_width = 1,
    cpu_avg_samples = 2,
	default_color = 'white',
    default_outline_color = 'white',
    default_shade_color = 'white',
    draw_borders = false,
    draw_graph_borders = true,
    draw_outline = false,
    draw_shades = false,
    use_xft = true,
    font = 'DejaVu Sans Mono:size=10',
    gap_x = 4,
    gap_y = 4,
    minimum_height = 5,
	minimum_width = 10,
	maximum_width = 366,
    net_avg_samples = 2,
    no_buffers = true,
    out_to_console = false,
    out_to_stderr = false,
    extra_newline = false,
    own_window = true,
    own_window_class = 'Conky',
    own_window_type = 'desktop',
    own_window_transparent = true,
    stippled_borders = 0,
    update_interval = 1.0,
    uppercase = false,
    use_spacer = 'none',
    show_graph_scale = false,
    show_graph_range = false
}

To see what driver is in use, look in /var/log/Xorg.0.log or run 'lspci -k'.
To select which driver to use, create /etc/X11/xorg.conf with a Device section, where you list which driver to use.

For detailed instructions on configuration, look at debian. It's done the same way in devuan.

Translation: Too much javascript.
(fungus obviously has a lower threshold than my limit of 4-5 allowances. I could see it fine once I unlocked a few doors.)

It looks like you could just replace the systemd commands with non-systemd commands. I don't know i3. How does it handle running those commands as root? Or does user have privilege for the shutdown and reboot commands? For hibernate and suspend, you can use 'pm-hibernate' and 'pm-suspend'.

Whenever I use a window manager without a diplay manager, I give my user sudo nopasswd permission for those commands.

It's also possible to let dbus manage the session, and then you can use dbus commands for shutdown, etc. I think that's been discussed somewhere on this forum. If you need that and can't find it, just say so.

This looks like the easy solution. No idea here if it works. (Note: Tags to put this in a code box are right above the message text box when you're composing.)

#!/bin/sh
lock() {
    i3lock
}

case "$1" in
    lock)
        lock
        ;;
    logout)
        i3-msg exit
        ;;
    suspend)
        lock && pm-suspend
        ;;
    hibernate)
        lock && pm-hibernate
        ;;
    reboot)
        reboot
        ;;
    shutdown)
        poweroff
        ;;
    *)
        echo "Usage: $0 {lock|logout|suspend|hibernate|reboot|shutdown}"
        exit 2
esac

exit 0