SUMMARY Spin off from https://bugs.kde.org/show_bug.cgi?id=431230. In there is also the dolphinrc file attached. When closing Dolphin and opening it again, it restores in a pretty small form factor not remembering its previous size (no matter whether maximized or just resized). This happens on X11 for me with Tumbleweed (most current version).
DP-1 HDMI-2 Height 1440=480 DP-1 HDMI-2 Width 2560=640 So Dolphin thinks its window size should be 640x480. When you increase the window size and close Dolphin, do either of these lines in the dolphinrc file change? Do you have any window rules?
That was a wrong dolphinrc file I uploaded (at least I think so - I guess I forgot to change the window size when launching dolphin after deleting the previous dolphinrc file to get a clean file). I have uploaded a correct one where I maximized the window and the problem still happens: https://bugs.kde.org/show_bug.cgi?id=431230#c3.
Forgot to answer the window rules question: No, I think I don't have any, at least I never have manually created one.
I just saw that also the other file I uploaded contains the lines you mentioned (while also containing `DP-1 HDMI-2 Window-Maximized 1440x2560=true`). So you might already be referring to that file. I'll try to test what happens when changing window sizes soon.
When you increase the window size and close Dolphin, do either of these lines in the dolphinrc file change?
Will report back soon (the next time I come around booting to Tumbleweed).
(In reply to Nate Graham from comment #5) > When you increase the window size and close Dolphin, do either of these > lines in the dolphinrc file change? Just tested and yes, they change. But also then, when launching Dolphin again it opens small. Closing it again overwrites those lines again with the small values.
That's bizarre. It makes no sense. It's like reading the value is broken, but writing it works. Are the file permissions for your dolphinrc file sane? Could it be writable but not readable? Are there any other settings saved to that file that are not read correctly after restarting Dolphin? For example changing anything on the General page in the settings window.
Yes, the behavior is pretty awkward. It also seems to happen only on the Tumbleweed system, Manjaro and the KDE Neon unstable VM don't seem to suffer from this. Problematic permissions *should* be covered by the deletion of the file in theory, but I'll make sure to check them! Also I think that other stuff in that file is applied correctly (I know for example that the window position is restored correctly and the last opened directory is also restored as expected).
I can confirm this bug. I had it once and IIRC "solved" it by deleting the dolphinrc file. However, now the behaviour is back. What I find interesting... I tried the following: - Quit dolphin - Removed that file - Started dolphin again Dolphin still came up with the same, wrong window size. But otherwise, it still remembered all of the other settings (e.g. the last folder it has been in). It somehow seems like the config is cached somewhere and not updated, no matter if that file is removed or not.
Permissions for the dolphinrc file look sane. My user is shown as owner and the owner has rw- permissions.
(In reply to Martin Höher from comment #10) > Dolphin still came up with the same, wrong window size. But otherwise, it > still remembered all of the other settings (e.g. the last folder it has been > in). It somehow seems like the config is cached somewhere and not updated, > no matter if that file is removed or not. Good to know I am not alone with this. Can you add some details about your setup (Distribution, X11 or Wayland, other special things like multiple monitors)? Also, what was the wrong window size? 640x480?
(In reply to Claudius Ellsel from comment #12) > (In reply to Martin Höher from comment #10) > > Dolphin still came up with the same, wrong window size. But otherwise, it > > still remembered all of the other settings (e.g. the last folder it has been > > in). It somehow seems like the config is cached somewhere and not updated, > > no matter if that file is removed or not. > > Good to know I am not alone with this. Can you add some details about your > setup (Distribution, X11 or Wayland, other special things like multiple > monitors)? Also, what was the wrong window size? 640x480? Sure. I am on Fedora 33, X11. I am using a dual-monitor setup, with a laptop and - attached to it an external 4K monitor. Dolphin says it is at version 20.08.3. For me, the window size seems to be fixed to 1920x740 (so, rather large).
Multi monitor it is. After deactivating one of mine, it works for me again. As I suspected in the original bug report, this is strongly related, maybe even a duplicate of https://bugs.kde.org/show_bug.cgi?id=427875. Having played around a bit, I am rather sure it is a duplicate. I will first mark the Konsole and Dolphin spin off as duplicate of my original report and then mark the as duplicate of https://bugs.kde.org/show_bug.cgi?id=427875. (Martin, I am assuming that you have the same problem, but please check whether this is correct, else we can track the bug you are experiencing somewhere else)
*** This bug has been marked as a duplicate of bug 431230 ***
(In reply to Claudius Ellsel from comment #14) > Multi monitor it is. After deactivating one of mine, it works for me again. > > As I suspected in the original bug report, this is strongly related, maybe > even a duplicate of https://bugs.kde.org/show_bug.cgi?id=427875. Having > played around a bit, I am rather sure it is a duplicate. I will first mark > the Konsole and Dolphin spin off as duplicate of my original report and then > mark the as duplicate of https://bugs.kde.org/show_bug.cgi?id=427875. > > (Martin, I am assuming that you have the same problem, but please check > whether this is correct, else we can track the bug you are experiencing > somewhere else) Yes, I can confirm: If I unplug the external monitor, everything is fine and Dolphin remembers the window size properly between restarts.
Thanks for confirming! I suggest you to follow up in the original bug then (linked above).