Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable local screensaver when x2go session is in fullscreen mode #95

sunweaver opened this Issue Feb 29, 2016 · 3 comments


None yet
2 participants
Copy link

sunweaver commented Feb 29, 2016

From X2Go BTS:

Package: nxproxy
Severity: serious

I noticed that the when nxproxy is in fullscreen mode, it (by design)
captures all keyboard strokes. This is in general great because this
way all keyboard shortcuts on the remote work.

However, the local screen saver might still kick in and require a
password. Because the nxproxy captures all input, a less carefull user
might enter his local password into the current application that is
running in the x2go session. When the remote application happens to be
a chat application, entering your password might have serious security

I think a fullscreen nxproxy is a good reason to inhibit the local screensaver.

@sunweaver sunweaver added this to the 3.6.0.x milestone Feb 29, 2016


This comment has been minimized.

Copy link
Member Author

sunweaver commented Mar 15, 2016

I just found that the screensaver gets disabled when nxagent is launched in fullscreen mode:

However, it may well be that this actually fails.

Furthermore, it is well possible, that the re-enable/re-disable mechanism is not working / not implemented, but should be.

@sunweaver sunweaver modified the milestones:, Mar 2, 2017


This comment has been minimized.

Copy link

uli42 commented Aug 8, 2017

Most aspects of screensaving seem to be broken, see also #263 and #80


This comment has been minimized.

Copy link

uli42 commented Jun 5, 2018

I have a fullscreen session. Screenblanking on the native display is disabled (xset q reports a timeout of 0. Activating the screen blanker there by calling xset s 10 results in a blank screen after 10s, and pressing any key unblanks the screen again. I am wondering how the original problem you describe might happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.