Tk Source Code

View Ticket
Login
Ticket UUID: 6fa2369ec654ec009b4dd061abb75aa91c307092
Title: X11: under Mutter wm geometry of a zoomed toplevel is offset by the invisible borders
Type: Bug Version: 8.6.18, 9.0.5, 9.1.1
Submitter: serhiy.storchaka Created on: 2026-11-05 15:29:59
Subsystem: 67. Unix Window Operations Assigned To: nobody
Priority: 5 Medium Severity: Minor
Status: Closed Last Modified: 2026-11-06 15:25:02
Resolution: Fixed Closed By: nemethi
    Closed on: 2026-11-06 15:25:02
Description:

Mutter puts invisible borders (for resizing and the shadow) around the frame of a normal window and reports them in _GTK_FRAME_EXTENTS on the frame window, here 14, 14, 12 and 17 pixels. Tk does not take them into account. After zooming and restoring a window placed at +303+210, wm geometry reports either the zoomed window at +-14+-12 instead of +0+0, or the restored one at +289+198; which of the two varies from run to run. Tests wm-geometry-2.3 and 2.4 fail under Mutter for this reason.

User Comments: nemethi (claiming to be Csaba Nemethi) added on 2026-11-06 15:25:02:

Serhiy, many thanks! Merged into main, core-9-0-branch, and core-8-6-branch by commits [6790de40], [9b7360b5], and [ce2acb17].


serhiy.storchaka added on 2026-11-05 17:03:59:

Proposed fix in branch x11-gtk-frame-extents: Tk reads _GTK_FRAME_EXTENTS of the frame window and leaves the invisible borders out of the position and size of the frame. No new test: wm-geometry-2.3 and 2.4 cover it when run under Mutter.


serhiy.storchaka added on 2026-11-05 16:46:39:

The same offset appears after leaving fullscreen and after deiconifying a withdrawn window: a window placed at +303+210 is reported at +289+198 after leaving fullscreen, and a window moved to +100+100 while withdrawn is shown at +86+88.