While a lot of people asked when we were planning to push a new release during the last months, it is finally close to happen We are aiming for this to arrive end of February.
We have settled onto a quite stressless release schedule since a while, but of course this doesnāt mean development stops or ceases in any way. Instead, the focus has been on working on improving in various other areas in the meantime. Thereās been a lot of improvements to our repository setup in the meantime, for example ā which is mostly work happening behind the scenes and might not be directly visible to everyone.
So here we are! We ask you guys to help us make the new release an excellent one, specifically by testing our ISO builds and reporting back any issues you find along the way
These are the builds we are looking to get feedback for:
I wonāt say more at the moment until the release. (wait, I havenāt said anything anyway lol)
However the OP mentioned something that will allow you to find the answer.
For suggestions/issues we find, do we want to use this thread, or will there be a separate thread for it?
In the Mokka ISO, when a window is maximized (1080p screen), it looks like the clock needs some more padding so it doesnāt spill over into the borders
Iām all in for testing the pre-release, but Iāve noticed in the past one canāt seem to have more than one copy of Garuda on their system without having to use chroot to access one of them. One will be detected by grub while the other is not. If there is away to address this Iām willing to create another thread for this issue so I can test without having to chroot from the live environment to switch which Garuda is available for use. Thanks
I am using custom.cfg, use at your own risk, no support for dual boot /snapshot errors.
You can use also refind, search about the thread from @BluishHumility.
# /boot/grub/custom.cfg
menuentry "Garuda Linux i3wm auf nvme0n1p7" {
insmod btrfs
search --no-floppy --fs-uuid --set=root 21e02e96-0ed6-4629-9a39-85ffee7a4359
configfile /@/boot/grub/grub.cfg
}
menuentry "Garuda Linux KDE auf nvme0n1p5" {
insmod btrfs
search --no-floppy --fs-uuid --set=root fc62cc44-07ab-497b-ac89-15704c290993
configfile /@/boot/grub/grub.cfg
}
menuentry "Garuda Linux Sway auf nvme0n1p6" {
insmod btrfs
search --no-floppy --fs-uuid --set=root d16c3a79-835a-4c1a-8af0-ec6ea0e3b7f9
configfile /@/boot/grub/grub.cfg
}
##menuentry "Garuda Hyprland SGS 123 GB auf nvme0n1p8" {
# insmod btrfs
# search --no-floppy --fs-uuid --set=root b147dd48-f302-484d-80b0-661e7ff40a76
# configfile /@/boot/grub/grub.cfg
# }
menuentry 'Windows auf nvme0n1p1' --class windows --class os $menuentry_id_option 'osprober-efi-94BA-ECE1' {
insmod part_gpt
insmod fat
search --no-floppy --fs-uuid --set=root 94BA-ECE1
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
Changes to /boot/grub/custom.cfg do not require re-running grub-mkconfig (sudo update-grub), since /etc/grub.d/41_custom adds the necessary source statement to the generated configuration file.
Also I noticed for the Mokka ISO, in the post-install applications selection, if you are choosing browsers, and select Firedragon (which the Mokka ISO has firedragon-catpuccin installed already), if the user selects Firedragon, it will then try to replace firedragon-catpuccin with the standard firedragon package instead of using the firedragon-catpuccin. Iām not sure if there is an easy way for the system to know if itās the Mokka desktop to choose the -catpuccin version of Firedragon. Just something I noticed.
I know everyone may not do it, but for new users, they may not realize that Firedragon is already installed when installing the ISO, and might select it from the Browsers tab because they want to try it out. In which they would get a package conflict. So would we want to add firedragon-catpuccin to the list of Browsers?
Maybe this was the problem all along!! Iāve never been successful in installing Sway edition but others work well.
Also just yesterday I started configuring Hyprland from scratch with gnome apps.
Well F that I guess! On my way to try āMokkaā!
By default, GRUB will use the same bootloader ID and overwrite the one thatās already in place. To work around that, change the GRUB_DISTRIBUTOR property for one of your installations as described in the āUpdate GRUBā section of this arcicle: https://wiki.garudalinux.org/Multiple_installations_on_one_partition#update-grub. It is not necessary to follow the rest of the guide if you want to use a separate partition for the new installation.
Yes Iām aware, not just the clock and not just Mokka.
Have not found a fix yet. We also assume people donāt spend most of the time in maxed out windows. But if itās a problem itās easy to change the preset manually by right-clicking on the systray or kickoff and Configure Panel-Colorizer.
We are aiming for this to arrive end of February.
