The bug is even worse if you just tap on the top bar, rather than drag. If you just tap, the window will un-maximize and also get trapped in the "snap to half of screen / tiling hint" thingy (see attached screenshot).
It gets worse though. While normally killing the foreground program works around the bug and makes the system usable again, if you kill the program while also trapped in the tiling thingy, it will also crash GNOME entirely.
Here's the stack-trace:
Oct 09 15:30:50 user-83BV gnome-shell[335512]: Error in size change accounting.
Oct 09 15:30:50 user-83BV gnome-shell[335512]: **
Oct 09 15:30:50 user-83BV gnome-shell[335512]: libmutter:ERROR:../src/core/window.c:5469:meta_window_get_workspaces: code should not be reached
Oct 09 15:30:50 user-83BV gnome-shell[335512]: Bail out! libmutter:ERROR:../src/core/window.c:5469:meta_window_get_workspaces: code should not be reached
Oct 09 15:30:50 user-83BV gnome-shell[335512]: GNOME Shell crashed with signal 6
Oct 09 15:30:50 user-83BV gnome-shell[335512]: == Stack trace for context 0x5570e87f79d0 ==
Oct 09 15:30:50 user-83BV gnome-shell[335512]: #0 5570e88bee48 i file:///<email address hidden>/src/extension/tilingWindowManager.js:99 (2597789ad9c0 @ 78)
Oct 09 15:30:50 user-83BV gnome-shell[335512]: #1 5570e88bed70 i file:///<email address hidden>/src/extension/tilingWindowManager.js:1291 (2597789b45b0 @ 95)
Oct 09 15:30:50 user-83BV gnome-shell[335512]: #2 5570e88bece8 i file:///<email address hidden>/src/extension/tilingWindowManager.js:431 (2597789addd0 @ 17)
Oct 09 15:30:50 user-83BV gnome-shell[335512]: #3 5570e88bec58 i resource:///org/gnome/shell/ui/init.js:21 (1a1d6a070ba0 @ 48)
The bug is even worse if you just tap on the top bar, rather than drag. If you just tap, the window will un-maximize and also get trapped in the "snap to half of screen / tiling hint" thingy (see attached screenshot).
It gets worse though. While normally killing the foreground program works around the bug and makes the system usable again, if you kill the program while also trapped in the tiling thingy, it will also crash GNOME entirely.
Here's the stack-trace:
Oct 09 15:30:50 user-83BV gnome-shell[ 335512] : Error in size change accounting. 335512] : ** 335512] : libmutter: ERROR:. ./src/core/ window. c:5469: meta_window_ get_workspaces: code should not be reached 335512] : Bail out! libmutter: ERROR:. ./src/core/ window. c:5469: meta_window_ get_workspaces: code should not be reached 335512] : GNOME Shell crashed with signal 6 335512] : == Stack trace for context 0x5570e87f79d0 == 335512] : #0 5570e88bee48 i file:///<email address hidden> /src/extension/ tilingWindowMan ager.js: 99 (2597789ad9c0 @ 78) 335512] : #1 5570e88bed70 i file:///<email address hidden> /src/extension/ tilingWindowMan ager.js: 1291 (2597789b45b0 @ 95) 335512] : #2 5570e88bece8 i file:///<email address hidden> /src/extension/ tilingWindowMan ager.js: 431 (2597789addd0 @ 17) 335512] : #3 5570e88bec58 i resource: ///org/ gnome/shell/ ui/init. js:21 (1a1d6a070ba0 @ 48)
Oct 09 15:30:50 user-83BV gnome-shell[
Oct 09 15:30:50 user-83BV gnome-shell[
Oct 09 15:30:50 user-83BV gnome-shell[
Oct 09 15:30:50 user-83BV gnome-shell[
Oct 09 15:30:50 user-83BV gnome-shell[
Oct 09 15:30:50 user-83BV gnome-shell[
Oct 09 15:30:50 user-83BV gnome-shell[
Oct 09 15:30:50 user-83BV gnome-shell[
Oct 09 15:30:50 user-83BV gnome-shell[
Here's the crash report: https:/ /errors. ubuntu. com/oops/ 8eae4f20- 66d9-11ee- 9abb-fa163ec44e cd