Help Testing 24.0 Release Candidates

Manjaro Development QA
1

The @Manjaro-Team is currently testing 24.0 Release Candidates and working hard on getting a new stable snap of packages out. Why not join to help?

Current Test-ISOs

Changes

  • firmware updates
  • Gnome 46.1
  • GlibC updates for Nvidia and Steam
  • Gstreamer is now at 1.24.3
  • Kvantum-Qt5 and breeze5 got added to fix Qt5 theme issues
  • libpamac uses now libalpm and therefore the configured download manager like curl for AUR database downloads
  • plymouth got downgraded to 22.02.122-18
  • python 3.12 updates
  • Kernel is now at 6.8.9 including ntfs-3g support fixes
  • MHWD-DB updates including profile updates for Nvidia and FOSS drivers
  • plasma-workspace defaults now to X11 session
  • SDDM got a last state config added to default to X11 session

Detailed package changes per edition can be found here: gnome.diff, kde.diff, xfce.diff

5 Likes
2

KDE ISO:
the same issue of a black screen while booting up as described in Unable to load latest stable and unstable ISOs (KDE/Plasma)
If to remove splash and quiet, booting up become successful.

Moderator edit: Corrected link to main topic instead of specific reply

3

here booting fine

will be possible to install it and after right the installation switching to testing?

4

that is a plymouth issue. We will ship with the older one which is not so picky about KMS.

1 Like
5

Why is it an issue with the latest ISOs though. Shouldn’t these have the “kms” hook already in the mkinitcpio config?

6

They have but it is still an issue. Only way to fix it is a git-bisect on plymouth with affected system and report it to upstream.

7

@alven Your hardware combination seems to be unique as for me with AMD graphics having the “kms” hook in /etc/mkinitcpio.conf fixed black screen.

  1. Can you make extra-sure that this is the case for you too, i.e. that on the ISO you downloaded it says kms in the HOOKS array.
  2. Would you be able to a) manipulate the ISO by changing the included plymouth or b) install to the affected hardware and then change the installed plymouth?
8

i was on the testing branch, until for some unknown reason i couldn’t start manjaro. I would like to know where I can download an iso for testing. I’ve been looking for it and can’t find it.Thanks

9

I dont fully agree with this guide (no need to use zip) but its here and has links:

10

Any plans for implementing systemd-boot in calamares in future releases ?

11

For the time being - this is a DIY as no such plans exist - but if you really want to - the change is uncomplicated.

There is a script to facilitate this.

12

Thanks linux-aarhus, i know it’s not that difficult just the question out of curiosity. EOS is doing a nice job on the subject. Tested 24.0 iso with xfce … for me it’s working flawless

13

There are new ISO uploaded for testing: Testing 24.0 ISOs (#9) · Issues · Release plan / Releases · GitLab

1 Like
14

xfce :+1:

15

No problem installing xfce then kde in VM

16

Today the ISOs got updated one more time, containing new kernels. If you have time for it, please test these ISOs, as they are expectedly the last update before our snap to stable.

You can test the ISOs through VirtualBox or QEMU/virt-manager.

17

may I ask why, in kde-minimal, I don’t see partitionmanager and other applications generally seen in the official release?

18

Because calamares 3.3 has problems after conversion to qt6.

Calamares 3.2 depends on kpmcore5 - this creates a file conflict with partition manager depending on kpmcore with qt6.

To avoid that conflict partition manager has been omitted from the installation.

You will then - after installation - need to install partition manager separately after installation - should you need it.

1 Like
19

No problem with xfce on a VM with this new version

20

gnome (full) installs without issues on bios and uefi using QEMU/KVM

I noticed that the default installation is X11 and switching to wayland using the layout manager in settings works without issues.