FS#57531 - [deepin] Missing Some Controls on Deepin UI

Attached to Project: Community Packages
Opened by Thiago França (tfsthiagobr98) - Friday, 16 February 2018, 15:19 GMT
Last edited by Evangelos Foutras (foutrelis) - Wednesday, 21 February 2018, 11:06 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Deepin don't support Qt 5.10.1 this cause to power menu not show any icons and login password field disappear.

Additional info:
* package version(s) 1.1.8-2
* config and/or log files etc.

pacman.log - https://gist.github.com/TFSThiagoBR98/319272a5f7454018a2412bfb60c22c5c
before.png - https://ibb.co/hhrVJ7
after.png - https://ibb.co/mLPT5n

Steps to reproduce:
Upgrade Qt5 5.10.0-2 -> 5.10.1-1 and Deepin.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Wednesday, 21 February 2018, 11:06 GMT
Reason for closing:  Fixed
Additional comments about closing:  qt5-base 5.10.1-2
Comment by Felix Yan (felixonmars) - Saturday, 17 February 2018, 17:46 GMT
See also upstream report: https://github.com/linuxdeepin/developer-center/issues/476
Comment by Evangelos Foutras (foutrelis) - Sunday, 18 February 2018, 19:00 GMT
Likely fixed by qt5-declarative 5.10.1-2 which reverts an upstream commit that also broke gcompris ( FS#57542 ).

Edit: According to feedback on the github issue, qt5-declarative 5.10.1-2 does NOT fix this.
Comment by Evangelos Foutras (foutrelis) - Monday, 19 February 2018, 11:51 GMT
Bisected the breakage to this commit: https://github.com/qt/qtbase/commit/7257862fb2 -- Seems like it could be reverted though it doesn't revert cleanly.

A bug for this already exists in Qt upstream: https://bugreports.qt.io/browse/QTBUG-66226
Comment by Evangelos Foutras (foutrelis) - Wednesday, 21 February 2018, 02:41 GMT
Went ahead and reverted that commit in qt5-base 5.10.1-2; better to have the old bug [1] than this one (which looks more serious).

Hopefully upstream Qt will fix this properly soon.

[1] https://bugreports.qt.io/browse/QTBUG-60231

Loading...