Bug 442492

Summary: X11: Konsole resizes the window to default size when minimizing/restoring the window
Product: [Applications] konsole Reporter: Daniel Schulte <trilader+kdebugs>
Component: generalAssignee: Konsole Bugs <konsole-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: a.samirh78
Priority: NOR    
Version First Reported In: 21.08.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Daniel Schulte 2021-09-15 20:35:24 UTC 
SUMMARY
Minimizing/Restoring a Konsole window on X11 resets the window size to the initial size even though it shouldn't. In a previous version (whatever was before 2021.08.) this wasn't the case.

This doesn't happen if the option "Remember window size" is set, which I don't have as I like new windows to always have the same size.

STEPS TO REPRODUCE
1. Use Konsole on X11 with the "Remember window size" unchecked. Resize the window to a size different from the initial size set in the profile (in my case 80x24), e.g., 100x50.
2. Minimize the window (either via the task manager in the panel or the minimize button on the window).
3. Restore the window (via the task manager).

OBSERVED RESULT
The window gets restored and resizes to the default size. While doing that it shows the "Size: 80x25" resize notification.

EXPECTED RESULT
The window stays at the size it was before it was minimized. In this case 100x50.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION
Comment 1 Ahmad Samir 2021-09-15 20:46:57 UTC 

*** This bug has been marked as a duplicate of bug 442252 ***
Comment 2 Daniel Schulte 2021-09-15 20:53:58 UTC 
I'm not sure this really is a duplicate. I just closed all konsole processes and then deleted ~/.config/konsolerc and this issue still happens when I started konsole again.
Comment 3 Ahmad Samir 2021-09-15 20:56:55 UTC 
You're right, wrong bug number.

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