Comments

187 Comments

What I know is that Ctrl+f is not working right in plain text files even with QtWebEngine 5.8.0. So I don't think that that is a regression from this update.

The new build should address the issue reported in the above comments (https://bugreports.qt.io/browse/QTBUG-61521), please retest.

This update has been unpushed.

Well, I was hoping to just edit the update with a fixed build, but now there is a mysterious further issue: https://bugzilla.redhat.com/show_bug.cgi?id=1464883#c2

Rebuilding stuff would work around it (kdepim is reportedly also affected), but QtWebEngine is supposed to be backwards-compatible, so I will try to fix it in QtWebEngine.

See also https://bugreports.qt.io/browse/QTBUG-60565

Hard to tell what your issue is, either there is still a race condition or xembedsniproxy (or even ksensors) is crashing entirely on you. What's sure is that it was worse before this update, because the setting supposed to prevent race conditions was ignored entirely in Plasma 5. So please use bugzilla.redhat.com to report your bug.

karma

Fixing broken dependencies is always good.

karma

See my test report for the F25 build from the identical specfile.

BZ#1395531 dnfdaemon package requires many SELinux-related dependencies
karma

I installed this update with:

sudo yum-deprecated --enablerepo=updates-testing --advisory=FEDORA-2017-6250e8f561 update

and I was able to remove the following SELinux-related packages:

  • audit
  • audit-libs-python
  • audit-libs-python3
  • checkpolicy
  • libcgroup
  • libselinux-python
  • libsemanage-python
  • libsemanage-python3
  • policycoreutils-python
  • policycoreutils-python-utils
  • policycoreutils-python3
  • python-IPy
  • python-IPy-python3
  • python2-imgcreate (was dragging in libselinux-python)
  • setools-libs

I did the removals with dnfdragora, so I can confirm that dnfdaemon still works fine here (SELinux disabled).

BZ#1395531 dnfdaemon package requires many SELinux-related dependencies
karma

A comment-only change is useless to push as an update and does not address the real issue at all.

karma

It is unacceptable that you are pushing this to stable despite the obvious regression.

karma

Is debuginfo not separated?

That's exactly it: https://bugzilla.redhat.com/show_bug.cgi?id=1424762#c1

The updated build should fix the speed dial regression.

karma

This fixes the regression #1413259 (tested the F25 package with the same contents).

BZ#1398300 git-cola-v2.9.1 is available
BZ#1413259 git-cola 2.9 is unusable, always hangs if maximized
BZ#1413277 git-cola-2.10 is available
BZ#1397822 git-cola-v2.9 is available
karma

I can confirm that this fixes the regression #1413259.

BZ#1398300 git-cola-v2.9.1 is available
BZ#1413259 git-cola 2.9 is unusable, always hangs if maximized
BZ#1413277 git-cola-2.10 is available
karma

Version 2.10, which should fix this, was released today.

karma

… or just update to 2.10, which was released today.