Bug 1744279 - shrinking window when maximizing then restoring gnome terminal
Summary: shrinking window when maximizing then restoring gnome terminal
Keywords:
Status: CLOSED DUPLICATE of bug 1411876
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-21 17:55 UTC by Eric Blake
Modified: 2019-09-17 10:36 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-09-17 10:36:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
demo of the bug in action (584.45 KB, video/webm)
2019-08-21 17:55 UTC, Eric Blake
no flags Details

Description Eric Blake 2019-08-21 17:55:55 UTC
Created attachment 1606683 [details]
demo of the bug in action

Description of problem:
I default to opening a gnome terminal window at 80x24.  But when I maximize a terminal (sometimes by accident when double- instead of single-clicking on the top bar of the terminal window), restoring the window back to its original dimensions loses a row and column.  This only started happening when I upgraded to Fedora 30 (it did not happen on F29).

Version-Release number of selected component (if applicable):
gnome-terminal-3.32.2-2.fc30.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Open a terminal window, and observe its dimensions (I did this by clicking the mouse on the bottom right corner, but not dragging)
2. Maximize the window by double-clicking the top bar
3. Restore the window by double-clicking the top bar
4. Check the size again

Actual results:
Each cycle reduces the size of the window

Expected results:
The restored size should match the original size


Additional info:

Comment 1 Egmont Koblinger 2019-08-21 19:11:55 UTC
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/129

Comment 2 Anoop C S 2019-09-17 06:31:53 UTC
Can this be considered as a duplicate of bug #1411876?

Comment 3 Eric Blake 2019-09-17 10:36:00 UTC

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


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