Comments

63 Comments

Thank you for the feedback. There was indeed more X11 usage that needed to be conditionalized. I figured out how to test this locally (with https://wiki.gnome.org/Initiatives/Wayland/GnomeShell/Testing ) and I believe the newly built 0.8.0-4 is working correctly. Could you please try again?

Thank you for the report. I run an X11 desktop so of course I didn't see the crash when I tried. It turns out 0.8.0 added additional X11-dependent code that needed to be made runtime-conditional instead of compile-time. If you would be able to try -3 and confirm that works on your Wayland desktop, I can try pushing my changes upstream.

This update has been unpushed.

This update has been unpushed.

BZ#1919034 stress-ng-0.12.02 is available
BZ#1928427 stress-ng-0.12.03 is available
BZ#1919034 stress-ng-0.12.02 is available
BZ#1928427 stress-ng-0.12.03 is available

@atim this was already noted in the description of this update. The conflict has to be fixed on the other end, and they have already been notified.

@besser82 this was already noted in the description of this update. The conflict has to be fixed on the other end, and they have already been notified.

This update has been unpushed.

BZ#521902 kdelibs: use ca-certificates' ca-bundle.crt
BZ#1529417 kdelibs3 does not find compat-openssl10-1.0.2m
BZ#1509862 xpdf cannot find display fonts

Doesn't the fix for CVE-2017-14929 cause an ABI break?

Doesn't the fix for CVE-2017-14929 cause an ABI break?

Doesn't the fix for CVE-2017-14929 cause an ABI break?