Comments
rspliet
Resolves the issue/conflict w/ libdmapsharing4-3.9.11.
Breaks Rhythmbox. dnf downgrade libdmapsharing4-3.9.10-6.fc37 restores rhythmbox functionality
@gcbox I had seen your comment and had since tested 5.18.16 successfully, thanks. That said, my feedback here is mainly meant to alert the kernel team that something is wrong and that this is not an anomaly - hence the reply with the downvote and details. 5.18.15 should not have been pushed, and I hope that my feedback can lead to the withdrawal of this kernel. If 5.18.16 hadn't worked then I would have chimed in on bugzilla too.
Works for me, does not exhibit the issue I saw with 5.18.15 either on a cold- or a warm boot.
Doesn't boot on my machine. Just gives a text output with some generic device discovery messages. It looks like there's an error at the top, but that's scrolled offscreen within miliseconds. Never prompted for my disk encryption password so these logs are not stored either. Asus M5A97 Evo R2.0 AMD FX 6300 NVIDIA GeForce GT640
Reverting to 5.18.13 works.
Quick test shows it works on GK107, Gnome-shell, Firefox + Youtube (which should be vaapi-accelerated).
Breaks the rendering of the mouse cursor on Wayland for NVIDIA GeForce Kepler-generation GPUs driven by nouveau. This is a known bug in upstream kernel 5.11+. See RHBZ #1941291 . A patch exists on the nouveau mailing list but has yet to be brought upstream. May wish to apply this downstream.
Installed and booted on two machines, no observed regressions. - Asus K501UB laptop, Intel I5 6200U, Intel HD 520+NVIDIA GeForce 940M (nouveau) - Asus M5A97 EVO r2, AMD FX6300, NVIDIA GeForce GT640 (nouveau)
@mooninite : Apparently this is a long standing bug [0] on the topic, to which no fix has been made to this day. The accompanying releng issue [1] has been closed stating "fixed" while the bugzilla entry's status is "CLOSED CANTFIX". Feel free to chime in at [0] if you think there is anything to contribute to the bug report.
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1652872 [1] https://pagure.io/releng/issue/7071
glibc-headers-2.29-12.fc30.i686.rpm appears to be missing from the updates repositories, despite indication of successful build of the package in koji. Prevents updates on systems that require glibc-headers.i686 with the following error:
Probleem 1: package glibc-headers-2.29-9.fc30.i686 requires glibc = 2.29-9.fc30, but none of the providers can be installed - cannot install both glibc-2.29-12.fc30.i686 and glibc-2.29-9.fc30.i686 - cannot install both glibc-2.29-9.fc30.i686 and glibc-2.29-12.fc30.i686 - cannot install both glibc-2.29-12.fc30.x86_64 and glibc-2.29-9.fc30.x86_64 - cannot install both glibc-2.29-9.fc30.x86_64 and glibc-2.29-12.fc30.x86_64 - cannot install the best update candidate for package glibc-headers-2.29-9.fc30.i686 - cannot install the best update candidate for package glibc-2.29-9.fc30.i686 - cannot install the best update candidate for package glibc-2.29-9.fc30.x86_64 Probleem 2: problem with installed package glibc-headers-2.29-9.fc30.i686 - glibc-headers-2.29-9.fc30.i686 has inferior architecture - cannot install both glibc-headers-2.29-12.fc30.x86_64 and glibc-headers-2.29-9.fc30.x86_64 - cannot install both glibc-headers-2.29-9.fc30.x86_64 and glibc-headers-2.29-12.fc30.x86_64 - cannot install the best update candidate for package glibc-headers-2.29-9.fc30.x86_64
Fixes #1594572 introduced with 4.17.2-200.x86_64.fc28.
Fails to recognise keyboard in Asus K501UB laptop: https://bugzilla.redhat.com/show_bug.cgi?id=1594572
Successfully enables Opus support in Picard. Thanks!
This kernel fixes a regression introduced in kernel 6.12 where the backlight controls no longer functioned on an Asus Zenbook (UM3402).