[Unstable Update] 2021-11-11 - Gnome 41.1, Xorg-Server 21.1, LxQt 1.0, Nvidia 470.86, Plasma 5.23.3

Why is that? 71-1 works fine for me.

Dont know, it was disabled (and showing not compatible) when i booted after installing the updates. So i installed the git version and rebooted and it worked fine.

Well, I lost video playing with that update.
Both in Firefox and in Edge, in wayland and in Xorg… And also in SMPlayer.
Also, Firefox and Thunderbird are freezing for 15 seconds every other minute.
I’m on Gnome with amdgpu.

Gnome 41 and all extensions are working perfectly for me too! :slight_smile:

Well, then create a new thread in #support with more details.

A post was split to a new topic: Tuxedo-keyboard 3.0.9 doesn’t build on linux510 and/or linux514

That’s alright, I am about to solve it.
I narrowed it down to pipewire.
During the update, it asked me if I wanted to replace pipewire-media-session by wireplumber. I said yes. That change broke the sound. I have no output devices, hence no video playing.

And what was the default option suggested for you? to replace or not?

The default has always been pipewire-media-session, but I think wireplumber will eventually replace it. So I went ahead with replacing it when asked during the update.
I think it also uninstalled manjaro-pipewire alongside pipewire-media-session. Basically, it just created a big mess.

I have reverted the change, cleaned house on config files and now everything is back in order, got output devices back (and the volume icon) and video playing is working anew.

A post was merged into an existing topic: Tuxedo-keyboard 3.0.9 doesn’t build on linux510 and/or linux514

I’ve read several cases of unwanted Wayland switch following the Gnome 41 upgrade.

I hadn’t encountered anything similar, updating was transparent after reboot. I just made the update in TTY, and do not have any exotic setup in conf files.

My few extensions worked out of the box following 41, including Dash to Dock. No need to use the AUR version.

Hi, there is an issue with installing 5.15 realtime kernel. After installation in grub its recognized as normal 5.15. When both 5.15 and 5.15-rt are installed, the system hangs on boot (no 5.15_rt17-1 option in grub only 5.15.2-1), no difference it is installed via Pamac or Manjaro Settings Manager.

Installing linux515-rt (5.15_rt17-1)...
Running post-transaction hooks...
Arming ConditionNeedsUpdate...
Updating module dependencies...
Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux515-rt.preset: 'default'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.0-1-rt17-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515-rt.preset: 'fallback'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.0-1-rt17-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful
Updating Grub-Bootmenu
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-rt-x86_64-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

linux514 got updated, but linux514-nvidia-470xx wasn’t bumped, so this combo is currently not bootable. Version magic doesn’t match.

Except 515 kernel series, the 470xx is missing. Seems our CI did not have that added yet @oberon

3 posts were split to a new topic: What driver do I use for nvidia gt430?

3 posts were split to a new topic: Issues with latest manjaro-zsh-config update

Linux 5.16-rc1 Released With Intel AMX, FUTEX2, Folios and I really cant wait to test it …

I know you are busy fixing other things , have a nice day :slight_smile:

1 Like

@wolfyrion
I think the target thread for the 5.16rc1 kernel request is the Update requests for packages built by Manjaro developers
Please post there and remove here.

I realized awful behavior of the

linux516
5.16rc1.211115.gfa55b7d-1

It present in safely removal of USB stick drives: may “PC was hanged” 2 times while that operation: operation did not complete (first time ejecting via GUI menu, second time with udisksctl power-off (after successful sudo eject sda). All other components, GUI works fine, but in order to get safely remove I call PC reboot via GUI and reboot procedure it hangs for several minutes. Hard reset was then.
Second time while udisksctl power-off hangs with no answer I switch to tty and systemctl reboot and it semi-hangs for 20 minutes: kernel periodicaly shows messages about hanged component.
Both times I need to hard reboot PC.

After first hard reset I lost history file of zsh: I have cleaned history now.

Like logs? ok: here is `journalctl`

First hang

~/Desktop ❯ journalctl -b-5 -p3 | grep -i "dumped core"
Nov 16 22:54:33 pc systemd-coredump[24975]: Process 805 (Xorg) of user 0 dumped core.
Nov 16 22:54:35 pc systemd-coredump[25082]: Process 909 (kwin_x11) of user 1000 dumped core.
Nov 16 22:54:36 pc systemd-coredump[25105]: Process 1421 (opera) of user 1000 dumped core.
~/Desktop ❯      

Second hang:

Nov 17 11:05:06 pc kernel: INFO: task pool-udisksd:4995 blocked for more than 860 seconds.
Nov 17 11:05:06 pc kernel:       Not tainted 5.16.0-1-MANJARO #1
Nov 17 11:05:06 pc kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 17 11:07:09 pc kernel: INFO: task pool-udisksd:4995 blocked for more than 983 seconds.
Nov 17 11:07:09 pc kernel:       Not tainted 5.16.0-1-MANJARO #1
Nov 17 11:07:09 pc kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 17 11:09:11 pc kernel: INFO: task pool-udisksd:4995 blocked for more than 1105 seconds.
Nov 17 11:09:11 pc kernel:       Not tainted 5.16.0-1-MANJARO #1
Nov 17 11:09:11 pc kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 17 11:11:14 pc kernel: INFO: task pool-udisksd:4995 blocked for more than 1228 seconds.
Nov 17 11:11:14 pc kernel:       Not tainted 5.16.0-1-MANJARO #1
Nov 17 11:11:14 pc kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

The purpose of that post:

  1. Use the 5.16rc1 kernel version only of you need it. Wait for the rc2 at least.
  2. Do not propagate the rc1 into testing and stable “downstream” branches.

Thanks for the warning.

I can’t help it, but this comes to mind:

  1. Nobody needs an rc kernel
  2. IMHO it does not matter if this goes to testing - it is an rc and not a stable kernel. People should not use those unless they want to find and report bugs to https://bugzilla.kernel.org/.
3 Likes