Description of problem: The full explanation is in this upstream (phototonic) bug report which I filed back in January, shortly after QT was updated to 5.4. Sadly I did not know or suspect it was a QT issue at that time. https://github.com/oferkv/phototonic/issues/170#issuecomment-120389113 This issue only affects Mageia 5 which is using QT 5.4.0. Tests by others in an OpenSUSE installation using QT 5.4.2 seem OK, so maybe we could update to 5.4.2 in Mageia 5? Mageia 4 is not affected which is using 5.2.0 Cauldron is not affected which is using 5.5.0. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: See upstream bug report. 1. 2. 3. Reproducible: Steps to Reproduce:
Unless a Qt update is planned for other reasons (which might already be the case, I'm not sure), I guess it would be safer to backport the probable commit that fixes this issue in the 5.4.x branch.
Assignee: bugsquad => mageia
Yes, Qt5 does need to be updated to 5.4.2 for Mageia 5. I don't know why it hasn't been built yet.
*** Bug 15009 has been marked as a duplicate of this bug. ***
Could bug 16615 also be related to this Qt 5.4.0 issue?
Possibly - if he can test his script in anything other than Mga5 it may give a clue.
can you test with qt 5.4.2 ?
(In reply to Nicolas Lécureuil from comment #6) > can you test with qt 5.4.2 ? Which is available from Core Updates Testing, to be clearer :)
(In reply to Nicolas Lécureuil from comment #6) > can you test with qt 5.4.2 ? Yes, that fixes *this* bug using a current git snapshot of phototonic in Mga5. x86_64 With the following installed: lib64qt5dbus5-5.4.2-1.1.mga5 lib64qt5network5-5.4.2-1.1.mga5 qttranslations5-5.4.2-1.mga5 lib64qt5widgets5-5.4.2-1.1.mga5 lib64qtx11extras5-5.4.2-1.mga5 lib64qt5core5-5.4.2-1.1.mga5 lib64qtsvg5-5.4.2-1.mga5 qtbase5-common-5.4.2-1.1.mga5 lib64qt5gui5-5.4.2-1.1.mga5 lib64qt5xml5-5.4.2-1.1.mga5 qtimageformats5-5.4.2-1.mga5
After downgrading phototonic to current Mageia 5 repo version this bug is also fixed with qt 5.4.2. :)
So what happened? [baz@localhost ~]$ urpmq -yf qt5 |grep "5.4.2" [baz@localhost ~]$
The update candidate was never passed onto QA, so it got cleanup from the repos a few days ago.
BUT as i had bugfixes to add in qt, i am adding it back in the testing repo and this time WE WILL VALIDATE IT ;)
Thanks Nicolas, Updating Mga5 to qt-5.4.2 from core/updates_testing has fixed this bug for me. I will close this when it gets pushed to core :)
Closing \o/
Status: NEW => RESOLVEDResolution: (none) => FIXED