One of the team members have explained this here.
1 Like
Change the dynamic wallpaper to static one. That is all. We discovered that the dynamic wallpaper had absurd resource usage and dropped it.
8 Likes
I am so excited! I am a like a kid at christmas opening presents. lol So I just installed a fresh gnome and the WOW factor is definately there. It is so snappy compared to PoPOS. No problems to report so far. 
Hats off to all involved and thank you!
1 Like
Wasn’t able to boot the install media with 6800XT, tty screen came up ok but the KDE desktop failed. (black)
Is there no magic trick I can try in the boot line to resolve this.
The solution is to install Architect and then chroot linux-mainline before restarting. There are other steps but that’s basically it.
Did you also tried the ISO with linux54 kernel?
@philm, when will you allow installing with the ESP on /efi ?
I currently mount my ESP on /efi and do a bind-mount of a subdir of the ESP as /boot.
This setup will work for all boot-loaders…
Using /efi is by the way the recommended place to mount the ESP see The Boot Loader Specification
That is simply not true,
Both /boot and /efi are fine as long /boot is not on a separate file system, that is not recommended. Since this is not the case with Manjaro it does not matter a bit.
1 Like
You are wrong…see this quote:
This placeholder file system shall be determined during installation time , and an fstab entry may be created. It should be mounted to either
/boot/or/efi/. Additional locations like/boot/efi/, with/boot/being a separate file system, might be supported by implementations. This is not recommended because the mounting of$BOOTis then dependent on and requires the mounting of the intermediate file system.
Note the parts i made bold especially the underlined parts…
Because most distributions, manjaro inclusive, mount the ESP at /boot/efi they all fall into this category of “not recommended”…
So by mounting the ESP at /efi in combination with a bind-mount of a subdir of the ESP at /boot makes it the recommended way while still allowing to install the kernel and ramdisks in /boot with the current tools…
1 Like
Very nice release ! I also love the boot splash, but sometimes it shows up and some times it don’t. Still didn’t understand why.
Indeed as it says. With boot being a separate file system… that part is also important and that is not the case with Manjaro by default as it is also not with (most) other distro’s.
Also you simply claim only mounting on /efi is recommended and according to your own quote that is simply not the case.
Rolling your eyes does not change that fact, sorry
Note I do not question you legit question, but only the claim you add to it.
Installed it today but the KDE Plasma version is very very laggy, any idea what might cause it?
1 Like
Plasma version has issues reported in many threads… Seems to be a KDE problem not a Manjaro one. Waiting for a permanent fix…
Probably at the same time with supporting esp on /boot. I thought calamares could already do that, but to my surprise discovered that this is not the case. It’s now on my to do list:
- better btrfs subvolume structure
- support systemd timers in iso-profile
- support alternative mount points for the esp partition
5 Likes
Thanks the Manjaro Team for the release of Manjaro 20.2 Nibia final version. 
I will install Manjaro Gnome on an hardware with 2Gb of ram (hybrid PC/tablet). Is there a way to uninstall evolution-data-server without removing the gnome calendar ? As I will install that version on an Emmc disk, I will not create a swap partition (to avoid to reduce the life of this “disk”). Chrysostomus talked about a swapfile. Is there a risk to use a swapfile on an Emmc disk ? if not, how to make this swapfile ? Is Trim can be used on an Emmc disk ?
Thanks.
1 Like
No, as you probably noticed gnome-calendar depends on evolution-data-server.
Congratulations all - I’m running Gnome with the Pop-shell and it’s buttery smooth on not-so-new hardware. A big positive release.
1 Like