Bug 1229922 (qt-5.5) - upgrade qt to 5.5
Summary: upgrade qt to 5.5
Keywords:
Status: CLOSED ERRATA
Alias: qt-5.5
Product: Fedora
Classification: Fedora
Component: qt5-qtbase
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: qt5-private 1247953 1252035 1255890
Blocks: 1245755 1249280
TreeView+ depends on / blocked
 
Reported: 2015-06-10 00:13 UTC by Mohammed Arafa
Modified: 2016-07-20 09:40 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-06 03:15:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 341497 0 None None None Never
Red Hat Bugzilla 1256572 0 unspecified CLOSED Qt 5.5.0 lets Plasma notifications show graphics glitches only 2021-02-22 00:41:40 UTC

Internal Links: 1256572

Description Mohammed Arafa 2015-06-10 00:13:57 UTC
Description of problem:
kde/qt monitor resolution issue fixed in qt 5.5

i opened a kde bug 347877 which specifically states the issue was fixed in qt5.5 see kde bug 341497 fedora 22 is still at 5.4 and is affected by the bug. this is a very annoying bug.
pls upgrade

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Rex Dieter 2015-06-10 04:30:29 UTC
Qt 5.5 is not released yet. When it is, we will consider it.

Comment 2 Bernie Innocenti 2015-06-14 18:50:18 UTC
Qt 5.5 also fixes a crash in plasmashell which affects me on Fedora 22 every time I unplug a monitor:

  https://bugs.kde.org/show_bug.cgi?id=343216

If Qt 5.5 is not ready yet, please apply the patch to Qt 5.4:

  https://codereview.qt-project.org/#/c/111100/

Comment 3 Rex Dieter 2015-06-14 19:37:42 UTC
That should be applied in this update already:
https://admin.fedoraproject.org/updates/FEDORA-2015-9718/qt5-qtdeclarative-5.4.2-2.fc22

Comment 4 Rex Dieter 2015-06-25 17:05:16 UTC
Initial test builds are available 
https://copr.fedoraproject.org/coprs/dvratil/qt5/

be warned, will include some bit of plasma-related abi breakage, until some packages that use private interfaces are rebuild against qt-5.5 (see bug #1233829)

Anyway, plan is to import into rawhide and work more on aforementioned bug #1233829 on (or shortly) after july 1 (planned release date for Qt 5.5.0)

Comment 5 Paulo Fidalgo 2015-08-01 09:49:45 UTC
Adding myself to CC as I have a dual monitor setup and got a lot of crashes in PlasmaShell.

Comment 6 Joe Christy 2015-08-10 01:39:12 UTC
After being lucky enough to catch, without totally wedging my machine, an instance of one of the bugs that causes plasmashell to crash several times a day and submit a detailed report with stack trace to KDE https://bugs.kde.org/show_bug.cgi?id=349062#c4. That was flagged by drkonqui as one of many duplicates. Those, in turn were all determined to due to not having upgraded qt5  to v. 5.5.0 https://bugreports.qt.io/browse/QTBUG-43827. Since plasmashell crashing (in fact, it crashed while I was writing this comment) renders both my Fedora machines, which run KDE, virtually unusable, I beg you to increase the priority of this bug.

Comment 7 Rex Dieter 2015-08-10 14:13:26 UTC
My understanding, is that QTBUG-43827 is (was, now fixed) a regression upgrading 5.4->5.5

That said, if you want to test Qt-5.5 *now*, it's available in (opt-in) copr:
https://copr.fedoraproject.org/coprs/dvratil/qt5/

We still have at least one blocker,  bug #1252035 and one nice-to-have bug #1233829

Comment 8 Raphael Groner 2015-08-25 10:11:49 UTC
It's not clear why Qt5.5 is now in Fedora 22, there are some major bugs reported and still unfixed, for instance see bug #1255890.

Comment 9 Raphael Groner 2015-08-25 10:14:16 UTC
Raising severity cause this update injects major impacts to other packages' functionality.

Comment 10 Rex Dieter 2015-10-06 03:15:19 UTC
Qt-5.5 has landed, may as well close this now.


Note You need to log in before you can comment on or make changes to this bug.