-
-
Notifications
You must be signed in to change notification settings - Fork 178
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
Xpra opens windows as tabs #3723
Comments
I'm going to guess that this is Ventura feature since I have never seen this before. I've just synced our MacOS build environment with https://github.com/jralls/gtk-osx-build yesterday and there are fixes to GTK, specifically for Ventura - perhaps this will fix things. |
You are right. Since I don't have access to a Windows machine or Linux Desktop, to rule out that it's a macOS thing, I had run Xpra client on the Linux server itself which I was accessing through Xpra client (different session) on my macOS, but observed that the tabbing also occurs there! I'd checked the Xpra code and found that while I don't find any code for the tabbing mechanism, there's the very old thread #539 that discusses such mechanism. Anyways, I just checked on another machine with macOS Monterey (12.5) and apps are not shown as tabs in form of a "merged" window, anymore. |
@nimamox there are updated builds in the MacOS beta area, try 5.0-r32739 or later to get the latest GTK version - which may fix your problem. You may first need to remove the quarantine to run it until we can figure out the sudo xattr -rd com.apple.quarantine /Applications/Xpra.app Just be aware that this is a beta release and there are some know issues with it (ie: #3769) so YMMV. |
@totaam I was in fact regularly checking your macOS beta releases. I even tried to build Xpra from scratch but I failed. On my server Ubuntu 22.04:
On my client macOS Ventura 13.2:
Actually, to be thorough, since I run my applications inside docker containers, I modify
and add the following line to
Then, on the server, I run the command below:
and run my docker container (with some redaction):
Then, on macOS:
While both my Monterey and Ventura systems run the same Xpra v5.0-r32739, the issue is still only with Ventura: In the PyQt app I'm writing, I realized that if I set the window size by issuing |
Why not just As for this bug, this is a MacOS feature, try: System Preferences -> Mission Control -> Then untick "Group windows by application". More details here: Use Stage Manager to organize apps and windows on Mac Alternatively, you could start an xpra session for each application which would prevent MacOS from seeing these applications as belonging to the same process and therefore ungroup them. |
Thanks for the tip about |
Describe the bug
Not sure if it's a bug or not. But I've searched a lot and I haven't seen anyone (or the documentation) mentioning this. I use Xpra 4.4 on a remote headless Linux server and my local macOS laptop to have the GUIs of the apps running on Docker containers of the Linux server shown on my macOS laptop, even with streaming audio and OpenGL. Everything works perfectly, but there is an issue that's been bothering me a lot. I run Xpra in the seamless mode, and all windows are shown as tabs of a single window on macOS. Then, I need to detach the tab into a new window manually:
If it's not clear, what I want is to have each window opened as a separate window, not a new tab. I already have some application running, and I develop some code that I need to respawn regularly, which would be frustrating as each time I have to switch to that tab (for that window) which also mistakenly inherits the size of the previous window (tab) that is already open.
As a side, I have found that the binaries released for macOS can not be run due to an issue with the
libcrypto
shipped with Xpra. FYI, I resolve this issue by replacing those files with the libcrypto and libssl installed by Homebrew. So, at least this one is a bug!To Reproduce
Steps to reproduce the behavior:
xpra start --daemon=yes :9898
xpra attach ssh:username@ip:9898 --encoding=h264
System Information (please complete the following information):
The text was updated successfully, but these errors were encountered: