202607191707 is not calling manjaro-live at all. Those are with the locale settings and other things. The newer ones already have the user created on build-time but still call part of things manjaro-live originally did.
manjaro-xfce-26.1-testing-260721-linux71.iso.
Intel IGP machine + Ventoy
Unable not contact settings server â Ctrl+Alt+Backspace â the password prompt window appears â I enter the password and wait 2-3 minutes â enter â the live session starts!
Booting manjaro-kde-26.1-testing-minimal-260721-linux618.iso reaches desktop logged in as manjaro on my laptop HP Elitebook 820 G1 and on my desktop PC with AMD Ryzen 5 3600 CPU and Radeon RX 590 graphics.
The keyboard is not my chosen DK, but instead the default US. However, keyboard setting is a problem separate from the desktop login.
As for the keymap settings - it seems that Gnome and Plasma Desktop may require the use of localectl set-keymap to pickup the keymap whereas xfce terminal pickup the keymap set by the kernel cmdline.
The desktop itself - tested using xfce - does not pickup the chosen locale from the kernel cmdline.
I have an idea of why the locale settings sometimes fails
When the ISO is booted using Ventoy Grub2 mode - then the locale variables are doubled, instead of replaced.
Normal boot using Ventoy will result in the correct locale parameters.
Xfce test
The xfce desktop defaults to en_US (da_DK was chosen), the keymap (dk) is correct, and Manjaro Hello uses the chosen locale (da_DK).
The first may be attributed to the locale-gen for da_DK has not been run by the live setup.
I think there was a time where we had all locales compiled - but then some was complaining about bloat - possibly the reason they are not there - this could be a task for manjaro-live - rebuilding the chosen locale.
Manjaro Settings Manager shows the locale, timezone and keymap correct.
I made a boot medium without Ventoy by using GRUB and EFI. The boot parameters for keyboard and tz are not doubled here, but the resulting keyboard on the desktop is still US.
Well, /run is itself a tmpfs, but several directories under /run are themselves separate tmpfs mounts, including /run/user/1000, which must be created when the 1000 user account itself is created.
[nx-74205:/dev/pts/3][/home/aragorn]
[aragorn] > mount | grep run
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=3247152k,nr_inodes=819200,mode=755,inode64)
none on /run/credentials/systemd-journald.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1623572k,nr_inodes=405893,mode=700,uid=1000,gid=1000,inode64)
[nx-74205:/dev/pts/3][/home/aragorn]
[aragorn] >