calamares issueshttps://gitlab.manjaro.org/applications/calamares/-/issues2024-03-27T17:13:48Zhttps://gitlab.manjaro.org/applications/calamares/-/issues/88microcode hook in initcpiocfg conflicts with postcfg or postcfg conflicts wit...2024-03-27T17:13:48ZFrede Hmicrocode hook in initcpiocfg conflicts with postcfg or postcfg conflicts with initcpioAs both microcode images is installed on the ISO root filesystem - it has been configured in postcfg to remove the obsolete microcode image based on the host CPU.
Since initcpiocfg and the following initcpio will add both microcode to i...As both microcode images is installed on the ISO root filesystem - it has been configured in postcfg to remove the obsolete microcode image based on the host CPU.
Since initcpiocfg and the following initcpio will add both microcode to init - the target system will experience boot failure as the postcfg removes one of the microcode packages with out updating initfs.
https://gitlab.manjaro.org/applications/calamares/-/commit/60c5f3fd5ad4232a6b7e605cffa59e797ebea0f6#note_31737
https://forum.manjaro.org/t/iso-calamares-grub-issue-ucode/158906/12https://gitlab.manjaro.org/applications/calamares/-/issues/85Calamares 3.3.x encrypted install2024-02-29T05:46:03ZFrede HCalamares 3.3.x encrypted installI usually do not test encrypted installs - I made an exception
## ISO 20240222 with v.3.3.1
## first test case
Selected
- Erase disk
- Swap with hibernate
- Filesystem **ext4**
- Tick encrypt option
- Enter encryption phrase twice (UI ...I usually do not test encrypted installs - I made an exception
## ISO 20240222 with v.3.3.1
## first test case
Selected
- Erase disk
- Swap with hibernate
- Filesystem **ext4**
- Tick encrypt option
- Enter encryption phrase twice (UI responds OK)
### Expected result
full-disk-encryption
### Actual result
Installation is fully encrypted.
## second test case
Selected
- Erase disk
- Swap to file
- Filesystem **btrfs**
- Tick encrypt option
- Enter encryption phrase twice (UI responds OK)
### Expected result
Full-disk-encryption
### Actual result
No encryption
## ISO 20240225 with v.3.3.2
I have tested calamares installer in various ways and it usually works.
However - as of February 25. 2024 the installer behaves weird when chosing to encrypt the installation.
## first test case
Selected
- Erase disk
- Swap with hibernate
- Filesystem **ext4**
- Tick encrypt option
- Enter encryption phrase twice (UI responds OK)
### Expected result
full-disk-encryption
### Actual result
Only swap partition is encrypted.
## second test case
Selected
- Erase disk
- Swap to file
- Filesystem **btrfs**
- Tick encrypt option
- Enter encryption phrase twice (UI responds OK)
### Expected result
Full-disk-encryption
### Actual result
No encryptionhttps://gitlab.manjaro.org/applications/calamares/-/issues/83Contributing merge request for interactive pacman-mirrors2023-10-04T03:08:15ZLawrence R. SteegerContributing merge request for interactive pacman-mirrorsLets the installing user select the mirrors to be used in the new target system during installation.
Forked branch is available at [interactive_pacman-mirrors](https://gitlab.com/lsteeger1/calamares/-/tree/Interactive_pacman-mirrors?ref...Lets the installing user select the mirrors to be used in the new target system during installation.
Forked branch is available at [interactive_pacman-mirrors](https://gitlab.com/lsteeger1/calamares/-/tree/Interactive_pacman-mirrors?ref_type=heads).
Related to [Add the ability to choose Mirror by country during the installation](https://gitlab.manjaro.org/applications/calamares/-/issues/39); but does not get down to directly selecting a country.
The resulting dialog allows for sorting by clicking on the **Country** column header, which makes selecting mirrors from a specific country accessible.
![Screenshot_2023-10-03_22-03-59](/uploads/effc5216ee8eefbba651587ac9089bfc/Screenshot_2023-10-03_22-03-59.png)https://gitlab.manjaro.org/applications/calamares/-/issues/80Buildiso created efi_boot_loader=systemd-boot iso cannot install due to "no s...2023-07-20T03:41:06ZXiao WangBuildiso created efi_boot_loader=systemd-boot iso cannot install due to "no such file /tmp/calamares-root-lymud_fv/vmlinuz-6.1-x86_64" errorI built a custom iso of manjaro with clean install of official `manjaro-gnome-22.1.3-230529-linux61.iso` file after updating the system for about 2GB downloading.
I read the `Build_Manjaro_ISOs_with_buildiso` wiki, only changed one con...I built a custom iso of manjaro with clean install of official `manjaro-gnome-22.1.3-230529-linux61.iso` file after updating the system for about 2GB downloading.
I read the `Build_Manjaro_ISOs_with_buildiso` wiki, only changed one config in *profile.conf*:
```
efi_boot_loader="systemd-boot"
```
my buildiso command was
```
buildiso -f -p gnome -b stable -k linux61
```
And my iso was build sucessfully.
I used ventoy to install this ISO. Installation progress went to around 79%, the installer prompted error, and here below is the failure log:
Calamares version: 3.2.62-4
…
2023-07-20 - 02:40:08 [6]: virtual void Calamares::JobThread::run()
Starting job “grubcfg” ( 32 / 35 )
2023-07-20 - 02:40:08 [6]: virtual Calamares::JobResult Calamares::PythonJob::exec()
Job file “/usr/lib/calamares/modules/grubcfg/main.py”
2023-07-20 - 02:40:08 [6]: [PYTHON JOB]: Found gettext “en_US” in “/usr/share/locale/en_US”
2023-07-20 - 02:40:08 [6]: … Job description from pretty_name “grubcfg” = “Configure GRUB.”
2023-07-20 - 02:40:08 [6]: … Running (“sh”, “-c”, “which dracut”)
2023-07-20 - 02:40:08 [6]: … Target cmd: (“sh”, “-c”, “which dracut”) Exit code: 1 output:
which: no dracut in (/usr/sbin:/usr/bin:/sbin:/bin:/root/bin)
2023-07-20 - 02:40:08 [6]: … Running (“sh”, “-c”, “which plymouth”)
2023-07-20 - 02:40:08 [6]: virtual void Calamares::JobThread::run()
Starting job “bootloader” ( 33 / 35 )
2023-07-20 - 02:40:08 [6]: virtual Calamares::JobResult Calamares::PythonJob::exec()
Job file “/usr/lib/calamares/modules/bootloader/main.py”
2023-07-20 - 02:40:08 [6]: [PYTHON JOB]: Found gettext “en_US” in “/usr/share/locale/en_US”
2023-07-20 - 02:40:08 [6]: … Job description from pretty_name “bootloader” = “Install bootloader.”
2023-07-20 - 02:40:08 [6]: [PYTHON JOB]: “Bootloader: systemd-boot”
2023-07-20 - 02:40:08 [6]: [PYTHON JOB]: “Root partition uuid: "be1b4009-f0de-4666-8bd9-d4b22562e09d"”
2023-07-20 - 02:40:08 [6]: [PYTHON JOB]: “Configure: ", with linux61"”
2023-07-20 - 02:40:08 [6]: Python Error:
<class ‘FileNotFoundError’>
[Errno 2] No such file or directory: ‘/tmp/calamares-root-lymud_fv/vmlinuz-6.1-x86_64’
File “/usr/lib/calamares/modules/bootloader/main.py”, line 777, in run
prepare_bootloader(fw_type)
File “/usr/lib/calamares/modules/bootloader/main.py”, line 744, in prepare_bootloader
install_systemd_boot(efi_directory)
File “/usr/lib/calamares/modules/bootloader/main.py”, line 487, in install_systemd_boot
create_systemd_boot_conf(install_path,
File “/usr/lib/calamares/modules/bootloader/main.py”, line 231, in create_systemd_boot_conf
shutil.copyfile(kernel_path, os.path.join(files_dir, kernel_name))
File “/usr/lib/python3.11/shutil.py”, line 256, in copyfile
with open(src, ‘rb’) as fsrc:
^^^^^^^^^^^^^^^
I tried twice, always failed due to mentioned error.https://gitlab.manjaro.org/applications/calamares/-/issues/74Logo is blue on XFCE2023-03-03T12:32:54ZVitor LopesLogo is blue on XFCE![Screenshot_from_2023-03-03_12-31-59](/uploads/4ce3b8984fb41e712368993db9017389/Screenshot_from_2023-03-03_12-31-59.png)![Screenshot_from_2023-03-03_12-31-59](/uploads/4ce3b8984fb41e712368993db9017389/Screenshot_from_2023-03-03_12-31-59.png)https://gitlab.manjaro.org/applications/calamares/-/issues/73Logo not displaying correctely on plasma depending of the screensize2023-03-03T13:29:43ZVitor LopesLogo not displaying correctely on plasma depending of the screensize![Screenshot_from_2023-03-03_11-31-37](/uploads/688f71a40701bcdb87ebe72cad482b48/Screenshot_from_2023-03-03_11-31-37.png)![Screenshot_from_2023-03-03_11-31-37](/uploads/688f71a40701bcdb87ebe72cad482b48/Screenshot_from_2023-03-03_11-31-37.png)https://gitlab.manjaro.org/applications/calamares/-/issues/70Enable the swap partition during installation. (and Exclude calamares install...2023-02-13T19:45:03ZphoepsilonixEnable the swap partition during installation. (and Exclude calamares installer from oom killer.)https://github.com/calamares/calamares/pull/2097
During installation, if a swap partition exists, enable swap.
If there is no swap at all when the partition of the installation destination device is mounted, if a Swap partition exists,...https://github.com/calamares/calamares/pull/2097
During installation, if a swap partition exists, enable swap.
If there is no swap at all when the partition of the installation destination device is mounted, if a Swap partition exists, enable swap.
target_env_call cannot be used because it is before the files are copied to the installation destination. host_env_process_output cannot be used because the return value cannot be obtained.
To avoid reinventing the wheel as much as possible, use subprocess.check_output.
```
diff --git a/src/modules/mount/main.py b/src/modules/mount/main.py
index 32da36dd0..6207a6cfe 100644
--- a/src/modules/mount/main.py
+++ b/src/modules/mount/main.py
@@ -307,6 +307,12 @@ def mount_partition(root_mount_point, partition, partitions, mount_options, moun
mount_option) != 0:
libcalamares.utils.warning("Cannot mount {}".format(device))
+def enable_swap_partitions(swap_partitions):
+ try:
+ for swap_device in swap_partitions:
+ libcalamares.utils.host_env_process_output(["swapon", swap_device])
+ except subprocess.CalledProcessError:
+ libcalamares.utils.warning("Failed to swapon " + swap_device)
def run():
"""
@@ -321,6 +327,10 @@ def run():
return (_("Configuration Error"),
_("No partitions are defined for <pre>{!s}</pre> to use.").format("mount"))
+ # swap
+ swap_partitions = [p['device'] for p in partitions if p['fs'] == 'linuxswap']
+ enable_swap_partitions(swap_partitions)
+
root_mount_point = tempfile.mkdtemp(prefix="calamares-root-")
# Get the mountOptions, if this is None, that is OK and will be handled later
```
```
diff --git a/data/calamares_polkit b/data/calamares_polkit
index 363dcf7..cb8d2f6 100644
--- a/data/calamares_polkit
+++ b/data/calamares_polkit
@@ -1,4 +1,11 @@
#!/bin/bash
+
+#swap
+[[ $(swapon --show) == "" ]] && SWAP=$(lsblk -l -f -n -p | awk '{if ($2=="swap") print $1}') && ( sudo swapon $SWAP || (sudo mkswap $SWAP && sudo swapon $SWAP) )
+
+NO_OOM_KILLER="`pidof -xw Xwayland udisksd` $$"
+echo $NO_OOM_KILLER | xargs -n1 sudo choom -n -1000 -p
+
if [ $(which pkexec) ]; then
pkexec --disable-internal-agent "/usr/bin/calamares" "-D6" "$@"
else
```https://gitlab.manjaro.org/applications/calamares/-/issues/65QML sidebar has scalling issues on small screens2022-10-04T16:15:07ZVitor LopesQML sidebar has scalling issues on small screenshttps://gitlab.manjaro.org/applications/calamares/-/issues/64QML sidebar has scalling issues on Hdpi resolutions.2022-10-04T16:14:25ZVitor LopesQML sidebar has scalling issues on Hdpi resolutions.https://gitlab.manjaro.org/applications/calamares/-/issues/63openswap.conf - misspelled option2022-07-19T17:04:11ZGhost Useropenswap.conf - misspelled optionTo reproduce - run a bare-metal installation using btrfs with swap, hibernate and encryption.
While troubleshooting the openswap.conf - found this https://github.com/calamares/calamares/issues/1659#issuecomment-920155121
I took the def...To reproduce - run a bare-metal installation using btrfs with swap, hibernate and encryption.
While troubleshooting the openswap.conf - found this https://github.com/calamares/calamares/issues/1659#issuecomment-920155121
I took the default openswap.conf and modified it - only to discover afterwards - a new test install - the config is almost correct when written by the installer only the __keyfile_device_mount_options__ configuration is written as
```
keyfile_device_mount_options=keyfile_device_mount_options=--options=subvol=@
```
Which will create an error message as the expected line would be
```
keyfile_device_mount_options="--options=subvol=@"
```
Reference: https://forum.manjaro.org/t/calamares-writing-openswap-conf-with-btrfs/117031
@philmhttps://gitlab.manjaro.org/applications/calamares/-/issues/60oem iso calamares end user setup failed2022-04-01T14:03:27Zguy duportailoem iso calamares end user setup failedCreated oem iso with latest profiles
After installation of computer, End user setup failes with error, but after reboot all is ok.
Happens with xfce and gnome also![IMG_2373](/uploads/cfa7a57ad02398bc51cf0bb18a4a2c82/IMG_2373.JPG)
See l...Created oem iso with latest profiles
After installation of computer, End user setup failes with error, but after reboot all is ok.
Happens with xfce and gnome also![IMG_2373](/uploads/cfa7a57ad02398bc51cf0bb18a4a2c82/IMG_2373.JPG)
See log here:
https://www.manjarocomputer.eu/cal.txthttps://gitlab.manjaro.org/applications/calamares/-/issues/58Encrypted Installation fails when not encrypting /boot2022-02-17T00:40:59Zwnhre2ur8cxx8Encrypted Installation fails when not encrypting /bootHi,
for reference, we discussed this already in an upstream issue here:
https://github.com/calamares/calamares/issues/1311#issuecomment-1042010353
In short: calamares supports not encrypting /boot while still encrypting the rest of th...Hi,
for reference, we discussed this already in an upstream issue here:
https://github.com/calamares/calamares/issues/1311#issuecomment-1042010353
In short: calamares supports not encrypting /boot while still encrypting the rest of the system. The latest Manjaro Gnome ISO fails to do that and always crashes in the mkinitcpio step with something like this (older warning, ignore old kernel):
```
Installation Failed
External command finished with exit code 1.
Output:
==> Building image from preset: /etc/mkinitcpio.d/linux513.preset:'default'
-> -k /boot/vmlinuz-5.13-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.13-x86_64.img
==> Starting build: 5.13.19-2 MANJARO
-> Running build hook: [base]
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.13-x86_64-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
```
There also is a forum thread for somebody who tried this with Gnome and failed aswell, but successfully did this with the KDE ISO:
https://forum.manjaro.org/t/install-without-boot-encryption-working-with-kde-version-but-not-with-gnome-version/102089https://gitlab.manjaro.org/applications/calamares/-/issues/54Disk encryption + BTRFS + Suspend to disk swap generates wrong configuration2021-10-15T23:56:28ZJohannes HörmannDisk encryption + BTRFS + Suspend to disk swap generates wrong configurationHi,
I noticed that when enabling these options, there are two errors in the configuration:
1. `/etc/crypttab` contains the root fs and the swap. This is not needed. (it is even noted in the comments above the entries that those should n...Hi,
I noticed that when enabling these options, there are two errors in the configuration:
1. `/etc/crypttab` contains the root fs and the swap. This is not needed. (it is even noted in the comments above the entries that those should not be added to the crypttab.
2. `/etc/openswap.conf` does not have the btrfs mount options enabled, which breaks the resume to disk swap as it doesn't mount the root fs with the keyfile correctly. (e.g. `keyfile_device_mount_options="--options=subvol=@"`)
I tested it with the latest manjaro installation image. Not sure if it's already fixed in the latest dev version. If so, this can be closed.https://gitlab.manjaro.org/applications/calamares/-/issues/52Specifying the mount option when partitioning a disk2021-08-20T14:27:35Zsaber716rusSpecifying the mount option when partitioning a diskI have submitted a suggestion to github calamaris. The essence of the proposal during the markup is to enable the user to edit the mount option.
https://github.com/calamares/calamares/issues/1753I have submitted a suggestion to github calamaris. The essence of the proposal during the markup is to enable the user to edit the mount option.
https://github.com/calamares/calamares/issues/1753https://gitlab.manjaro.org/applications/calamares/-/issues/50Editfield cursor bug during user setup2021-01-23T07:20:08ZsoshialEditfield cursor bug during user setupSteps to reproduce:
1) Launch install on Manjaro KDE LiveCD
2) Get to the user setup step
3) Enter full name and user name
4) Put your cursor in the middle of username or computer name
5) Try to edit it
Results:
The cursor jumps to the ...Steps to reproduce:
1) Launch install on Manjaro KDE LiveCD
2) Get to the user setup step
3) Enter full name and user name
4) Put your cursor in the middle of username or computer name
5) Try to edit it
Results:
The cursor jumps to the end of the edit field
![PXL_20210121_052506645](/uploads/c261ea52beb51210e1f9f711d5cea8be/PXL_20210121_052506645.jpg)https://gitlab.manjaro.org/applications/calamares/-/issues/49No systemd-boot option2020-09-14T23:06:06ZmirhNo systemd-boot optionI seem to understand upstream calamares should already be offering it.I seem to understand upstream calamares should already be offering it.https://gitlab.manjaro.org/applications/calamares/-/issues/48Typo in office suite image2020-09-03T08:24:21ZMatthias BraunTypo in office suite imageHi and thanks a lot for Manjaro!
I noticed there's a typo in the image where the user gets to choose their office suite. It says
>You can always install multiple Office suite applications on you system.
![manjaro installer screenshot]...Hi and thanks a lot for Manjaro!
I noticed there's a typo in the image where the user gets to choose their office suite. It says
>You can always install multiple Office suite applications on you system.
![manjaro installer screenshot](https://i.imgur.com/OoIIsuF.png)
"you system" should be "your system".https://gitlab.manjaro.org/applications/calamares/-/issues/46No default shortcut for changing KB layout2020-07-04T15:15:50ZJedi-Mind-TricksNo default shortcut for changing KB layout**Steps to reproduce:**
1) Start to install Manjaro
2) Add additional keyboard layout (RU for example)
3) Set user password in English
4) After reboot try to login
**Result**
- Can't enter password since current layout is not US
- Can't...**Steps to reproduce:**
1) Start to install Manjaro
2) Add additional keyboard layout (RU for example)
3) Set user password in English
4) After reboot try to login
**Result**
- Can't enter password since current layout is not US
- Can't change layout, no default key for that
**Expected result**
- Can change layout
- Probably by default shortcut such as [Shift] + [Alt]
**Additional info**
- Really nasty bug, there's even manuals out there on how to get around this bug.
- I'm suggesting to have a default shortcut but maybe there's other smart solution?https://gitlab.manjaro.org/applications/calamares/-/issues/42Help strings in user ui page are too long for the labels2019-07-27T08:11:37ZGhost UserHelp strings in user ui page are too long for the labelsThe file [page_usersetup.ui](https://gitlab.manjaro.org/applications/calamares/blob/development/src/modules/users/page_usersetup.ui) contains strings which does not fit inside a fixed size label as described in [this forum comment](https...The file [page_usersetup.ui](https://gitlab.manjaro.org/applications/calamares/blob/development/src/modules/users/page_usersetup.ui) contains strings which does not fit inside a fixed size label as described in [this forum comment](https://forum.manjaro.org/t/iso-openbox-19-07-11-unstable/94461/21?u=linux-aarhus)
Maybe the labels could be extended to fit horizontally to the window size or the help texts could be shortened to fit the label size.
@philm
A corresponding issue has been opened on https://github.com/calamares/calamares/issues/1202https://gitlab.manjaro.org/applications/calamares/-/issues/41Installing manjaro with CZECH keyboards set vconsole.conf to wrong value2019-03-27T11:33:21ZAntonín DachInstalling manjaro with CZECH keyboards set vconsole.conf to wrong valueHi,
I am not sure if where this issue is. But when installing Manjaro with regular czech keyboard layout the mpa value for tty virtual console is set to
```
KEYMAP=cz-lat2
```
This is a idiocy of the layout makers but that keyboard i...Hi,
I am not sure if where this issue is. But when installing Manjaro with regular czech keyboard layout the mpa value for tty virtual console is set to
```
KEYMAP=cz-lat2
```
This is a idiocy of the layout makers but that keyboard is nearly the same as us-english and has nothing to do with Czech language, it should not even exist IMHO.
All czech who uses ttys are complaining and has to change this back to this value which is
```
KEYMAP-cz
```
There is also options for qewrtz
```
KEYMAP=cz-qwertz
```
Would there be a possibility to change the installation process? Or if it's not Calamares related, then to whom should this be reported.
Some distributions does this correctly so there must be an option.