-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
unable to leave fullscreen mode with CTRL+ALT+ENTER - after a while... #9640
Comments
well, that sounds like a possible window manager issue. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Hi @akallabeth
xfreerdp (as mentioned earlier) is RDPing with /multimon so all "host" screens used to control my windows PC. It works great, but I think since I upgraded to 23.04 (half a year ago) this problem of not being able to leave remote session is kind of annoying. It reproduces quite often, so if I need to collect logs please tell me (and please also tell me what to collect exactly :)) |
@basprins ok, so you are using the repo package I assume? |
This comment was marked as off-topic.
This comment was marked as off-topic.
Apologies for the radio silence... I installed:
Any consecutive CTRL+ALT+ENTER "nothing" happens. I see a brief screen refresh over all three physical screens, but the key event is either ignored by xfreerdp, or it never gets delivered. The only way to exit full screen is by terminating the RDP session on client side (windows => power => disconnect). |
I see the same issue on Fedora 39 with 2.11.4. I started in window mode then CTRL+ALT+Enter goes into fullscreen mode. I can never leave fullscreen mode. This sounds similar to @basprins, but I didn't start in fullscreen mode. The remote system is Ubuntu 22.04 using the built-in GNOME display sharing feature. I don't have a disconnect option on GNOME, so I have no way to get out of session other than dropping to a VT and killing |
To add another data point, I just tried to floatbar option since that should give me a way to disconnect. The floatbar does indeed only show up by default in fullscreen mode when I add |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Reporting the same issue as @basprins on Arch Linux in gnome. 6.7.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 23 Feb 2024 16:31:48 +0000 x86_64 GNU/Linux Using CTRL-ALT-ENTER:
|
Same problem. After a while i can't exit fullscreen. Xfreerdp with Ubuntu 22.04. |
I use xfreerdp to RDP into a windows laptop (from ubuntu 23.04 host). I run xfreerdp in full screen mode, taking control of all my displays. I use CTRL+ALT+ENTER to leave full screen mode, and CTRL+ALT+ENTER again to go back to full screen mode.
This sometimes work, but often xfreerdp refuses to leave full screen mode when I hit CTRL+ALT+ENTER. I can see some visual feedback (a quick blink on all screens) where I think xfreerdp tries to leave full screen mode, but fails.
I am using latest versions of x
I start xfreerdp as follows
xfreerdp /multimon /d:*** /u:*** /p:*** /v:***
When the RDP session is freshly started, CTRL+ALT+ENTER always works. Always. But when I am in the RDP session for a while, it pretty much never works. The only way to leave full screen mode is to choose Windows->Power->Disconnect, this closes the RDP session client side and then I can reopen it again from ubuntu, to repeat the cycle.
Maybe it has something to do with power management or auto lock settings (which I can't control on the guest OS, company policies).
Does this sound familiar to anyone? Is there something I can do to prevent this? Is there more information I can share I don't know about? xfreerdp logging maybe (not sure if that exists and if so, where I can find them). Or wayland loggings (I don't really know what I am saying now ;-)).
The text was updated successfully, but these errors were encountered: