It works here in xfce (refracta ascii), but I'm not seeing the icon on the panel. I haven't checked to see if I did anything wrong.

Even better, it installs and runs in my nodbus beowulf, and the icon shows up on lxpanel. Testing in a live-iso running in a VM was less than ideal, and I didn't jump through all the hoops to get it to actually connect. I can do that with an installed system some time.

Thanks.

I'm no sudo expert, but you shouldn't have to mess with pam to allow a user to have certain commands with no password. First thing I would try is to just list the command with its full path but without the arguments. And maybe leave out the (ALL).

Maybe this:

os      ALL= NOPASSWD:  /sbin/wondershaper

It's not one of ours.

$ apt-file find /usr/share/themes/Shiny
mate-themes: /usr/share/themes/Shiny/metacity-1/metacity-theme-1.xml

I think the installer normally asks you for additional CDs early in the install. It's been a long time since i've done that. I do know that if you install without a mirror, there are some packages that won't get installed, such as wicd, firefox, and synaptic. If you want them, you'll need to install them afterward, even though they are on the installer media.

If you're having trouble with a particular package mirror, you can either use pkgmaster.devuan.org or select another from this list:
http://pkgmaster.devuan.org/mirror_list.txt. You might need to select one of the expert install options (graphical or not) to be able to put in any mirror you want.

The rc before the package name means that the package was installed previously, has been removed and left behind one or more config files. The original iso only has the four libraries listed, so you must have installed something that pulled in dbus and dbus-x11 and then removed it.

To get those two out of the list, purge them.  (Note: 'aptitude search ~c' will show you others that left behind config files, and 'aptitude purge ~c' will get rid of them.)

I don't know what HevyDevy is using, but I made some nodbus live isos to see how much I could install. It wasn't difficult, and I got a fairly complete set of desktop apps. You can read about it here:
https://dev1galaxy.org/viewtopic.php?id=2158

Newer isos than the link in that thread are here.
https://get.refracta.org/files/experimental/
(refracta9 is ascii, refracta10 is beowulf.)

It doesn't look like we have a pinebook image here: https://files.roundr.devuan.org/devuan_ascii/embedded/

It might be possible to install one of the other images and then migrate to devuan, but I don't see plain vanilla debian in the list that you linked. So a migration from something else to devuan might be difficult.

If you have a pinebook to play with, you have an opportunity to be the first one to make a devuan image for it.

Um, we did that. It's in /etc/os-release.  ID=debian magically makes third-party software work with devuan. I think there's another reason for it, but I don't remember what it is. What I don't get is why /etc/lsb-release doesn't override it like it used to.

Whoa! OK, so gdm is going to manage access to this encrypted home, user records will be json files to be more compatible with the internet (wtf?), and when you convert the json to a more traditional format, some metadata will be lost. (i.e. you won't see all that's in the user record.) 

What does "Queriable via Varlink interface." mean? Is it time to put on my metal hat?

Find the older package in /var/cache/apt/archives and install it wtih

dpkg --force-downgrade -i <package>

This one can often be fixed by adding RESUME=none to /etc/initramfs-tools/initramfs.conf and then running update-initramfs -u or my manually unpacking the initrd and removing the resume file before repacking it. I suppose it would also be valid to put the correct swap uuid in the resume file if you're planning to hibernate.

I don't know an initrd edit for this. You could try adding rootdelay=10 to the linux line in grub.cfg as suggested in the screen. If you know your way around grub command line, you could muck around there and see if you can find the root device yourself.

Does your laptop normally boot in uefi mode, like the one in the article you posted? Have you tried installing with gpt and uefi? Do you know if it needs a 32-bit bootloader to do that? If so, there's a way to use the amd64 desktop-live iso to install on such a system.*

It sounds like Ralph identified the problem. Get rid of that erroneous uuid, and it should work. (Run blkid to prove that the uuid doesn't exist, if you haven't already done that.)

* You would install the grub-efi-ia32 package that's in the root of the live system before you run the installer. When it asks about installing the bootloader, say No. Then run the installer, and when that asks about bootloader, let it install.
This was tested at least one time, on a macbook pro, by someone other than me.

_