Graphical installation is not meant for everyone?
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
1. It's impossible to choose Btrfs instead of ext4, without being forced to redo all the partitions from scratch.
2. It's impossible to choose a swap partition or swap file, without being forced to redo all the partitions from scratch.
3. I am unable to know what Trisquel 12 is choosing for me during installation. I'll only know after reboot the computer.
Using Ubiquity I have all these issues, while using Calamares I can avoid them... Why persist with Ubiquity?
When moving to from Trisquel 11 to Trisquel 12 I reformatted. As part of that I clicked on the "something else" (I think it was called?) in the installer and selected to use BTRFS and continued on my way.
Did you try the netinstaller? That is still a graphical installer although it is text-mode graphics, and it has more partitionning options.
Thanks jxself, I tried something similar but it didn't work.
I first installed Trisquel 12 by deleting the entire disk, then I repeated the installation by selecting "other"...
I typed "free -m" in the terminal to see the final result. Even though the RAM was only 2GB in size, Ubiquity created a 0GB swap file!
Thanks Avron, I'll try it when I have some free time.
However, even if the netinstaller worked better, I would be forced to give up on a normal or offline installation.
Please keep in mind that I did not ask for assistance.
I just wanted to point out that Ubiquity was not designed to be transparent and, in my opinion, it should not be used in an open Linux distro.
Completely free GNU/Linux distros usually take a bit longer to take new features, from well known working ones.
One of the main aims for ubiquity to stay is because it has a good support for screen reader. Last time I checked Calamares it didn't really had much support. That was long time ago, hopefully that has changed, we could revisit on the next release.
Cheers!
There is an old (closed) issue on the topic:
https://codeberg.org/Calamares/calamares/issues/470
But there is now a suggested work-around pointing to what may need to be fixed for Calamares to work with Qt6:
https://codeberg.org/Calamares/calamares/issues/1294#issuecomment-2861118
The last release annoucement is from February 2025, though:
https://calamares.io/calamares-3.3.14-is-out

