Comments

254 Comments

Works for me on two machines (Haswell laptop and Ivy Bridge desktop).

karma

Works for me, no regressions noted.

@yisooan See: https://github.com/libming/libming/blob/master/configure.ac#L4 . It's a pre-release snapshot at this time and is versioned according to the versioning guidelines.

Actually, scratch that. It looks like dnf didn't install kernel-modules-4.20.11 and I haven't noticed. Sorry for the false alarm. All is fine.

It looks like nobody noticed that 4.20.11-200.fc29 is not shipping nouveau driver:

# rpm -ql kernel-modules-4.20.11|grep nouveau.ko
# rpm -ql kernel-modules-4.20.10|grep nouveau.ko
/lib/modules/4.20.10-200.fc29.x86_64/kernel/drivers/gpu/drm/nouveau/nouveau.ko.xz

A serious regression for me.

Generally works, but doesn't fix #1648978 .

BZ#1648978 SELinux is preventing plymouthd from 'getattr' accesses on the diretório /sys/firmware/efi/efivars.

Generally works, but doesn't fix #1648978 .

BZ#1648978 SELinux is preventing plymouthd from 'getattr' accesses on the diretório /sys/firmware/efi/efivars.

Generally works, but doesn't fix #1648978 .

BZ#1648978 SELinux is preventing plymouthd from 'getattr' accesses on the diretório /sys/firmware/efi/efivars.
karma

No more errors.

BZ#1508808 dbxtool service fails to start - EFI Signature List is malformed

-13 build works just as well, thanks.

BZ#1663599 Stop working with the error: Failed to get sync_sequence_id

Works fine again, thanks for the quick build release.

BZ#1663599 Stop working with the error: Failed to get sync_sequence_id

@carlwgeorge thanks for the report, however none of the stack traces in your paste contain anything related to mkvtoolnix. Also, mkvtoolnix can't possibly be able to crash gnome-shell directly. I think it just exposed a bug in either gnome-shell or one of the drivers. Please report the crash via abrt (System Tools -> Problem Reporting) if possible. Does it happen only under Wayland or under Xorg as well? Does it happen with any other desktop environment?

Does this contain the fix for the block layer data corruption bug described in https://lwn.net/Articles/774440/ and https://bugzilla.kernel.org/show_bug.cgi?id=201685 ?

Thank you for the feedback. Most certainly your crash is not related to libidn.

@jgu did it work in 27.0.0 or any previous version? Otherwise it's not a regression but a new bug and not a reason to hold this update.

@avij you're right, sorry about that. I forgot to do what @slaanesh just did (thank you!).

Why is this update (for F28) referencing an F30+ bug ticket?

It should still work with SeaMonkey, but yes, you're right. New builds with both classic and WebExtension versions done (like on F27-F28).

FYI you must not break upgrade paths between older and newer releases and dokuwiki-20180422a-2.fc27 is newer than dokuwiki-20180422a-1.fc28, which means rpm will consider it a downgrade when upgrading from F27 to F28 or newer. If you need a quick fix, please add a suffix, i.e. dokuwiki-20180422a-1.fc27.1 instead. See https://fedoraproject.org/wiki/Packaging:Versioning#You_need_to_change_an_old_branch_without_rebuilding_the_others for more details.

The correct thing to do now is to bump the Release field to 2%{dist} in F28+.

Works for me and together with FEDORA-2018-5829577f03 mitigates the Spectre v4 vulnerability.