Bug 8199 - Client in GNOME can't start in in full screen
Summary: Client in GNOME can't start in in full screen
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Linux
: P2 Normal
Target Milestone: 4.19.0
Assignee: Pierre Ossman
URL:
Keywords: adaha_tester, relnotes
Depends on:
Blocks:
 
Reported: 2023-07-25 11:07 CEST by Samuel Mannehed
Modified: 2025-02-13 11:16 CET (History)
1 user (show)

See Also:
Acceptance Criteria:
MUST: * Display settings are respected on startup in all major Linux desktop environments SHOULD: * Display settings are respected on startup in the less common Linux desktop environments


Attachments

Description Samuel Mannehed cendio 2023-07-25 11:07:39 CEST
I can't start the ThinLinc client in full screen on all monitors in GNOME on Fedora. The client window starts in windowed mode on a single monitor anyway. It doesn't matter whether I use "selected monitors" or "full screen on all monitors".

When changing to full screen while connected, things work as expected.

Works fine on Windows 11 and macOS 13. Have not tested any other Desktop Environments or Linux flavors than GNOME on Fedora.

Tested with GNOME on Wayland and GNOME on Xorg. Same results. Used a fresh new user without any ~/.config/monitors.xml file.

Tested using clients of the following versions:

 * 4.12.1 (before the changes made as part of bug 7006)
 * 4.14.0
 * nightly build 3234

Tested against a nightly server (build 3333) and against a 4.14.0 server (tl.cendio.se).
Comment 1 Samuel Mannehed cendio 2023-08-09 13:18:55 CEST
This seems to apply to both "full screen on current monitor" and full screen on all monitors.

Reproduced on two different Fedora machines (37 and 38).
Comment 2 Samuel Mannehed cendio 2024-04-09 15:47:27 CEST
This is sporadic on my Fedora 39 machine. Out of 10 tries, it failed to start in full screen 5 times, and succeeded 5 times.

I used the same settings and procedure each time. I had the client set to use full screen on all monitors + send system keys. Furthermore, I ran GNOME on Wayland on the client machine. I used an empty workspace with two 1440p screens.

1. Alt+F2
2. run tlclient
3. click the password field, and type in password
4. press ENTER to connect
Comment 3 Pierre Ossman cendio 2024-04-11 14:57:40 CEST
Issue also seen with prototype Qt code, so definitely seems to be some GNOME issue.

Both the Qt code and the FLTK code works well with MATE on RHEL 9.
Comment 4 Samuel Mannehed cendio 2024-05-07 14:53:01 CEST
Upstream issue in tigervnc:

https://github.com/TigerVNC/tigervnc/issues/1752
Comment 5 Pierre Ossman cendio 2025-02-08 14:55:25 CET
Fixed upstream:

https://github.com/TigerVNC/tigervnc/pull/1909
Comment 6 Pierre Ossman cendio 2025-02-08 15:07:12 CET
The investigation of this bug did confirm that we still need to enable full screen after creating the window, not before. Mutter (GNOME's window manager) respects an initial _NET_WM_STATE_FULLSCREEN, but not an initial _NET_WM_FULLSCREEN_MONITORS.
Comment 9 Pierre Ossman cendio 2025-02-10 13:57:31 CET
Seems to work well under Fedora 41. Tested GNOME on Wayland, GNOME on X11, KDE on Wayland, and MATE on X11.

Only GNOME saw issues with ThinLinc 4.18.0, and mostly when using X11. With the nightly build, those issues are gone.
Comment 10 Adam Halim cendio 2025-02-13 11:12:58 CET
Tested client build 3809.

Started the client in fullscreen several times on the following platforms:

Fedora 41
=========
* KDE
* MATE
* GNOME X11
* GNOME Wayland
* Budgie
* Cinnamon
* i3
* LXDE
* XFCE

Ubuntu 24.04
============
* Ubuntu Desktop

Did not see any issues and fullscreen worked every time.
Comment 11 Adam Halim cendio 2025-02-13 11:16:32 CET
> MUST:
> 
>  ✅ Display settings are respected on startup in all major Linux desktop 
>     environments
> 
> SHOULD:
> 
>  ✅ Display settings are respected on startup in the less common Linux desktop 
>     environments
I did not look into the popularity of different desktop environments, but I tested almost all the readily available environments in Fedora 41 which should cover what most people are using.

Commits & release notes look good.

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