Bug 430145

Summary:	Dolphin cannot remember its position and size
Product:	[Applications] dolphin	Reporter:	Guo Yunhe <i>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	dolphin-bugs-null, nate
Priority:	NOR
Version First Reported In:	20.08.3
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Guo Yunhe 2020-12-08 11:45:25 UTC

SUMMARY
Every time I open Dolphin, the window is maximum, which is annoying in a 27inch 4K screen.

STEPS TO REPRODUCE
1. Open Dolphin.
2. Resize Dolphin to a smaller size.
3. Close and reopen Dolphin.

OBSERVED RESULT
Dolphin is always opened in maximum mode.

EXPECTED RESULT
Dolphin should remember its last position and size.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20201205
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.2
Kernel Version: 5.9.12-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa DRI Intel® UHD Graphics 620

ADDITIONAL INFORMATION
I have checked KWin option "Allow KDE apps to remember the positions of their own windows". But it has no effect.

Kate and Filelight also have the issue. But Konsole and Krita work perfectly.

Comment 1 Nate Graham 2020-12-08 14:53:55 UTC

Reminds me of Bug 426813. Does your ~/.config/dolphinrc file have any lines like this in it?

Window-Maximized 1016x1807=true
Window-Maximized 614x1093=true
Window-Maximized 647x1150=true
Window-Maximized 864x1536=true
Window-Maximized 904x1205=true
Window-Maximized 909x1617=true

Comment 2 Guo Yunhe 2020-12-08 14:56:45 UTC

Yes, it is:

Window-Maximized 1440x2560=true
Window-Maximized 2160x3840=true
Window-Maximized 320x427=true
Window-Maximized 400x533=true
Window-Maximized 720x1280=true
Window-Maximized 960x1707=true

Comment 3 Nate Graham 2020-12-08 14:58:34 UTC

Looks like the same issue then. I'll need some help debugging this (in Bug 426813) because I am not yet sure what's going on. It's some kind of regression that I caused in kconfig while implementing the position remembering feature.

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