Bug 1263951 - Konsole does not retain the original size after restoring it from maximised view
Summary: Konsole does not retain the original size after restoring it from maximised view
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: konsole5
Version: 24
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-17 07:38 UTC by Panos Kavalagios
Modified: 2016-07-26 12:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-26 12:56:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 366127 0 None None None 2016-07-26 12:56:36 UTC

Description Panos Kavalagios 2015-09-17 07:38:31 UTC
Description of problem: If you maximise a konsole having a default 80 columns and 100 rows, if you restore it, it returns to 80x40 instead of the original 80x100.


Version-Release number of selected component (if applicable): konsole5-15.04.3-2.fc22.1.x86_64


How reproducible: Maximise a konsole and then restore it to the original size.


Steps to Reproduce:
1. Start konsole
2. Either double click the title or click on the Maximise button
3. Double click the title or click on the Maximise button again

Actual results: The konsole returns back to a geometry that has fewer rows.


Expected results: The konsole should have returned to the original geometry.


Additional info: If you resize manually the konsole and repeat the scenario, the issue is not reproduced. The konsole returns back to its original geometry. Only the first time is reproduced after logging in to KDE. It is an irritating old issue.

Comment 1 Fedora End Of Life 2016-07-19 17:55:10 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 2 Panos Kavalagios 2016-07-20 10:09:33 UTC
It still occurs on Fedora 24 too.

Comment 3 Rex Dieter 2016-07-20 11:10:38 UTC
I cannot reproduce this.

Either way, I'd suggest you report this upstream @ bugs.kde.org  (*if* there is some verifiable problem, we downstream in fedora are generally not in a position to fix it ourselves).

Comment 4 Panos Kavalagios 2016-07-25 15:39:35 UTC
The issue is also reproduced on a clean user by removing any specific environment (rm -rf $HOME/.[a-z]*). The exact scenario:

1. Start konsole
2. Resize konsole's height to reach the taskbar
3. Exit konsole
4. Start konsole with the new height that takes not half of the screen but up to taskbar
5. Either double click the title or click on the Maximise button
6. Double click the title or click on the Maximise button again
7. The konsole returns to the half of the screen size and not to the previous user defined height.

Are you using KDE or other desktop environment? The konsole was started in KDE. We may report it upstream if you believe it is not related to any packaging or Fedora specific configuration.

Comment 5 Rex Dieter 2016-07-25 15:53:08 UTC
I'm using plasma, and I don't believe it's related to any fedora-specific configuration, yes.

Comment 6 Panos Kavalagios 2016-07-26 11:16:06 UTC
I have also reproduced the issue on a Kubuntu 16.04 VM, so we can safely assume it is not specific to Fedora. Reported upstream as well:

https://bugs.kde.org/show_bug.cgi?id=366127

Comment 7 Rex Dieter 2016-07-26 12:56:36 UTC
Thanks, let's continue tracking there


Note You need to log in before you can comment on or make changes to this bug.