Being as there are a few reports of this issue on Manjaro KDE installation maybe the bug ought to be raised here in the Manjaro Calamares repo.

If anyone is triaging please could you decided if this is a manjaro specific issue. If not then the manjaro team might want to chase in core.

The issue is here calamares 1208 . On an install which creates a LUKS /swap partition for encrypted hibernation the root LUKS UUID is written to the grub.cfg as the resume UUID instead of the swap partition UUID.

I notice that there is also grub.cfg writing source code in this manjaro repo, last commit 3 years ago whereas the core calamares grub.cfg source last commit was only a few days ago, does this version need to pull from upstream or merge in changes for swap UUID? It does look like there are quite a few changes in the code to deal with it in core.

Hello,

I recently installed Manajaro 16.08 KDE and accidentally chose a mounting point for a partition. This mounting point can only be changed to a different one but cannot be removed anymore - unless you start over with the installation.

This should be fixed IMHO.

Kind Regards
Alex

keep track on stuff to do after moving config to livecd for iso

I have made yesterday a test uefi install on real hardware.
The install finishes, but the fstab on the installed system has wrong order of entries.

The /boot/efi entry gets written before the /boot entry and thus efi boot fails.

Manjaro can currently not be installed on a Mac with UEFI with Calamares. The installer does not offer VFAT, the installation fails with this error message if another filesystem is used for the boot partition:

Boost.Python-Fehler in Job "bootloader".
<class 'subprocess.CalledProcessError'>
Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --force' returned non-zero exit status 1
Traceback:
  File "/usr/lib/calamares/modules/bootloader/main.py", line 289, in run
    prepare_bootloader(fw_type)

  File "/usr/lib/calamares/modules/bootloader/main.py", line 277, in prepare_bootloader
    install_grub(efi_directory, fw_type)

  File "/usr/lib/calamares/modules/bootloader/main.py", line 220, in install_grub
    "--force"])

  File "<string>", line 2, in <module>

The whole problem is described in this thread, however still not improved in Manjaro 17.0.2.
https://forum.manjaro.org/t/first-install-help-me-to-get-going-please/21810/14

The workaround is:

1. Create and format the boot partition manually before the installation
2. Mount the partition manually at the right moment while Calamares is doing the installation.
3. Boot again with from USB
4. Mount /-partition
5. Modify fstab entry for boot-partition from xxx to vfat

After Manjaro installation using Calamares with this partition schema:
/boot (unencrypted)
/boot/efi (unencrypted)
/ (encrypted)

There is duplicated entry for GRUB_ENABLE_CRYPTODISK in /etc/default/grub. Lines 16 & 50 in my case. First one is commented but second one isn't.

I see two problems here:

1. Duplicated GRUB_ENABLE_CRYPTODISK - if config file hasn't been changed by user you could except there will be only one entry for every option
2. Calamares do not respect user settings when /boot & /boot/efi are unencrypted.

Tested on manjaro-kde-20.0.1-200511-linux56.iso but I've checked /etc/default/grub on system installed more then year ago ( with encrypted both boot partitions ) and there GRUB_ENABLE_CRYPTODISK is also duplicated.

I've been trying to install Manjaro using the Calamares installer and it constantly fails to recognize any partitions on one drive (/dev/sda), whether or not it has an empty 400gb ext4 partition, or just 400gb of unpartitioned space.

Calamares view: http://i.imgur.com/IQ8kBid.png
Output of lsblk: http://i.imgur.com/QuGmIPJ.png
Output of blkid: http://i.imgur.com/elwOzKb.png
Output from sudo calamares -d: http://pastebin.com/hBitV4GJ

From the output, 3 lines stand out:
13:16:54 [1]: checking if "/dev/sda5" can be resized.
13:16:54 [1]: "/dev/sda5" seems like a good path
13:16:54 [1]: Partition "/dev/sda5" CANNOT BE RESIZED FOR AUTOINSTALL.

Using GParted, I am able to resize sda5, so I am not sure what to do in this case.

Also, the output repeatedly shows:
13:16:57 [1]: WARNING: system is EFI but there's no EFI system partition, DISABLING alongside and replace features.
The EFI partition is /dev/sda2

Is this an issue with my drive configurations? (Windows 10 is installed on sdb and "half" of sda)
Side note: I was able to use the CLI installer in the Net version of Manjaro, and that allowed me to access and install on a partition in the sda drive.

As described, if you try to install Manjaro Deepin on 4k screen, Calamares installer on live will be 1:1 (very small) even though system scaling is x2.

Tested on manjaro-deepin-18.0.2-stable-x86_64.iso

No luks encryption

in german and english gui of calamares the checkbox for activating luks encryption is missing.
See here
I used this image:
download 2016-05-24, verified by sha1sum and gpg

after installation from this image i can choose manjaro and opensuse 13.2 in grub. I have never installed opensuse.

I adopted your profile and pkgbuild for calamares 2.0.
We use a calamares.png file that is getting put under icons but so is a small non existent calamares.svg.

https://calamares.io/bugs/browse/CAL-390

Continuing here...

pykwalify -d settings.yaml -s settings-schema.yaml
INFO - validation.valid

Schema exists:

• settings.conf
• bootloader.conf
• grubcfg.conf
• luksopenswaphookcfg.conf
• packages.conf
• servicescfg.conf
• welcome.conf
• chrootcfg.conf
• initcpio.conf
• machineid.conf
• partition.conf
• services.conf
• displaymanager.conf
• keyboard.conf
• mhwdcfg.conf
• plymouthcfg.conf
• umount.conf
• finished.conf
• license.conf
• mount.conf
• postcfg.conf
• unpackfs.conf
• fstab.conf
• locale.conf
• netinstall.conf
• removeuser.conf
• users.conf

