| Summary: | No saved size & position | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | vic <victorlysak78> |
| Component: | general | Assignee: | Konsole Developer <konsole-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | asn, aumartyom, bugseforuns, duha.bugs, fanzhuyifan, kde, miranda, nicolas.fella, smowtenshi, volodarolathana |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 24.05 | |
| Sentry Crash Report: | |||
| Attachments: | shoot | ||
|
Description
vic
2024-02-27 15:09:37 UTC
If you go to konsole settings - general, do you have remember window size checked? Created attachment 166173 [details]
shoot
Yes, it is checked in (No 1 in the list) need to add to this, that this issue happens in plasma 6 on wayland, but when I log into X11 konsole remembers its size and position Remembering window positions is not something applications can do on Wayland. Remembering the size is expected to work, and does work for me Than, what does have to remember that in Wayland? *** Bug 482907 has been marked as a duplicate of this bug. *** I am also facing this bug. Konsole is ignoring the "Remember window size" option and is using the "Initial terminal size" option set in the profile. For me, it is not working on both Wayland and X11. It worked fine on Plasma 5. I have tried removing the konsolerc file from .config and the konsole folder in .local/share but the issue was still there. Is there anything else that I can try? System Information - Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: Wayland Konsole Version: 24.02.0-1 I tested this with different Global Scale. If the scale is 100% then Konsole remembers the window size, but if the scale is any value other than 100 then it uses the Initial columns set in the profile. I am using 125% scale so this bug is appearing for me. I had the display at 105% - didn't work. I set it to 100%, reboot, doesn't work. I can reproduce even using display scale 100%. I maximize and then close Konsole, but Konsole never opens maximized. Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Graphics Platform: Wayland OK. What I found is that if I right-click on the very top strip, then click on More Actions > Configure Special Window Settings, then on Add Property, choose position whatever I need, then click on apply, than it will remember the konsole's position. Bloody hell, what a hassle. (In reply to vic from comment #12) > OK. What I found is that if I right-click on the very top strip, > then click on More Actions > Configure Special Window Settings, > then on Add Property, choose position whatever I need, > then click on apply, > than it will remember the konsole's position. > > Bloody hell, what a hassle. yeah, it does work when you make an explicit window rule for konsole but, it still doesnt respect the 'remember window size' option inside of konsole settings Git commit 38a3efaa979a28c055a8bd3da6b107d8a1fc3bb7 by Kurt Hindenburg, on behalf of Serge Roussak. Committed on 10/05/2024 at 16:29. Pushed by hindenburg into branch 'master'. Fixed the window geometry config file placement. Since the window geometry placement was moved to the state config files globally in KDE, exactly these files should be checked for such configuration data (instead of the main application config file). This issue may not been reproduced on the systems where the 'konsolerc' file remains filled by some old version of the konsole so that it holds the window geometry. But on the fresh install, the "Remember window size" option does nothing because the window geometry is being stored in the '.local/share/konsole/konsolestaterc', but is being looked up in the '.config/konsolerc' files. Related: bug 482954 M +1 -1 src/MainWindow.cpp https://invent.kde.org/utilities/konsole/-/commit/38a3efaa979a28c055a8bd3da6b107d8a1fc3bb7 This is likely fixed with 24.05 If you still having issues with 24.05 please file a new bug report |