Connection does not start in full screen despite options (Ubuntu 23)

ThinLinc
, ,
1

I have Thinlinc Client installed in my Ubuntu 23 (64 bits) laptop. I can successfully log into relevant servers via Thinlinc, but every new connection starts in windowed mode regardless of the Thinlinc Client options showing that I selected “Full Screen in All Monitors”. After the connection is established, if I manually hit F8 → Full Screen, the client correctly goes to full screen. It’s just the start of the connection that is not respecting the “Full Screen in All Monitors” option.

Is there a way to solve or work around that? For example setting something via file configurations.

Thanks!

2

Hi @Lucy_Z,

That seems strange. Do you experience the same behaviour if you go into the client settings immediately before connecting, and select “Full screen on all monitors”?

There is a configuration file for the ThinLinc client at ~/.thinlinc/tlclient.conf. If you look in there prior to starting the client, you should find three parameters:

These are the settings which the client will use on startup, so you could check that these are set to the appropriate values as well. Let us know what you find.

3

Hi @aaron, thanks for your reply! So, actually when I check the client settings immediately before connecting, the option “Full scree on all monitors” is already selected. Still, the connections starts in windowed mode (accordingly, the menu that pops up when I press F8 shows “Full Screen” unselected").

Regarding the 3 configuration parameters you mention from the tlclient.conf file, their values are, respectively, “1”, “all” and “1”.

4

Very strange. Could you please start the client from the command line with the “-d5” switch (see Client command line usage — ThinLinc Administrator's Guide) and check the resulting ~/.thinlinc/tlclient.log file? This should tell you explicitly which configuration parameters are being read. If you’re running multiple clients with different configurations, I’m just wondering if it might be the wrong one being read somehow.

Feel free to post the content of the log file here for us to check too if you like, just make sure to remove any sensitive information first.

5

This sounds like this bug in GNOME:

Fortunately, we’ve been able to identify a workaround that will be included in the upcoming release. There is a beta out, so please test that and see if it works better for you.

6

@aaron I checked the log, and the parameter configurations being read are correct:

2025-06-30T14:55:49: VNC command: /opt/thinlinc/lib/tlclient/vncviewer -FullScreen=1 -FullScreenMode=all -FullScreenSelectedMonitors=1 -FullscreenSystemKeys=1 -emulateMiddleButton=0 -FullColour=1 -LowColourLevel=2 -AutoSelect=1 -CustomCompressLevel=0 -CompressLevel=2 -QualityLevel=8 -MenuKey=Pause -PasswordFile=/tmp/vncviewer076UbL -ReconnectOnError=0 -Shared=1 -_tl_SSHCompression=0 -_tl_SSHPortSelection=2 -_tl_SSHPortArbitrary=22 -_tl_ReconnectPolicy=single-disconnected -_tl_StartProgramEnabled=0 “-_tl_StartProgramCommand=tl-single-app firefox” -_tl_UpdateEnabled=1 -_tl_ShadowingEnabled=1 -_tl_SoundRedirection=1 -_tl_FeatureLocalSound -_tl_FeatureLocalSoundAdvanced -_tl_SerialportRedirection=0 -_tl_FeatureSerialRedirection -_tl_DriveRedirection=0 -_tl_FeatureLocalDrives -_tl_PrinterRedirection=1 -_tl_FeatureLocalPrinter -_tl_SmartcardRedirection=1 -_tl_FeatureLocalSmartcard -_tl_AuthenticationMethod=password -_tl_FeatureSmartcardAuth -geometry=+50+100 127.0.0.1::38711

So, it does indeed look like the issue linked to by @CendioOssman .

7

Great! As mentioned, if you’d like to give the beta a spin and see if it fixes the problem for you, you can download it here:

Don’t forget to update once the final release is out, though :slight_smile:

1 Like
8

@aaron Yep, just to report back: the beta solves the issue for me. Thanks!

3 Likes