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

QA: Two screens, wrong screen used for limits of positioning context menus #78

sunweaver opened this issue Feb 20, 2016 · 1 comment


None yet
1 participant
Copy link

commented Feb 20, 2016

With the new RRXinerama code, we should check, if this X2Go issue has been solved.
Submitted here:

This bug concerns the placement of context menus in a two screen setup.
On my client I have two screens. One in landscape mode from 0,0 to
1920,1080 and to its right a second screen in portrait mode, from 1920,0
to 3120,1600. I run an x2go session, the session type is single application
(terminal). I fullscreen my application window, either on the left or on
the right screen. I then open a context menu while my mouse cursor is in
the bottom half or right half of the application window.

Everything works fine with the application positioned on the right hand
screen. It is correctly determined that the context menus would not fit
into the remaining space if they would start where the mouse cursor is, so
they are repositioned in a way that I can see the entire menu.

But if the application is on my left hand screen the context menus will
always start (their top left corner) where my mouse cursor is, therefore
spilling outside my visible monitor area to the bottom, or overlapping into my
second screen. Expected behaviour: context menus to stay within my
screen, just as they do for all other non-x2go applications.


This comment has been minimized.

Copy link
Member Author

commented Feb 5, 2017

This issue has been resolved by the new Xinerama implementation. Reporting back down stream to X2Go and closing this issue here, now.

@sunweaver sunweaver closed this Feb 5, 2017

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.