Usual Python and Haskell package updates and rebuilds
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 Mikah 20.1.1 release! XFCE, KDE and Gnome
Our current supported kernels
linux44 4.4.238
linux49 4.9.238
linux414 4.14.200
linux419 4.19.149
linux54 5.4.69
linux57 5.7.19 [EOL]
linux58 5.8.13
linux59 5.9-rc7
linux54-rt 5.4.66_rt38
linux56-rt 5.6.19_rt12
Packages Changes (Sat Oct 3 08:39:27 CEST 2020)
testing community x86_64: 879 new and 877 removed package(s)
testing core x86_64: 14 new and 14 removed package(s)
testing extra x86_64: 222 new and 220 removed package(s)
testing multilib x86_64: 2 new and 2 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)
This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed
Older Issues
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 org.cups.cupsd.service systemctl enable org.cups.cupsd.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.
Unfortunatly, this update broke CUDA. The cuda package was updated to v11.1.0-2 but the drivers were kept back in 450.66 which are incompatible with CUDA 11.1 according to Nvidia. The solution is to upgrade the drivers to >=455.23.
CUDA_ERROR_UNSUPPORTED_PTX_VERSION: the provided PTX was compiled with an unsupported toolchain.
Right, seems we have that CUDA issue again. Arch is always using some newer Nvidia driver when they update CUDA. Lets see what got updated in that regard and find a way to downgrade. Seems CUDA is a hot topic anyway with some of you.
My main problem with CUDA is that with every newer version, support for - not too much - older GPUs is discontinued! I have a laptop with a GTX960M and with the current CUDA version is already deprecated. I guess with the next few CUDA updates my GPU will be completely useless. I own the laptop for 2 years only… though GTX960M is around for a bit longer…
I am one of the few remaining Firefox users.
Looks like this update interfered with Firefox somehow.
In stock Firefox 81, in about:support , Compositing has switched from OpenGL back to Basic and I get:
I didn’t notice any issue yet regarding that but my new firefox profile also has it set to basic. Not sure if it is an issue as test in “webgl aquarium” benchmark still has high framerate, or maybe it always had a bad framerate I consider ‘high’, I don’t know. Maybe I misunderstand the opengl/basic issue and it has nothing to do.
Also what do you call ‘glitches’? Do you mean tearing?
Indeed, it appears to be tearing. When I move the mouse wheel, only the upper part (a small bar) of the displayed page follows this movement, the lower part remains static but the border between the moving part and the static part subsequently also moves in parallel with the scroll bar button on the right side.
Looks kinda funny but unfortunately, it often renders the page not readable anymore.
A quick feedback from a few weeks old Linux noob on Manjaro:
Thank you for all the digital heroes for “living on the unstable/test” versions so that, we, the people on the stable can enjoy this so far so stable ManjaroOS as the nucleic core of an atom.
And I say this after deleting 15 other distros including Debian stable because they were sluggish or things did not really work. OpenSUSE LEAP stable (on two of my secondary laptops) is the only one that I could compare (by my feeling and experince so far).
Out of those like 15, Manjaro was the only distro which smoothly installed without any glitches or issues and with truly top performing desktop (snappiest of all) on all of my four (4) PCs which are really different configurations in age and in performance as well:
Lenovo Thinkpad X200T (13 years old, wounded in wars)
Lenovo Carbon X1 (1st generation, 7+ years old)
Custom DIY mini Intel i3 PC with IGPU
Custom power PC station (8700K, OEM NVME, Z370, Nvidia RTX2070)
I guess this update is working just fine. Although, it’s just me or, is nvidia-settings (for nvidia 455) not exist anymore? It’s still mentioned in nvidia-xconfig man page, but I can’t call it out. Also, I had to use TTY to reboot after updating. No big deal. It went back to normal shutdown/restart after that. Other than that, thanks for fixing cuda. I’m working with Blender and still can’t get away from that API yet. You guys awesome.