Bug 457950 - Dolphin windows reset their size in dual-monitor setup
Summary: Dolphin windows reset their size in dual-monitor setup
Status: RESOLVED DUPLICATE of bug 427875
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 22.04.3
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-16 10:10 UTC by Riccardo Robecchi
Modified: 2022-08-17 20:42 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 Riccardo Robecchi 2022-08-16 10:10:10 UTC
SUMMARY
I have two monitors arranged vertically, the top one with a resolution of 2560x1440 and the bottom one (which is designed as "primary") of 1920x1080. After booting the computer or waking it from sleep, Dolphin "forgets" the size I previously set and uses an apparently random, almost-square size. Furthermore, if I resize the window, the new size is only saved if I close the window while it is on the top monitor. If I close it on the bottom monitor, the size is not updated and reverts to the "wrong" one the next time I open Dolphin.

STEPS TO REPRODUCE
1. Boot the computer or wake it from sleep
2. Open Dolphin

OBSERVED RESULT
Dolphin's window size is not the one set by the user.

EXPECTED RESULT
Dolphin's window size is not changed randomly and stays the one set by the user.

SOFTWARE/OS VERSIONS
Linux: KDE neon
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-08-17 20:19:49 UTC
Are you using the X11 session? If so, this is very likely Bug 427875.
Comment 2 Riccardo Robecchi 2022-08-17 20:42:06 UTC
(In reply to Nate Graham from comment #1)
> Are you using the X11 session? If so, this is very likely Bug 427875.

Yep, X11. It looks like it is that bug indeed, as I just noticed today that Gwenview is affected as well. Thanks for pointing this out. Let's hope for a fix soon!

*** This bug has been marked as a duplicate of bug 427875 ***