I had the same. I suspect that pamac claims that in this location should be only a symlink to a file located elsewhere. Instead, there is already the library file at that location. However, I’m also unsure if this is something wrong in this case. When I check usr/lib there are symlink pairs, meaning: there is a library file and its symlink, all in the same location.
I guess, we can create symlinks for those, and it won’t hurt anything. However, I don’t know how to do that. The usual command:
ln -s file file
is returning that the file already exists. So how one creates the symlink to a file in the same location as it is done with many libs?
Removing the executable permissions for that file (e.g. sudo chmod 644 /etc/grub.d/60_memtest86+) also worked for me. This might be handy in case one decides to install Memtest86+ in the future, but I think including the file with the Memtest86+ package instead of the base Manjaro system would avoid the “unknown device” message in the first place for those who don’t have that package installed.
Arch report seems to apply to me. Can’t open Konsole via Dolphin if kinit is not installed. Dunno if Konsole itself has features requiring it.
It seems Dolphin’s search no longer crashes, though. Still happens, worked once by chance, I guess.
Edit: Also, Display Configuration once again uses proper icons for orientation with Breath2 theme. Those were “unknown file” icons for a good while. This might’ve taken place on 13th already, but only noticed it now.
Thanks for pointing that out as I must’ve forgotten to mention about it earlier. I do have Memtest86+ installed in my desktop system and Manjaro booting through UEFI, but Memtest doesn’t show up in GRUB and sudo update-grub does find it.
An EFI compatible one is available I think in the repos, never installed and used it as Memtest is the kind of tool you may need once in your computer’s life.
@acarasimon96 I think the issue with MBR Memtest is that its script can not handle NVME devices, the EFI one should. though, but seems to require manual operation after the package is installed to complete the installation in your GRUB.
//EDIT: from the look of it, its script is calling a function is_path_readable_by_grub from /usr/share/grub/grub-mkconfig_lib and I think this is what generates the error for NVME devices. That’s my guess by quickly looking at /etc/grub.d/60_memtest86+
I use a regular 2.5" SATA SSD in my desktop, but I do have a NVMe drive on my laptop. Both drives use a GPT partition scheme and boot throught UEFI. However, I used the minimal ISO image (which didn’t come with Memtest86+ preinstalled) to install Manjaro on the laptop, whereas I used the full ISO image on my desktop.
I think I remember you have 200% scaling settings enabled? That may mess things up. If I select small, icons are small and don’t get wider spaces in between. I select adjust to Panel height, it scales properly to the Panel height.
Quick tip/side note: If you have the time in your hands, I recommend you give these packages a look through the pamac interface and read their descriptions. Therefore if something goes wrong you will have a better idea of what might have caused it. Packagers very rarely screw up package dependencies, but it has happened. This is also a very good way of getting to know your very own linux box and how it works. Later on in life you will find yourself with much more control over your machine, which is the point of linux.