[Stable Update] 2021-11-19 - Kernels, Gnome 41.1, Plasma 5.23.3, Frameworks 5.88, LxQt 1.0, Xorg-Server 21.1, Mesa

Just upgraded, seems like it went well but I’ll need to do more testing. Before upgrading I performed the pamac upgrade and wire-plumber changes so I wonder if that helped.

The only issue I have is when I try to use the 5.15 kernel, things become incredibly slow, the DE (KDE) locks up and shows blurred backgrounds where the application launcher and taskbar should be, and it’s pretty unfunctional overall. I’ve gone back to 5.14 in the meantime (using an X1 Carbon 9th gen)

There’s no poll for successful updates, so I would like to say it’s fine here and thanks for the hard working of Manjaro team.

5 Likes

Most likely philm wanted to add that later but I just added one.

At last…waited soooooooooo long…
Now updating…

GUI didn’t launch.
The problem is nvidia was updated to 495 and my (old) graphic card requires nvidia-470xx.
After removing all newer nvidia pkg and installing all needed nvidia-470xx pkg, all went fine.

Nice update anyway.
Thanks a lot :smiley:

2 Likes

Kernel 5.15.2 seems broken for me in this update. Most things worked fine under the last version of 5.15.x in stable (was it rc6?), but under 5.15.2 my system hangs at the desktop immediately after logging into sddm. I can not ssh into the system, can not switch virtual terminals, etc. 5.14.19 can go to the desktop (but has problems with my virtual machines) and 5.13 is still the only kernel working fine.

Other info:
CPU: 5950x
main GPU: AMD RX 6900XT
DE: swaywm
(other GPU but is still bound to vfio_pci at boot): nvidia RTX 3080

1 Like

Yeah, that is really a sad story. Any reason why they did not work on it that you are aware off?

2 Likes

Well I’ve had an interesting one and I’m not really sure what happened. I was running the update like normal and my computer locked up toward the end. Couldn’t get any response from anything, no switching to CLI or mouse movement. Waited a while and restarted and apparently I now have no kernel image (or fallback). Guess that’s a reminder to always backup. Figured I’d post about it in case anyone has any similar experiences.

2 Likes

Likely no developer time.

yes, I got the patch update. I don’t have time to test update.

I imagined that. Thank you.

I think it is time to come out of the mentality that free means no cost. We should come out of the socialist mentality and get to be a little more capitalistic in the #Foss community. I will start posting a few questions about this issue on another thread.

#Manjaro should start having a program with in it’s own OS that would allow us to make Monthly recurring payments for $X amount. The Developers place time, cost and different resources to get this going, and most of us Just want this for free as in cost. All those who are able to donate should be able to and someone should be in charge of getting that money.

You guys should have a Patreon acct among others to collect the necessary funds to run this beautiful and amazing operation. I mean, look at this update. I am downloading 1.8 GB and then some of software for my laptop. Who is getting the cost of this? I might be wrong, maybe you do have an acc for collecting funds. Please let me know if you do. Maybe something that we need to start thinking like #ElementaryOS or something. But I am not a developer.

I wish you well and @Strit Thank you for your quick reply. :slight_smile:

1 Like

I think they are just goofing off and having a good time with the OS.

1 Like

i will wait 1 day to make sure everything is okey

4 Likes

The ARM Team does have a Patreon, else they accept donations via opencollective

5 Likes

This bug was already fixed.

Thank you, you will have money flowing your way soon.

1 Like

This is a good idea and I was doing it most of the time too. Also make sure you use a system backup/recovery tool like Timeshift every time before you do a bigger update.

2 Likes

The update went smoothly, I’m using gnome DE, and there wasn’t any big problem as such.
A couple of small issues I did face however were:

  1. the wallpaper was set to blue color from my selected time changing wallpaper(probably because of updates to that as well)
  2. DE was behaving oddly, like the “Show Application” button was missing from the dock, wasn’t able to switch workspace. I guess these were because I did the changes to /etc/environment as suggested by update log(==> We have switched into qgnomeplatform instead qt5ct so now), took 2 restarts of the system(probably logout/login would be enough, but rebooted because of kernel update) to get it acting normally.

