Bug 402244 - breeze.so breaks Qt application layout settings
Summary: breeze.so breaks Qt application layout settings
Status: RESOLVED WORKSFORME
Alias: None
Product: Breeze
Classification: Plasma
Component: QStyle (show other bugs)
Version: 5.14.4
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-17 15:45 UTC by mathieu.westphal
Modified: 2021-02-17 18:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mathieu.westphal 2018-12-17 15:45:54 UTC
When opening and closing a Qt application, settings are automatically saved by Qt so the layout of the application stays the same when they are changed by the user.

If breeze.so is loaded by Qt, then this saving step saves incorrect values which causes an empty layout to be loaded next time, all toolbars and dock widgets will have disappeared.


STEPS TO REPRODUCE
1. Open a Qt application with toolbars
2. Close it
3. Open it again

OBSERVED RESULT
Qt layout is empty, all toolbars and dock widgets are hidden.
Removing the settings fix the issue.


EXPECTED RESULT
Application should look the same as before




SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ArchLinux
KDE Plasma Version: 5.14.4
KDE Frameworks Version: ?
Qt Version: 5.12.0


Preventing breeze.so to load prevent the issue
Using breeze.so from 5.12.4 (Ubuntu current version) prevent the issue.

for reference : https://gitlab.kitware.com/paraview/paraview/issues/18659
Comment 1 mathieu.westphal 2019-01-11 14:03:09 UTC
Looks like it is related to using setStyleSheet.

See here for reference : 
https://gitlab.kitware.com/paraview/paraview/merge_requests/2963
Comment 2 Nate Graham 2021-02-16 20:56:47 UTC
Is this still happening with Breeze 5.21? If so, can you provide an example of an application that can be used to reproduce the issue? Thanks!
Comment 3 mathieu.westphal 2021-02-17 09:25:54 UTC
Tbh I have no idea. You can try with an old version of ParaView, eg ParaView 5.5.
Comment 4 Nate Graham 2021-02-17 15:56:42 UTC
I tried with the latest version of ParaView available in my distro (5.8) and couldn't reproduce the bug. Let's call it fixed. :)
Comment 5 mathieu.westphal 2021-02-17 16:02:10 UTC
We fixed it in ParaView here, way before ParaView 5.8, by not using setStyleSheet.

https://gitlab.kitware.com/paraview/paraview/-/merge_requests/2963

I'm fine with closing as we are not impacted anymore.
Comment 6 Nate Graham 2021-02-17 18:11:42 UTC
Yeah in general using setStyleSheet is a good way to break things. :) See also Bug 354627.