Here's the fix for lightdm power buttons that we're currently recommending. This will be in the final version of the release notes.

Power buttons are disabled in lightdm login screen with elogind.
(See Debian bug #932047)

Add the following line to /etc/pam.d/lightdm-greeter

     session   optional pam_elogind.so

Before entering the chroot:

mkdir chroot-dir/run/udev
mount --bind /run/udev chroot-dir/run/udev

That will get rid of the repeated warnings on update-grub.

I don't remember how to get it to work automatically, but I know it needs geoclue-2.0 installed. I disabled that after one day and just use it manually. You can test with something like redshift -o -P -O 4800. If that doesn't work, I'll take a wild guess and say it's the nvidia driver. In that case, check nvidia-settings for a way to change the screen temp.

I think it's been ready since December. Read what others are saying:
https://dev1galaxy.org/viewtopic.php?id=3372

Confirmed. I can reproduce this in a beowulf nodbus live iso.

In another live iso with xfce and dbus, sound in firefox-esr works with or without firejail.

I don't really know how to debug this. Maybe something in the firejail profile files would give a clue, or maybe running with strace would show something.

python3.8 is also in chimaera (our next testing when beowulf goes stable).

ceres=sid=unstable

That's really weird. I've installed refractasnapshot in beowulf a few times. And isolinux is a real package.

$ apt-cache policy isolinux
isolinux:
  Installed: 3:6.04~git20190206.bf6db5b4+dfsg1-1
  Candidate: 3:6.04~git20190206.bf6db5b4+dfsg1-1
  Version table:
 *** 3:6.04~git20190206.bf6db5b4+dfsg1-1 500
        500 http://deb.devuan.org/merged beowulf/main amd64 Packages
        100 /var/lib/dpkg/status

Make sure you have all three lines in /etc/apt/sources.list and run 'apt update'

deb http://deb.devuan.org/merged beowulf main
deb http://deb.devuan.org/merged beowulf-updates main
deb http://deb.devuan.org/merged beowulf-security main

If that isn't the problem, try installing syslinux and isolinux first, then install refractasnapshot.

I burned the 3/25 iso to dvd, booted and got the udev warning. Pressing alt-F2 does nothing. Really nothing. I can't change to another tty. Pressinc ctrl-c seems to stop the warnings.

On another machine, I booted from a usb that has a regular install from a netinstall iso on it. When I got to the desktop, the keyboard was not working. Unplug/replug the keyboard fixed it.

Update: boot dvd on laptop, keyboard doesn't work, trackpad and trackpoint don't work. Can't unplug them.

I've been informed that when you get these repeating messages, you can make them stop by switching to tty2 and then back to tty1.

Press
alt-F2 and then alt-F1

It's normal for everything to be upgraded when you dist-upgrade from one major release to the next. It's also normal for there to be some new packages. That happens because package dependencies or priorities sometime change, or a source package that creates several binaries might get split up differently, and you'll get new names. (e.g. cryptsetup-run is a new one)

You should update again after installing a new keyring. I didn't think it worked without doing that.

I made another desktop-live iso with changes that I hope will address the udev delays. If anyone who was getting messages like the one below could test the new iso, it would be a big help. Thanks.

https://get.refracta.org/files/experime … p-live.iso

sha256sum
822ed7c7d3c456e60ba4041e8b2d43891c6853739b5fdcb16527eb041dbfe21e  devuan_beowulf_3.0.0_beta_2020-03-25_amd64_desktop-live.iso

You should be able to boot the dvd, go into rescue mode, get a network connection and install grub-efi-amd64. You don't need the -signed version unless you're using secure boot.

All the installation media (including desktop-live) boot with grub on uefi and boot with isolinux on bios. If you can't tell the difference by looking at them, you can test:
Press TAB to edit the boot command in isolinux.
Press e to edit the boot command in grub.
Press ESC to return to the boot menu - this one is the same for both.

If you're already booted into the system, check to see if /sys/firmware/efi exists. If it does, you booted in uefi mode.