I also faced some other issues, but they were just on my level and I also had to update mirrors to get better download speed(simple sudo pacman-mirrors --fasttrack)

1 Like

I have an old Nvidia GTX 760 graphics card that is unsupported by the current proprietary driver version 495. However, driver was updated automatically from version 470 to the newest version resulting in black screen after reboot (as I expected). I had to manually remove linux514-nvidia kernel module and install linux514-nvidia-470xx module. Now everything seems to work properly. Actually, I have used mhwd -r pci video-nvidia and mhwd -i pci video-nvidia-470xx commands.

8 Likes

EDIT: I created a support issue @ 2021-11-19 Stable Update - error in "Install DKMS modules" step which was resolved and ended up having nothing directly to do with this update.

Expand to see original post

I proceeded with a pamac update (GUI) after updating libpamac first (sudo pacman -Sy libpamac)… I didn’t need to worry about the pipewire/wireplumber conflict as I do not have wirerplumber installed.

For the most part, the update went smoothly and I am booted back into an update Manjaro on Kernel 5.14.18 (previously 5.14.10).

However, I did notice issues in the pamac GUI log… and later extracted from var\log\pacman.log related to v4l2loopback-dkms (the pamac GUI’s package name)…

[2021-11-19T10:51:06-0600] [ALPM] running '70-dkms-upgrade.hook'...
[2021-11-19T10:51:06-0600] [ALPM-SCRIPTLET] ==> Unable to remove module v4l2loopback/0.12.5 for kernel *: Not found in dkms status output.
[2021-11-19T10:51:06-0600] [ALPM] running '71-dkms-remove.hook'...
[2021-11-19T10:51:06-0600] [ALPM-SCRIPTLET] ==> Unable to remove module v4l2loopback/0.12.5 for kernel 5.14.10-1-MANJARO: Not found in dkms status output.
[2021-11-19T10:51:06-0600] [ALPM-SCRIPTLET] ==> Unable to remove module v4l2loopback/0.12.5 for kernel 5.10.70-1-MANJARO: Not found in dkms status output.

<removed many unrelated/successful lines>

[2021-11-19T10:51:51-0600] [ALPM] running '70-dkms-install.hook'...
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing home kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing proc kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing lost+found kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing 5.10.79-1-MANJARO kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing lib kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing mnt kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing desktopfs-pkgs.txt kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing rootfs-pkgs.txt kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing bin kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing tmp kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing etc kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing swapfile kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing 5.14.18-1-MANJARO kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing sys kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing dev kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing usr kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing sbin kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing lib64 kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing data kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing share kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing opt kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing var kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing srv kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing root kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing run kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> ERROR: Missing boot kernel headers for module v4l2loopback/0.12.5.
[2021-11-19T10:51:51-0600] [ALPM] running '90-mkinitcpio-install.hook'...
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
[2021-11-19T10:51:51-0600] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img

Do these errors mean that my current (5.14) and backup (5.10 LTS) kernels were not updated properly… and/or perhaps some things (headers?) it was trying to build against weren’t installed yet?

This is what I see for kernels, post update…

P.S. My favorite fixes/additions in KDE that I’ve noticed so far…
1. right-clicking a desktop icon (on the right monitor) no longer opens the context menu on the left monitor… a fix I’ve been looking forward to for a while!
2. the inclusion of accent colour settings… yay!
3. KDE would sometimes forget that I disabled my AMD HDMI/DP sound… now it has an “Inactive Cards” section where it’s now listed as “Profile = Off”
4. audio profiles/test moved up a level to “Playback Devices”

EDIT: Is it because dkms in pamac lists no “header dependencies” selected/installed?


Instead of selecting any of the listed optional dependencies, should I pick the “version specific” ones from pamac?

And then what? Reinstall via pacman -S v4l2loopback and then run mkinitcpio -P ?

P.S.S. Are there any issues trying to be “future proof” and installing the 5.15 and 5.16 packages even though I’m not using those kernels yet?

1 Like