Comments
kkofler
3.1.6 fixes a regression in 3.1.5: the finished.conf module configuration file was corrupt.
3.1.6 fixes a regression in 3.1.5: the finished.conf module configuration file was corrupt.
I've had it just not do anything. But this is with the old 5.8.0, mind you.
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.
Looks like I have a fix that works now (built in Rawhide already): http://pkgs.fedoraproject.org/cgit/rpms/qt5-qtwebengine.git/plain/qtwebengine-opensource-src-5.9.0-qtbug-61521.patch?id=ace3e112e6b8e0338b84be9abe5e63d7052ecf54
I'll be updating the F26 update today.
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
I'm testing a fix now: http://pkgs.fedoraproject.org/cgit/rpms/qt5-qtwebengine.git/commit/?id=09a57d530ce6e89d75b43e1d73007b1b66a3bb8f but it will be a while until I have F26 builds ready to test.
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.
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.
Fixing broken dependencies is always good.
See my test report for the F25 build from the identical specfile.
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).
A comment-only change is useless to push as an update and does not address the real issue at all.
It is unacceptable that you are pushing this to stable despite the obvious regression.
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.
Shouldn't this obsolete libtxc_dxtn now that S3TC support is built in? Or are there other users of that library?