If you like following latest Plasma development you may also like to check out our current version of manjaro-kde-dev, which we build on a regular basis against kde-git master packages. Also check out our latest Manjaro Ornara 21.0 preview release! KDE, XFCE and Gnome
Our current supported kernels
linux44 4.4.249
linux49 4.9.249
linux414 4.14.213
linux419 4.19.164
linux54 5.4.86
linux59 5.9.16 [EOL]
linux510 5.10.4
linux54-rt 5.4.84_rt47
linux59-rt 5.9.1_rt19
Packages Changes (Thu Dec 31 11:49:13 CET 2020)
testing community x86_64: 1510 new and 1485 removed package(s)
testing core x86_64: 27 new and 24 removed package(s)
testing extra x86_64: 436 new and 519 removed package(s)
testing multilib x86_64: 15 new and 9 removed package(s)
A detailed list of all package changes can be found here.
No issue, everything went smoothly
Yes there was an issue. I was able to resolve it myself.(Please post your solution)
Yes i am currently experiencing an issue due to the update. (Please post about it)
The libtraceevent package prior to version 5.9-1 was missing a soname link. This has been fixed in 5.9-1, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors
libtraceevent: /usr/lib/libtraceevent.so.1 exists in filesystem
PAM and PAMBASE got updated, which might prevent you from login
Due to updates from pambase and pam you might take care about any .pacnew files in /etc/pam.d as for example pam_tally, pam_tally2 and pam_cracklib got deprecated. Read in the ArchWiki about managing those files.
Typical issue:
For recovery, it is enough to boot with kernel option “systemd.unit=rescue.target”, then proceed into /etc/pam.d and merge “system-auth” and “system-auth.pacnew”
System takes a long time to boot
If you’ve got errors like Failed to start Network Manager Wait Online. you can try removing systemd from passwd and group in /etc/nsswitch.conf as described here Update: If you can see the line dbus-daemon[1453]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 45146ms)
in in your dbus log ( journalctl -b -u dbus ), the new/better workaround is to switch cups from service to socket as described here: systemctl disable cups.service systemctl enable cups.socket
I think I’ve some font problems
With the update of fontconfig some major rules how fonts get applied changed. Make sure that your system has ttf-dejavu installed. A more in depth explanation can be found here.
Gnome-shell-extension-pop-shell is currently incompatible with wayland
… and causes the system to freeze when the first window is tiled and can render it unbootable. Solution is a hard reset and disabling either pop shell or wayland. If the system becomes unbootable, use a live USB to edit /etc/gdm/custom.conf to disable wayland and reboot.
Hi, I upgraded to the latest packages.
The xfce Status Tray plugin exits with a core dump (thus, currently no status icons are visible):
Process 5720 (panel-6-systray) of user 1000 dumped core.
Currently optimus-manager does not work for me. Just came from stable (after reinstalling KDE). Switching worked fine on stable, but now it doesn’t (switching worked fine yesterday).
The error I get is
The nvidia module does not seem to be available for for the kurrent kernel. It is likely the Nvidia driver was not properly installed. GPU switching will probably fail. Continue anyway?
I have changed optimus-manager from repo to optimus-manager-git from AUR, but no luck in having it switch for the time being.
I am currently on kernel 5.10, will check kernel 5.9
Update
Switching using optimus-manager works like a charm on kernel 5.9 for me, not 5.10 (which is sad because 5.9 is close to EOL).
rsync. I’ve just uninstalled timeshift and reinstalled ,it gave me a message about upgrading another package on the reinstall. I’ve just done a manual backup and that’s now showing in timeshift so fingers crossed its just a package that didn’t get updated
Looks like a nvidia driver incompatibility/bug with the kernel to me rather than an optimus-manager thing. Both seem rather not-ready for prime yet, for example 5.10.4 is still on Arch testing repo. Others have problems with Nvidia’s Prime as well, like