Comments

352 Comments
karma

Despite the reported issue at https://bodhi.fedoraproject.org/updates/FEDORA-2024-92664ae6fe#comment-3529261 this worked for me. dracut --force followed by successful reboot with kernel 6.8.10-300.fc40.x86_64. cc @tyrbiter

karma

LGTM here on a Framework laptop 13 AMD 7840U UEFI LUKS btrfs GNOME Wayland.

@tyrbiter did you also update dracut (https://bodhi.fedoraproject.org/updates/FEDORA-2024-6f919aaf6d) before updating the kernel by any chance?

karma
BZ#2279206 keepassxc-2.7.8 is available
karma

LGTM, also fixes the segfault when locking the desktop with the vault unlocked: https://github.com/keepassxreboot/keepassxc/issues/10432

karma

LGTM: Framework laptop 13 AMD 7840U UEFI secure boot / LUKS / btrfs / GNOME / Wayland

BZ#2276375 Missing randomized slab caches for normal kmalloc: enable CONFIG_RANDOM_KMALLOC_CACHES=y
karma

LGTM on Framework laptop 13 AMD 7840U; Secure Boot/LUKS/btrfs/GNOME/Wayland

LGTM

BZ#2276078 Opening links in emails with Firefox fails if FF is already running
karma

LGTM, including with Google Pixel Buds Pro A2DP.

karma

LGTM on a framework 13 AMD 7840U LUKS/btrfs/GNOME/Wayland

Regression: Clicking on links fails to use the already-running Firefox. Instead it attempts to open a new FF process, resulting in an error popup (from that FF process presumably) about Firefox already running. Distro-syncing back to 115.9.0-1.fc39 resolves this.

karma

LGTM: Framework laptop 13 AMD 7840U LUKS/btrfs GNOME/Wayland

karma

LGTM on Framework 13 AMD 7840U LUKS/btrfs/GNOME/Wayland

BZ#2274069 AMD-PMF driver fails to load on kernel- 6.8.4-300.fc40.x86_64. Resulting in GPU failing to use full gpu available watts.

Framework 13 AMD laptop, GNOME/Wayland, UEFI, btrfs. LGTM.

No apparent trouble here on a Framework 13 AMD 7840U GNOME Wayland. Thermal zone info is missing, known issue with fix merged for 6.9 (and hopefully backported in a 6.8 update subsequent to this one).

karma

LGTM

BZ#2268610 bluez-5.73 is available
BZ#2269516 bluetooth.service becomes unresponsive when disabling the interface while a device is still connected since bluez 5.73
karma

LGTM on Framework 13 AMD 7840U GNOME Wayland.

karma

No regressions here.

100% CPU at rfkill block upstream at https://github.com/bluez/bluez/issues/785

karma

Thanks, I looked at the description from the -1 build, attempting to toggle bluetooth off from the GNOME quick settings reliably pegs it at 100%. I have to killall -9 bluetoothd to recover.

That happens with both this and the upstream tip+patch build I referenced earlier BTW.