Thunderbird does not remember its window position
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
People
(Reporter: wolfiR, Unassigned)
References
Details
Comment 1•16 years ago
|
||
Comment 2•15 years ago
|
||
| Reporter | ||
Comment 3•15 years ago
|
||
Comment 6•12 years ago
|
||
Comment 8•10 years ago
|
||
Comment 10•10 years ago
|
||
Comment 11•9 years ago
|
||
Comment 12•9 years ago
|
||
Comment 13•7 years ago
|
||
@atmarsden96 Seeing this issue as well on Windows 10 with Thunderbird 60.5.0 (32-bit).
In xulstore.json there are "screenX" and "screenY" values. It seem that if screenX is set to a negative value, i.e. the Thunderbird window is off the left-hand side of the screen, then screenX is set to "0" on restarting.
Snapping the window to the left-hand edge appears to have a screenX value of "-6" with my setup, so after doing this and restarting Thunderbird screenX is reset to 0 which results in the Thunderbird window being a bit away from the left-edge of the screen.
You can observe this happening by keeping open xulstore,json and watching the values change as Thunderbird restarted.
Comment 14•7 years ago
|
||
Updated•3 years ago
|
Comment 15•7 months ago
|
||
Does this still reproduce?
Comment 16•7 months ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #15)
Does this still reproduce?
Yes, at least for me.
(now currently running TB 140.7.0esr)
Comment 17•7 months ago
|
||
Running openSUSE Linux Tumbleweed with Wayland, and Gnome 49.
Thunderbird is v147.0.
Thunderbird always opens in the middle of the screen, but doesn't remember the last screen position upon restart.
It remembers the size of the window though.
Comment 18•7 months ago
|
||
Yes, v146 on Fedora 43 X11. Always starts in top left corner, hardcoded near (100, 100).
(Note: apps on Wayland cannot set window position, a new security req. The window manager should/is handling it in that case.)
Comment 19•15 days ago
|
||
Still reproducible in Thunderbird 154.0 (Flathub, org.mozilla.thunderbird) on Linux Mint 22.2,
Cinnamon 6.6.4 / Muffin 6.6.1, X11, GTK 3.24.41, single 3440x1440 monitor.
Measurements that may narrow this down: the position IS persisted correctly, it is the
restore that never reaches the window manager, because the main window ships no position
hint at all.
-
Saving works. After dragging the main window flush to the left edge, xulstore.json holds:
"messengerWindow": {"screenX":"0","screenY":"0","width":"1720","height":"1372","sizemode":"normal"}
which matches xwininfo (frame at 0,0).
-
Restore does not. Closing and relaunching with that exact xulstore always yields
absolute frame x=50, regardless of the stored value. Overwriting screenX/screenY with
400/300 while Thunderbird was closed changed nothing: the window still came up at x=50,
with y stepping through a cascade (28, 78, ...) on successive launches. Width and height
are restored exactly, every time. -
The main window sets no position hint:
$ xprop -id <messengerWindow> WM_NORMAL_HINTS
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified minimum size: 95 by 95
program specified maximum size: 16384 by 16356
program specified base size: 95 by 95
window gravity: NorthWestNo "program specified location" / "user specified location" line, i.e. neither PPosition
nor USPosition. Mutter/Muffin only skips its own placement for windows that set one of
those flags, so every launch gets auto-placed by the cascade and the restored coordinates
are discarded. Checking every other client in the same session (Brave, Teams, PhpStorm,
Bitwarden, Double Commander) shows they all set the flag - and they all restore their
position correctly under the same window manager. This lines up with the earlier comment
in this bug quoting the window manager log line "PLACEMENT: Not placing window with
PPosition or USPosition set" for the application that worked.
Separate but related, and possibly why some reporters describe the window "walking" across
the screen over many restarts: with the default mail.tabs.drawInTitlebar=true the persisted
screenX/screenY include the invisible GTK CSD shadow margins. _GTK_FRAME_EXTENTS on this
system is 20,20,20,20 for the unfocused window and 26,26,23,29 for the focused one, so the
value written on shutdown depends on focus state, and a window parked at x=0 is stored as
screenX=-20. Setting mail.tabs.drawInTitlebar=false makes _NET_FRAME_EXTENTS take over and
the stored numbers become stable - but the position is still ignored on restore, per point 3.
Comment 20•14 days ago
|
||
Is it still the case that Firefox does not have this problem?
Description
•