You are not logged in.
You're right. The amd64 desktop-live beta iso doesn't boot in uefi. I'm not sure what happened, but I just made a beta2 and it works. I will upload that and make the other three isos some time in the next day or two.
There are four live isos. Which one did you use?
The desktop-live iso should boot on uefi. The minimal-live is bios only. Image a usb thumb drive using dd or cat to the whole device (not a partition). Did you use a different method or burn an optical disk?
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."
Your bug report was not removed. There seems to be a problem with BTS today. I'm getting '502 bad gateway' when I try to access any bug reports. Word has been passed along to the web wizards, and I'm sure it will be corrected soon.
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.
Look in /var/log/apt/history.log to see what was recently installed or removed. Something related to policykit or elogind might be missing. You shouldn't need to enable sudo for these things in kde.
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
Chimaera desktop-live beta isos are available at your favorite iso mirror.
https://www.devuan.org/get-devuan
I hacked in the fixes for desktop-base (menu icons and desktop background) and also hacked in a fix for refractainstaller to remove the scary warning in the first screen. These changes will be in the next build of the packages and in the repo soon.
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.
if ssh server is installed in the snapshot, add the following to the qemu line:
-device e1000,netdev=user.0 -netdev user,id=user.0,hostfwd=tcp::5555-:22
And then you can ssh in with
ssh -p5555 user@localhost
where user is the actual username.
Note: in the qemu options above, 'user' does not get changed to the real username.
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
1GB? A standard system install uses around 900MB, so I guess that can work. I have noticed that encrypted installs in qemu require 2GB RAM to boot. Is that limited, too?
Did you have to edit /etc/crypttab and /etc/fstab to get it to work?
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
Check these first:
https://bugs.debian.org/cgi-bin/pkgrepo … age=openrc
Edit: Hm, no response on one since February and no response on the other since May 2020. I guess bug reports don't help in this case. Maybe talk to parazyd or Adam Borowski. They might have more information.
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?
I've done single partition encrypted installs, with or without lvm, and they worked. Maybe some more details about your setup would give us a clue to what went wrong.
Welcome back.
Will it eventually just morph into the release by doing the updates?
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.
If you answer 'yes' to that first firmware question, you are expected to provide the actual files (not packages) on removable media (usb stick).
We use a modified version of debian-installer. Debian does not provide non-free firmware in their official isos, so they have that question for people who need the wireless firmware to do the install.
We put the firmware packages in the iso, but we still have to keep that question there for people who have hardware that requires firmware that we don't include for legal reasons, like some broadcom chips.
Even if you say 'no' to that first question, non-free firmware will be installed if you need it. That's because the packages are in the iso and the installer will install what's in the iso. (Unless you choose expert and decline the later questions.)
Wicd is no longer maintained and is not in chimaera or ceres repos. However, someone in IRC yesterday mentioned that wicd did not get removed when they upgraded from beowulf to chimaera. So I decided to try it.
On my laptop running chimaera with xfce, I removed connman, added a single line for beowulf main repo, ran 'apt update' and then 'apt -t beowulf install wicd-gtk'. Below is posted a copy of my apt history.log showing what else got pulled in. (Disclaimer: I have not checked versions of any those packages to see which repo they came from.)
I tested wired and wireless connections, and wicd seems to be working normally. I commented out the beowulf line and ran 'apt update' again when I was done.
Start-Date: 2021-08-21 18:57:13
Commandline: apt -t beowulf install wicd-gtk
Install: python-gtk2:amd64 (2.24.0-5.1+b1, automatic), wicd-gtk:amd64 (1.7.4+tb2-6+devuan1.1), python-is-python2:amd64 (2.7.18-9, automatic), python2-minimal:amd64 (2.7.16-1, automatic), python2:amd64 (2.7.16-1, automatic), libglade2-0:amd64 (1:2.6.4-2+b1, automatic), libpython2-stdlib:amd64 (2.7.16-1, automatic), python-dbus:amd64 (1.2.8-3, automatic), python-pkg-resources:amd64 (40.8.0-1, automatic), python-glade2:amd64 (2.24.0-5.1+b1, automatic), python-cairo:amd64 (1.16.2-1+b1, automatic), python-numpy:amd64 (1:1.16.2-1, automatic), wicd-daemon:amd64 (1.7.4+tb2-6+devuan1.1, automatic), python-gobject-2:amd64 (2.28.6-13+b1, automatic), python-wicd:amd64 (1.7.4+tb2-6+devuan1.1, automatic)
End-Date: 2021-08-21 18:57:28
Edit: OK, I checked two packages. python-gtk2 and python-dbus are from beowulf. I don't yet know if I broke anything that depends on python3.
KDE and lxqt are choices in the tasksel menu. If you have a network connection during installation, you can install them. The statement about CD and DVD only apply to off-line installs.
Ignore that first question about missing firmware. There's wireless firmware in the iso, and it will be installed if you need it. If you don't want non-free firmware, choose Expert install to get some extra questions about that.
This package is in debian and devuan:
orphan-sysvinit-scripts
apt-file list orphan-sysvinit-scripts
orphan-sysvinit-scripts: /usr/lib/orphan-sysvinit-scripts/mapping
orphan-sysvinit-scripts: /usr/lib/orphan-sysvinit-scripts/update_init_d.sh
orphan-sysvinit-scripts: /usr/share/doc/orphan-sysvinit-scripts/README.Debian
orphan-sysvinit-scripts: /usr/share/doc/orphan-sysvinit-scripts/changelog.gz
orphan-sysvinit-scripts: /usr/share/doc/orphan-sysvinit-scripts/copyright
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/dirsrv
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/dirsrv.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/dnscrypt-proxy
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/dnscrypt-proxy.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/gpsd
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/gpsd.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/iwd
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/iwd.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/network-manager
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/network-manager.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/nftables
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/nftables.md5sum
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/tomcat9
orphan-sysvinit-scripts: /usr/share/orphan-sysvinit-scripts/tomcat9.md5sum
Nixer, big thanks for the report.
libreoffice should have been taken off the autoremove list along with other things when you installed task-xfce-desktop. You're sure it's still there and didn't get removed again behind your back?
The commands I posted for you are from the release notes of refracta gnu/linux. I wrote that part about 10 years ago, and I've used it multiple times over the years. It really is just like mounting any other data partition.
On the other hand, if you try to share system files between two different systems, you'll probably run into some interesting problems we've never seen before. But that would happen with or without lvm.
I don't know if it's related, but I had 'Debian' in my boot menu until I installed lsb-release so that the lsb_release command in /etc/default/grub worked, and I then got 'Devuan' in the boot menu.