Unreliable full screen on macOS

[RobyB]

Describe the bug
I am using latest beta on OsX Sequoia 15.2 on an external monitor.
I start vnc viewer and make it full screen on my external monitor.
Everything seems to work normal, but after a while i leave the screen unattended (without typing anyting in it) it goes completely black and there is no way to make it normal again with mouse or switching between windows.
The only way i found to recover frm this situation is the following.
I press F8-f (to make it go out of full screen).
At this point it works again, but the window is maximized and not full screen (On OsX it means that if i type command+tab i switch between apple programs and not between tigervnc windows as usual).
If i press F8-f again the window exits full screen and shrinks (as it should have done with the first time i pressed F8-f).
Then if i press F8-f a third time it goes back full screen until the behaviour repeats.

Nothing that makes it unusable, but with this bug i prefer to stick to stable version, hoping this will be fixed before release.

Client (please complete the following information):

• OS: OsX Sequoia 15.2 running on a macbookpro Apple M1 pro
• VNC client: TigerVnc
• VNC client version:1.15.0 beta
• Client downloaded from: the link provided on email and github

[RobyB]

After some more investigation i found that:
If i switch from TigerVnc app (full screen) to another mac app the behaviour i explained is triggered.
So it is not due to timeout or screensaver or screen blanking (that are both turned off on my linux machine).
The strange thing is that while i use mac apps on my laptop screen i see the TigerVnc screen correctly on my monitor, but as soon as i switch to it (with mouse or shortcut) i blanks. and the only way to recover is what i described before.
If i switch back to mac apps everything reappears as it would behave normally, but as soon as i switch to TigerVnc everything goes black again.

[CendioOssman]

Thank you for your report.

Just to be clear, you do not see this issue with TigerVNC 1.14.1?

[RobyB]

Absolutely not.

[CendioOssman]

I've been able to reproduce a lot of weird behaviour with full screen on macOS. Unfortunately, this seems to be entirely an issue in FLTK (fltk/fltk#1192).

I would suspect the difference between TigerVNC 1.14.1 and 1.15.0 beta is that we got a new version of FLTK in the build system between those releases. @bphinz, could you check if FLTK got upgraded to 1.3.10 after 1.14.1?

We can't work around this in TigerVNC, so we'll need to wait for a fix in FLTK. We can probably patch our binaries, though. @bphinz, do you think you can revert the commit referenced in the FLTK issue in your build system?

[bphinz]

FLTK definitely did not get upgraded but I can try reverting that commit and rebuilding Sent from Gmail Mobile

…

On Wed, Jan 22, 2025 at 7:52 AM Pierre Ossman (ThinLinc team) < ***@***.***> wrote: I've been able to reproduce a lot of weird behaviour with full screen on macOS. Unfortunately, this seems to be entirely an issue in FLTK ( fltk/fltk#1192 <fltk/fltk#1192>). I would suspect the difference between TigerVNC 1.14.1 and 1.15.0 beta is that we got a new version of FLTK in the build system between those releases. @bphinz <https://github.com/bphinz>, could you check if FLTK got upgraded to 1.3.10 after 1.14.1? We can't work around this in TigerVNC, so we'll need to wait for a fix in FLTK. We can probably patch our binaries, though. @bphinz <https://github.com/bphinz>, do you think you can revert the commit referenced in the FLTK issue in your build system? — Reply to this email directly, view it on GitHub <#1900 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB45M3MOXLMN5IYQJWUMRX32L6IARAVCNFSM6AAAAABVSZONH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBXGE3DSNBSGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[RobyB]

If you provide me with a new build i could test it asap.

[bphinz]

I’ll be making a new build tonight and will post it here for testing Sent from Gmail Mobile

…

On Thu, Jan 23, 2025 at 9:27 AM Roberto Beccherle ***@***.***> wrote: If you provide me with a new build i could test it asap. — Reply to this email directly, view it on GitHub <#1900 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB45M3MWEQ7HYBRKTJE7ZRD2MD33TAVCNFSM6AAAAABVSZONH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBZHE2TAMZTGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[bphinz]

Sorry, I had not gotten the chance to patch & rebuild but I see that FLTK has responded with a proposed fix. Have been able to verify it yet?

[CendioOssman]

After a few rounds with FLTK, I think they've squashed all the new bugs. So you could try their latest code instead.

They also said they'd release FLTK 1.3.11 soon, which should have what we need.