Ubuntu
gnome-shell package

Toggle-maximize-vertically/horiz fully maximzes (REGRESSION)

Bug #1837974 reported by jimav
56
This bug affects 11 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Double-clicking a window title-bar now fully-maximizes the window, even though the action is set to "Toggle Maximize Vertically" or "Toggle Maximize Horizontally".

In other words, those options now behave just like "Toggle Maximize".

This problem started after I upgraded from Ubuntu 18.10 (gnome-shell 3.30?) to Ubuntu 19.04 (gnome-shell 3.32.1).

STEPS TO REPRODUCE:

1. Run gnome-tweaks
2. Click "Window Titlebars" in left menu panel
3. Set "Titlebar Actions ... Double-Click" to "Toggle Maximize Vertically"
4. Double-click a gnome-terminal titlebar

RESULTS: WIndow maximizes fully (fills entire screen)

EXPECTED RESULTS: Maximize in vertical direction only.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Uname: Linux 5.0.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 25 22:53:16 2019
DisplayManager: gdm3
InstallationDate: Installed on 2018-04-05 (477 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-07-26 (0 days ago)

Revision history for this message
jimav (james-avera) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Daniel van Vugt (vanvugt)
tags: added: eoan
Daniel van Vugt (vanvugt)
tags: removed: disco
Revision history for this message
Almir Campos (almircampos-e) wrote :

Any "guestimate" about the solution? Thanks.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sounds related to bug 1698083

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
Fred Drake (fdrake) wrote :

This isn't working in 20.04 either, so should remain open.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I suspect this will turn out to be a duplicate of bug 1698083, regardless of the clicking method employed.

tags: added: focal
removed: eoan
Changed in gnome-shell (Ubuntu):
status: Won't Fix → Confirmed
Revision history for this message
Fred Drake (fdrake) wrote :

For the record, I'm running Xorg.

Are there any diagnostics we can run to determine if these are the same?

This is a long-standing bug. While it may seem insignificant, it does impact daily workflow for those of us who find maximize-vertically to be useful.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This upstream bug:

  https://gitlab.gnome.org/GNOME/gtk/-/issues/539

mentions double clicking. And that bug is linked from bug 1698083. So I will generalize this into bug 1698083.

Revision history for this message
jimav (james-avera) wrote :

Something is strange here: That upstream bug is 5+ years old, yet this problem appeared in Ubuntu at most 3 years ago (vertical resize worked in Ubuntu 18.10)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes, regressions can occur multiple times (sadly) and/or can be observed in different circumstances with multiple different root causes.

I agree we're now talking about a regression that occurred after Ubuntu 18.04 but it's not worth starting a new upstream bug when they already know about it, and continued to acknowledge it in the past year.

Revision history for this message
Walter Daems (daems) wrote :

Still not solved in Ubuntu 20.10.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.