Bug 454771 - Dolphin always opens maximized (even if before closing it was in a small window) when config file has `Window-Maximized [resolution]=true` line in it
Summary: Dolphin always opens maximized (even if before closing it was in a small wind...
Status: REPORTED
Alias: None
Product: frameworks-kxmlgui
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.94.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-02 20:32 UTC by MrNekit
Modified: 2022-08-25 15:20 UTC (History)
5 users (show)

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


Attachments
Demonstration (3.30 MB, video/mp4)
2022-06-02 21:09 UTC, MrNekit
Details
dolphinrc (1.26 KB, text/plain)
2022-06-03 19:52 UTC, MrNekit
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MrNekit 2022-06-02 20:32:47 UTC
STEPS TO REPRODUCE
1. Open doplhin
2. Resize unmaximize window (make it little)
3. Close dolphin
4. Open again

OBSERVED RESULT
Dolphin has opened maximized again.

EXPECTED RESULT
Dolphin open in little window from step 2. 

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.15.41-1-MANJARO (64-bit)
Graphics Platform: X11
Comment 1 MrNekit 2022-06-02 21:09:21 UTC
Created attachment 149421 [details]
Demonstration
Comment 2 Nate Graham 2022-06-03 17:47:23 UTC
Can you attach your ~/.config/dolphinrc file please?
Comment 3 MrNekit 2022-06-03 19:52:30 UTC
Created attachment 149443 [details]
dolphinrc
Comment 4 MrNekit 2022-06-03 19:52:41 UTC
(In reply to Nate Graham from comment #2)
> Can you attach your ~/.config/dolphinrc file please?

Done
Comment 5 Nate Graham 2022-06-06 17:44:48 UTC
If you delete this line:

HDMI-A-0 Window-Maximized 1920x1080=true

Does it start working as you expect?
Comment 6 MrNekit 2022-06-06 17:57:36 UTC
(In reply to Nate Graham from comment #5)
> If you delete this line:
> 
> HDMI-A-0 Window-Maximized 1920x1080=true
> 
> Does it start working as you expect?

Yes, now it is work.
Comment 7 MrNekit 2022-06-06 18:00:17 UTC
Also I've removed 

HDMI-A-0 XPosition 1920x1080=169
HDMI-A-0 YPosition 1920x1080=374

Now dolphin opens in the mid of screen (as it should)
Comment 8 Nate Graham 2022-06-07 15:44:29 UTC
Thanks, I had a feeling. Out of curiosity have you been using Dolphin for a long time on this system? Or is is a relatively recent install?
Comment 9 MrNekit 2022-06-07 15:46:44 UTC
I've installed this system (manajro kde) in march on a fresh pc.
Comment 10 Nate Graham 2022-06-07 16:03:36 UTC
Hmm, that's troublesome. It means there's a bug in our code somewhere, because I had thought we'd fixed the issue of these lines showing up in the config file. Thanks for the info and the bug report.
Comment 11 Michał Dybczak 2022-06-18 06:35:16 UTC
I noticed the same issue, also on Manjaro.
I thought that it came with Plasma 5.25 update, because I didn't notice it before.
However, in my case, I have 7 years old OS install.

I also am seeing Window-Maximized true multiple lines in config, although the Dolphin was closed as not-maximized window.

After deleting those lines, Dolphin opens not-maximized as it should be, although not in the last position. I guess, I need to clean up the config.
Comment 12 avalonvales 2022-08-25 08:55:00 UTC
Had this randomly happen to me as well. I believe it started after an update in the last month, although that's probably not awfully specific. I was confused as I explicitly checked the "application specific window settings" and nothing I did could revert it back to its usual behaviour. Thankfully deleting those lines fixed it.
Comment 13 Michał Dybczak 2022-08-25 15:20:34 UTC
After deleting the config, Dolphin behaves correctly, so it had to be correlated with some other line. The bad thing is, I lost tons of my own customizations and till today I can't get it all like it was before, so Dolphin is not so comfortable anymore. In time maybe...
Anyway, the problem was solved by nuking configs, so this is an individual problem and not a general bug.