Comments

54 Comments

After installing this and rebooting I'm getting horrible screen flickering on some GUI elements, like popup menus and when scrolling in firefox. I'm using KDE plasma and kwin_x11 and I don't know if it's actually caused by this update,it could be something else.

karma

@atim, no, it's not OK. GCC and annobin are out of sync again. Trying to build Boost with the updates-testing repo enabled fails with dozens of these errors:

annobin: command.c: ICE: The location of the "-fstack-clash-protection" flag has changed - please rebuild annobin
annobin: command.c: ICE: Please contact the annobin maintainer with details of this problem
annobin: command.c: Expeceted name: -fstack-clash-protection.  Actual name: -fstack-check=
cc1: error: failed to initialize plugin /usr/lib/gcc/x86_64-redhat-linux/10/plugin/annobin.so

(Note also "Expeceted" typo)

Fixes bug #1688562 (rootless "podman build" doesn't allow network access). I haven't tested other functionality.

BZ#1688562 rootless "podman build" doesn't allow network access
BZ#1695492 /usr/libexec/podman is not owned by any package

I've started a new build to fix the bad Obsoletes tag and will add it to this update when it's complete.

This update has been unpushed.

Still doesn't fix the problem, sddm fails to start when using nvidia drivers. SElinux exception is needed to get a working desktop system.

BZ#1598995 SELinux is preventing sddm-greeter from 'map' accesses on the chr_file /dev/nvidiactl.

Sigh, that was supposed to be a -1, because several of the bugs apparently fixed in this update, are not fixed.

Installs and works OK on F26.

karma

This is a major version update that breaks functionality, with no justification. This is against EPEL updates policy: https://fedoraproject.org/wiki/EPEL_Updates_Policy#Stable_Releases

karma

This is a major version update that breaks functionality, with no justification. This is against EPEL updates policy: https://fedoraproject.org/wiki/EPEL_Updates_Policy#Stable_Releases

karma

This is a non-backwards compatible change in a stable release, why?

There is no systray for Synergy now, it can only be configured on the command-line or in config files (and that makes it harder to stop/start the processes, and to debug connection logs).

It is no longer possible to use a mouse & keyboard attached to a client machine, it seems that synergy eats the input events, so you can only use the mouse & keyboard attached to the server. This is a major regression.

Boost.Python NumPy examples from upstream compile and run correctly.

Upgrading existing boost or boost-devel packages correctly installs the new boost-numpy package. After rpm -e --nodeps boost-numpy downgrading other boost packages also works correctly.

BZ#1451982 Missing Boost.Python NumPy extension
BZ#1488133 Local git aliases don't work in linked working tree
karma

No problems found

karma

No problems found