SUMMARY I like to start Kate with specific dimensions and in a specific position on the screen(s). However, Kate doesn't remember its dimensions and it's position when I close it and start it again. Most of the times start at the "primary" screen, although it was closed on another screen and its dimensions are very small, almost non usable. Every time I start it, I have to resize it and move to the position I want and the screen I want. I clearly remember that this wasn't an issue in the recent past. Also, this is not a duplicate of 423191 because in my case kate doesn't remember it's starting position or screen or dimensions regardless where I start it/close it! A note: If I start kate from the cli, it starts on the screen the konsole is. Which more or less explains why the it always starts on my laptop's screen (primary) and not in the desired one. STEPS TO REPRODUCE 1. Start Kate 2. Resize and reposition the Kate's window 3. Close kate 4. Start it again OBSERVED RESULT Kate start in the middle of the screen. The size of the window is ALWAYS 510x640px, which means that it's not a calculated from the screen size since I have a FHD and a QHD screen. EXPECTED RESULT Kate should start at the position it was closed and with the same dimensions it had prior its closure. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.24 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
Interesting. As far as I know, this is fixed in 5.26, but the bug report is still in reported status.
If you're still have this problem, you can try to rename following files/folders to reset kate config: * ~/.config/katerc * ~/.local/share/kate I do remember that I had such problem because of broken config due to X11/Wayland switching.
(In reply to Peter Tselios from comment #1) > Interesting. > As far as I know, this is fixed in 5.26, but the bug report is still in > reported status. Well, not fixed in 5.26... I just upgraded to 5.26 from Fedora RPMs and it's not fixed :(
(In reply to Peter Tselios from comment #3) > (In reply to Peter Tselios from comment #1) > > Interesting. > > As far as I know, this is fixed in 5.26, but the bug report is still in > > reported status. > > Well, not fixed in 5.26... > I just upgraded to 5.26 from Fedora RPMs and it's not fixed :( Removing katerc fixed it. Good :)
*** This bug has been marked as a duplicate of bug 461937 ***