Will apt-get update; apt-get upgrade bring my already existing installations to this version?
Yes, it does.
]]>Graphical issues with hover button occur on both Intel and NVidia. The latter with or without proprietary drivers.
]]>During installation, when I select the keyboard layout, it is applied in the target system but not during the live-session (stays US).
We are not able to reproduce, what keyboard layout did you choose throughout the install process ?
When installing on a LUKS Partition the tde mount daemon pops up after the partitions are created. It can be avoided by disabling encrypted HDs in the settings on the live media.
We can confirm that, added to our to-do list.
The Hover description on the menu icons is a bit strange sometimes. It shows small horizontal lines on the top, directly below the rounded top corners.
We are not able to reproduce, it may be a video driver dependent issue. Please specify your hardware.
The desktop profiler fails with error code 60 on some dependencies for the full profile 'synaptic-q4 : depends on: synaptic-trinity but should not be installed'
Fixed, that should work now.
Encryption in settings:/Security/ has no icon
We can confirm that, a solution is in progress.
]]>When installing on a LUKS Partition the tde mount daemon pops up after the partitions are created. It can be avoided by disabling encrypted HDs in the settings on the live media.
The Hover description on the menu icons is a bit strange sometimes. It shows small horizontal lines on the top, directly below the rounded top corners.
The desktop profiler fails with error code 60 on some dependencies for the full profile 'synaptic-q4 : depends on: synaptic-trinity but should not be installed'
Encryption in settings:/Security/ has no icon
]]>non-EFI/msdos:
/dev/sda1 / (includes /boot) ~4.5GB
/dev/sda2 /home ~5.5GB
EFI/gpt:
/dev/sda1 /boot/efi (non-encrypted FAT32, EFI required) 300MB
/dev/sda2/ (includes /boot and /home) ~9.7GB
So / and /home volume size arrangement are quite different. One could debate and perhaps consider if they shouldn't be similar in the same automatic partitioning option scheme. I do prefer the all-in-one / mount single-partition scheme. Manual partitioning is available to all other custom arrangements, encryption included.
]]>Now, since LUKS2 is available, ideally /boot should be separated from / and mounted on a LUKS1 encrypted partition while / (and other mounts/partitions) should be on LUKS2. If you can manage this it will be perfect! But hey, I can't complain as is. This should be a temporary solution, let's hope that GRUB doesn't take long to support LUKS2.
]]>@jotapesse
The final solution is the cleaner solution (b.), so we could leave Cryptsetup package untouched. Therefore Cryptsetup still defaults to LUKS2 for any of system operations except the Calamares install process. Keep in mind, Calamares encrypting on secure boot systems should work as well, but it might require some additional manual configuration before the first boot.
1. Calamares uses cryptsetup to encrypt;
2. Cryptsetup (currently version 2.1.0 on Debian testing) defaults to LUKS2;
3. GRUB currently only suppports LUKS1 and no other bootloader supports LUKS2 yet;
4. From the former, full-disk encryption with current Calamares/cryptsetup will always fail!
Solutions or workarounds:
a. Wait for GRUB to support LUKS2, if and when it will support it;
b. Explicitly use LUKS1 for /boot encryption (on Calamares?) with option "--type luks1" (the partition that GRUB loads/decrypts);
c. Replace Debian's cryptsetup by a custom built version with option "--with-default-luks-format=LUKS1" to default to LUKS1.
https://gitlab.com/cryptsetup/cryptsetu … leaseNotes
https://github.com/calamares/calamares/issues/1096
https://github.com/calamares/calamares/issues/1099
https://savannah.gnu.org/bugs/?55093
So (a.) isn't desirable and I don't know how easy it is to workaround Calamares with (b.). Perhaps the current best approach will be (c.) to Q4OS build and hold a custom cryptsetup package built with option "--with-default-luks-format=LUKS1", until (a.) or (b.) are resolved.
What do you guys think?
]]>Regarding Q4OS Centaurus 3.5, I look forward the Calamares install with Full Disk Encryption. I tried it on a Virtualbox install but it failed with grub not finding the device, both TDE and Plasma ISOs.
After a quite thorough investigation, we can definitely say, it's upstream Calamares bug already reported here: https://github.com/calamares/calamares/issues/1099 . You are welcome to post your findings at the Calamares issue tracker.
]]>