I think fstab should say '/dev/mapper/azura-dawn' instead of '/dev/azura/dawn'. Did the installer do that? Did you do automatic or manual partitioning?

tasksel --list-tasks

does not show me a task for standard system utilities. I don't know anything about the --new-install option.

aptitude search ~pstandard

shows me a list of 36 packages with priority Standard in chimaera. (it was 62 in beowulf)

apt-listchanges
bash-completion
bind9-dnsutils
bind9-host
bind9-libs
bzip2
ca-certificates
dbus
debian-faq
doc-debian
file
gettext-base
groff-base
krb5-locales
libc-l10n
liblockfile-bin
locales
lsof
man-db
manpages
media-types
mime-support
ncurses-term
netcat-traditional
openssh-client
pciutils
perl
perl-modules-5.32
python3-reportbug
reportbug
telnet
traceroute
ucf
wamerican
wget
xz-utils

beta2 amd64. This one booted in uefi for me. (hardware and qemu). I only booted bios in qemu, but I expect it works on hardware, too.

https://files.devuan.org/devuan_chimaer … p-live.iso

sha256sum

46b3866ea990956e2bffbf7c9efcf44cda623c6a60f30fc12aa8069e288438b6  devuan_chimaera_4.0.beta2_2021-09-04_amd64_desktop-live.iso

beta2 i386 (bios only)
https://files.devuan.org/devuan_chimaer … p-live.iso
sha256sum

1eda4236e82d54b95358d4c85632e04974a17cab30ced591985178bd05569358  devuan_chimaera_4.0.beta2_2021-09-04_i386_desktop-live.iso

There are four live isos. Which one did you use?

I'm not sure I understand the question. Right now, debian and devuan are out of sync with respect to "stable" and "testing". Chimaera will move to stable and be officially released when we fix a few issues with the isos and get the documentation written. After that happens, I expect work will begin on the next release.

It should be a matter of a few weeks, not a few months.

But as usual, bottom line is "When it's ready."

Lars, yes if you can test it again that would be good, and if possible get a screenshot or two of the partitioning scheme. Thanks.

So, the copy of refractainstaller-yad that I hacked into the desktop-live iso was an older version that I modified. Oops. It'll still work.

Right one is here and will be in the next build.
https://git.devuan.org/devuan/refractai … taller-yad

Maintainer says he has no idea but will give it some thought. Also "colord-insane is a wrath upon us since the beginning."

I can't figure out what colord does. I have libcolord2 on the two systems I checked, but not colord. One of those systems is chimaera with runit, and I have made bootable isos from that system using refractasnapshot. Maybe removing colord will fix it.

Wow. I'm stumped. The chimaera snapshot iso boots in vbox in beowulf but not in chimaera?
Things to try:

Boot the iso in chimaera using qemu. You might need more that 1024mb of RAM.
qemu-system-x86_64 -m 1024 -cdrom snapshot.iso

Add 'set -x' to the top of /etc/init.d/saned to see if you get more information from the script.

There is no init script for colord, but there is a systemd service file. I don't know if the lack of an init script is the problem. Was there ever one for colord?

Not sure what to do with this. I'll ping jaromil. He's the maintainer of colord.

apt-file find colord-sane
colord: /usr/lib/colord/colord-sane       
colord: /usr/libexec/colord-sane

Here are error messages when trying to run the experimental version of wicd in chimaera.

$ wicd-gtk
Traceback (most recent call last):
  File "/usr/share/wicd/gtk/wicd-client.py", line 41, in <module>
    import gtk
ModuleNotFoundError: No module named 'gtk'

$ wicd-cli
Please use --wireless or --wired to specify the type of connection to operate on.
No operations performed.

$ wicd-cli --wired
No operations performed.

$ wicd-cli --wireless
No operations performed.

$ wicd-curses

Runs
I can connect and disconnect wired. Sometimes.
It sees the one router in the house, but doesn't see the second router, which is 2 meters away. It also sees my neighbor's router. Also, iwlist does see the router across the room.

Select my router from the list and press right-arrow to configure gives the following error message.

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gi/overrides/GLib.py", line 664, in <lambda>
    func_fdtransform = lambda _, cond, *data: callback(channel, cond, *data)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1148, in call_update_ui
    self.update_ui(True)
  File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1161, in update_ui
    self.handle_keys(input_data)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1039, in handle_keys
    self.diag = WirelessSettingsDialog(pos, self.frame)
  File "/usr/share/wicd/curses/netentry_curses.py", line 502, in __init__
    self.encrypt_types = misc.LoadEncryptionMethods()
  File "/usr/lib/python3/dist-packages/wicd/misc.py", line 368, in LoadEncryptionMethods
    parsed_template = _parse_enc_template(enctype.strip())
  File "/usr/lib/python3/dist-packages/wicd/misc.py", line 408, in _parse_enc_template
    cur_type["required"] = __parse_field_ent(parse_ent(line, "require"))
  File "/usr/lib/python3/dist-packages/wicd/misc.py", line 380, in __parse_field_ent
    for val, disp_val in grouper(2, fields, fillvalue=None):
  File "/usr/lib/python3/dist-packages/wicd/misc.py", line 655, in grouper
    return zip_longest(fillvalue=fillvalue, *args)
NameError: name 'zip_longest' is not defined

In addition to the possibility of unknown breakage, there is the possibility of security vulnerabilities that will never be fixed and probably not even reported.

I tried wicd-gtk and wicd-cli from experimental. The gtk program does not start. The cli program gives an error message. (I'd have to try it again to get the message, but I gave up after five minutes.)

HELP! Is there a python programmer in the house?

Yes. And it's almost there. The desktop theme is still partly broken and there may still be some bugs in the installer isos. I don't think there's much else that needs to be done. Oh yeah. Write the docs.