https://github.com/manjaro/manjaro-tools/blob/master/data/schemas

@teo

If you have use for the schemas let me know.

ToDo:

• fix pykwalify package, something is wrong with python-yaml and python-dateutil version dep
• conf files despite yaml are not accepted by pykwalify, they must have yaml extension

Hello,

I installed Manjaro 16.08 Ellada with Calamares and chose:

• Install beside existing system
• Do not install a bootloader

Nonetheless the summery of the installation contained "Install bootloader"

I then went the two steps back and chose "manual configuration of the partitions" and "no bootloader" and then finally in the summary the point "Install bootloader" was gone.

Kind Regards

https://github.com/manjaro/calamares

Do we want branch per module?

or manjaro branch?

I used Calamares to install Manjaro on a 16.06-rc1 raid 0 array which I created with mdadm, but when I booted the system the array partition could not be found, so I had to add mdadm_udev to the HOOKS array in mkinitcpio.conf and regenerate the initramfs image.

Would it be posible to make it so if any raid paritions are selected, mdadm_udev is added to the HOOKS array in /etc/mkinitcpio.conf, so they are mounted by fstab at boot?

I created an issue for Thus too https://github.com/manjaro/thus/issues/54

Gents,
is there a way to force manj-Calamares to use arch-chroot instead of chroot?

thanks a lot.

In Manjaro 21.2.5, using calamares version 3.2.52.r10510.3e130c3e3

1. The installation crashes after manual partitioning, while trying to format the partitions.

• physical volumes were created (with pvcreate from the command-line)
• one logical group was created (with lgcreate)
• logical volumes were created (with lvcreate)

├─MANJ-swap 254:0    0     3G  0 lvm  
├─MANJ-sys  254:1    0    22G  0 lvm  
└─MANJ-home 254:2    0    18G  0 lvm  
sdb           8:16   0    15G  0 disk 
└─MANJ-home 254:2    0    18G  0 lvm

After selecting

• sys, asking to format it as ext4 and / mount point
• home, asking ext4 and /home mount point
• swap, asking linux-swap (no mount point)

and after validating the choices, calamares crashed.

Moreover, MANJ/sys had been removed from the group and completely deleted.

This makes it impossible to install Manjaro in a LVM system.

2. It is apparently possible to manage volume, but not to create physical volumes or volume groups

This can however be done manually from the command line, so this could only be a suggestion to add it.

I have tried on several sessions using multiple hard drives, all the the same result. After the last install entry, just before install, calamares disappears. There is no log files nothing. Here's the screenshots one at a time:

Summary is the last thing that appears. Once I push Next the installer disappears.

Hello,

it seems Calamares cannot detect my Samsung 950 PRO (/dev/nvmen0).

We need something similar for:

    # Configure root user
    cp /etc/skel/.{bash_profile,bashrc,bash_logout,extend.bashrc} /root/
    if [[ -d /etc/skel/.config ]];then
        cp -a /etc/skel/.config /root/
    fi

Using Calamares-manjaro auto-installer configurator menu should allow only options which work in practice
For example, if I select
/ with btrfs and LUKS encryption
hibernation file with LUKS encryption
it does not work proberly.
When you boot the new installed PC it always says hibernation file cannot be opened. There is no solution so far in the forums even after deep research.

Also
/ with btrfs and LUKS encryption
swap file btrfs with LUKS encryption
it does not work properly.

On the other hand also in the standard auto configuration menu a separation of /home and / directory should be selectable including which of each partition wants to be encrypted or not.
Using a seperated hard with LUKS and btfs should be integrated in the installation process as well.
From my expierence having (only) a / partition with hibernation file all in btrfs and LUKS encrypted plus a seperated hard disk for data always shows an error on booting "hibernation cannot be opened" and requires not only entering the password for the root partition but every time also additionally needs the LUKS password for the (second data) hard disk.

See mailing list.
I think we should do a split build, cal-base, cal-modules, cal-branding.
We can use the chance to give sonar a working branding.

Hi, I'm trying Manjaro in VM, I'm looking for a cute modules where you can edit the mount options at the time of installer assembly: Format > Mount Subvolume > Squashfs Image Extraction
In this step I would like to force the ZSTD level 15 compression at the time of installation.
I can set up and modify the sublumal, the mount options on fstab (post installation)
Is there a way to do it with Calamares on Manjaro?
In this way I would save a lot of space at the time of installation.
Thanks in advance to anyone dedicating time to answer me

Before we replace hardwarecfg we have to review the new code of mhwdcfg and think on how we handle following things:

• Remove virtualbox driver on real hardware, as some editions ship it preinstalled. There is no option for it yet
• Check if we still need configuration of ALSA. If so, we should move it to postcfg
• Check if we still need configuration of PULSE. If so, we should move it to postcfg

It would be nice if installer would check if passphrase contains any characters (non-English characters?) that will make unlocking encrypted drive by grub impossible.

Tested on: manjaro-kde-20.0.1-200511-linux56.iso

Hi, it's a small feature request

I am using calamares-dev to install community i3 version of manjaro.

I don't want to have swap on SSD drive and I had to do manual partitioning.

The process works fine, but when selecting flags I expected to see them on reentry the partition options when clicking EDIT from a menu, they all unselect and it gave me impression of something have gone wrong.

It is competitive bootmenu option and should be easy to implement, as the option would just need to run refind-install inside the chroot.

Is there any reason why not to allow hostnames to start with a number? It is legal and accepted: http://tools.ietf.org/html/rfc1123#page-13