5.81-2 works, fixes BZ#2356863

lsblk -f:

NAME                       FSTYPE      FSVER    LABEL UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1                                                                                                     
├─nvme0n1p1                vfat        FAT16    EFI   E785-2187                               135,1M    32% /boot/efi
├─nvme0n1p2                ext4        1.0            31df2498-3903-450f-ae68-d9ab7fe628ad    369,3M    69% /boot
├─nvme0n1p3                LVM2_member LVM2 001       QcA5eV-lLYE-e3QZ-CgPN-njzM-DCrn-pjTR0m                
│ ├─fedora_max--n56vb-swap swap        1              c58f94c4-9e82-4266-a346-ca32208cf7e9                  [SWAP]
│ ├─fedora_max--n56vb-D    ext4        1.0            ef877a2a-180a-471c-bcc9-3a4985146761    344,1G    61% /mnt/d
│ └─fedora_max--n56vb-root ext4        1.0            7daf9d20-e401-477f-8c7f-c088838438de       97G    46% /
├─nvme0n1p4                                                                                                 
├─nvme0n1p5                ntfs                       9C28321C2831F63C                                      
└─nvme0n1p6                ntfs                       6A02F24D02F21DAF 

grub2-mkconfig:

Generating grub configuration file ...
Found theme: /boot/grub2/themes/megano-fedora/theme.txt
/usr/libexec/os-probes/50mounted-tests: line 186: 27934 Segmentation fault      (core dumped) grub2-mount "$partition" "$tmpmnt" 2> /dev/null
/usr/libexec/os-probes/50mounted-tests: line 186: 27957 Segmentation fault      (core dumped) grub2-mount "$partition" "$tmpmnt" 2> /dev/null
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done

efibootmgr:

BootCurrent: 0004
Timeout: 5 seconds
BootOrder: 0004,0006,0000,0001,0002,0003
Boot0000* UEFI IR-SSDPR-P34B-02T-80 GY5168865 1 HD(1,GPT,20786662-27e6-4d42-bd05-5ab648ab3727,0x800,0x64000)/\EFI\Boot\BootX64.efi{auto_created_boot_option}
Boot0001* ONBOARD NIC (IPV4)    PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(60189529e740,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0){auto_created_boot_option}
Boot0002* ONBOARD NIC (IPV6)    PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(60189529e740,0)/IPv6([::],0,Static,[::],[::],64){auto_created_boot_option}
Boot0003* UEFI HTTPs Boot       PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(60189529e740,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)/Uri(){auto_created_boot_option}
Boot0004* Fedora        HD(1,GPT,20786662-27e6-4d42-bd05-5ab648ab3727,0x800,0x64000)/\EFI\fedora\shimx64.efi
Boot0006* Windows Boot Manager  HD(1,GPT,20786662-27e6-4d42-bd05-5ab648ab3727,0x800,0x64000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000020000100000010000000040000007fff0400

ls -l /boot

total 1001878
-rw-r--r--  1 root root    281770 Feb 19 03:00 config-6.13.3-201.fc41.x86_64
-rw-r--r--  1 root root    281770 Feb 22 03:00 config-6.13.4-200.fc41.x86_64
-rw-r--r--  1 root root    281707 Feb 27 03:00 config-6.13.5-200.fc41.x86_64
drwx------  4 root root     16384 Jan  1  1970 efi
drwx------. 6 root root      1024 Mar  7 11:44 grub2
-rw-------  1 root root 313608270 Mar  7 09:30 initramfs-6.13.3-201.fc41.x86_64.img
-rw-------  1 root root 313599260 Mar  7 09:33 initramfs-6.13.4-200.fc41.x86_64.img
-rw-------  1 root root 313511837 Mar  7 09:17 initramfs-6.13.5-200.fc41.x86_64.img
-rw-r--r--. 1 root root    560575 Jun 23  2016 initrd-plymouth.img
drwxr-xr-x  3 root root      1024 May 10  2018 loader
drwx------. 2 root root     12288 May  5  2013 lost+found
-rw-r--r--  1 root root    184428 Feb 21 17:11 symvers-6.13.3-201.fc41.x86_64.xz
-rw-r--r--  1 root root    184444 Feb 25 09:46 symvers-6.13.4-200.fc41.x86_64.xz
-rw-r--r--  1 root root    184496 Feb 28 08:23 symvers-6.13.5-200.fc41.x86_64.xz
-rw-r--r--  1 root root  11041112 Feb 19 03:00 System.map-6.13.3-201.fc41.x86_64
-rw-r--r--  1 root root  11041786 Feb 22 03:00 System.map-6.13.4-200.fc41.x86_64
-rw-r--r--  1 root root  11043203 Feb 27 03:00 System.map-6.13.5-200.fc41.x86_64
-rwxr-xr-x  1 root root  16685416 Feb 19 03:00 vmlinuz-6.13.3-201.fc41.x86_64
-rwxr-xr-x  1 root root  16685416 Feb 22 03:00 vmlinuz-6.13.4-200.fc41.x86_64
-rwxr-xr-x  1 root root  16697704 Feb 27 03:00 vmlinuz-6.13.5-200.fc41.x86_64

With this update sddm can not autostart on boot (wayland):

sddm-helper-start-wayland[2312]: "kwin_core: Failed to open /dev/dri/card0 device (No such device)\nkwin_wayland_drm: failed to open drm device at \"/dev/dri/card0\"\n"
мар 07 08:12:31 MAXG155510 sddm-helper-start-wayland[2312]: "kwin_core: Failed to open /dev/dri/renderD129 device (No such device)\nkwin_wayland_drm: failed to open drm device at \"/dev/dri/renderD129\"\n"
мар 07 08:12:32 MAXG155510 sddm-helper-start-wayland[2312]: "KCrash: Application 'kwin_wayland' crashing... crashRecursionCounter = 2\n"

Reverting back to 6.3.2.1-1 solves the issue.

I have nvidia GPU in on demand mode, display is driven by Intel iGPU.

This issue still persists: https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/755

Anyone who experience this issue can use a workaround: create ~/.config/wireplumber/wireplumber.conf.d/headphonesfix.conf with the following contents:

monitor.alsa.rules = [
  {
    matches = [
      {
        # This matches the value of the 'device.name' property of the device.
        device.name = "~alsa_card.*"
      }
    ]
    actions = {
      update-props = {
        # Apply all the desired device settings here.
        api.acp.auto-profile = true
      }
    }
  }
]

Tested just now:

Problem 1: installed package kf5-libkgeomap-20.08.3-11.fc41.x86_64 requires libmarblewidget-qt5.so.28()(64bit), but none of the providers can be installed - installed package marble-widget-qt5-1:24.08.3-1.fc41.x86_64 conflicts with marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing - package marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing obsoletes marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt5-1:24.08.3-1.fc41.x86_64 from @System - package marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing conflicts with marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt5-1:24.08.2-1.fc41.x86_64 from fedora - package marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing obsoletes marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt5-1:24.08.2-1.fc41.x86_64 from fedora - package marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing conflicts with marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt5-1:24.08.3-1.fc41.x86_64 from updates - package marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing obsoletes marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt5-1:24.08.3-1.fc41.x86_64 from updates - cannot install the best update candidate for package marble-widget-qt5-1:24.08.3-1.fc41.x86_64 - cannot install the best update candidate for package kf5-libkgeomap-20.08.3-11.fc41.x86_64 Problem 2: problem with installed package - installed package kf5-libkgeomap-20.08.3-11.fc41.x86_64 requires libmarblewidget-qt5.so.28()(64bit), but none of the providers can be installed - package kf5-libkgeomap-20.08.3-11.fc41.x86_64 from fedora requires libmarblewidget-qt5.so.28()(64bit), but none of the providers can be installed - installed package marble-widget-qt5-1:24.08.3-1.fc41.x86_64 conflicts with marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing - package marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing obsoletes marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt5-1:24.08.3-1.fc41.x86_64 from @System - package marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing conflicts with marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt5-1:24.08.2-1.fc41.x86_64 from fedora - package marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing obsoletes marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt5-1:24.08.2-1.fc41.x86_64 from fedora - package marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing conflicts with marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt5-1:24.08.3-1.fc41.x86_64 from updates - package marble-widget-qt6-1:24.12.0-1.fc41.x86_64 from updates-testing obsoletes marble-widget-qt5 < 1:24.12.0-1.fc41 provided by marble-widget-qt5-1:24.08.3-1.fc41.x86_64 from updates - package marble-1:24.12.0-1.fc41.x86_64 from updates-testing requires libmarblewidget-qt6.so.28()(64bit), but none of the providers can be installed - package marble-1:24.12.0-1.fc41.x86_64 from updates-testing requires marble-widget-qt6(x86-64) = 1:24.12.0-1.fc41, but none of the providers can be installed - cannot install the best update candidate for package marble-1:24.08.3-1.fc41.x86_64

Looks like marble components are not properly obsoleted, or are repos not in sync yet?

Question. libvkd3d-shader package now has version 1.14, but it contains file libvkd3d-shader.so.1.12.0, is this correct?

Upgrades, works

Qt 6.8.0 is released as update for Fedora 41, please rebuild gstreamer1-plugins-good-qt6 against it.

I tried to install them out of curiosity and found out than nvidia driver package already has them, so I wanted to point that out. Everything works fine for me.

Works, but currently there's a conflict between egl-x11 and xorg-x11-drv-nvidia-libs: /usr/lib64/libnvidia-egl-xcb.so.1 /usr/lib64/libnvidia-egl-xlib.so.1

What is the intended way of packaging those libraries?

Works

With, I have that update installed.

@leigh123linux 550.78-1.fc40.x86_64 (rpmfusion)