-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
X windows not opening after upgrading to XQuartz 2.8.0_beta3 #66
Comments
Update: export DISPLAY=:0.0 solves the issue (but this is a hack). When opening the terminal, the value of DISPLAY is set to /private/tmp/com.apple.launchd.xnmyJRQjmT/org.xquartz:0 |
Hello,
indeed solves the issue (by default it was set to a similar value as previously reported). Thanks for the hint! |
I am on 10.15.7 the newest update also broke my remote displays. I have gone back to the 2.7.11. The entire idea hear is the DISPLAY need to match what the SSH session is using not just :0.0 |
I also had to revert back to 2.7.11 due to pgplot windows not opening in 2.8. Using DISPLAY=:0.0 did not provide a solution. Many thanks to all those maintaining this package! |
Does XQuartz keep coming back for you too? |
Xquartz keeps restarting after downgrading to 2.7 for me too. The "export DISPLAY=:0.0" works for me with XQuartz 2.7 (I can see xeyes and xclock, neither of the shows up when DISPLAY is set to a path similar to "/private/tmp/com.apple.launchd.cPtkoJjCQK/org.xquartz:0") |
This bug affects me too. Using If I don't set the DISPLAY value then ssh -v -X myserver.x.y.z stalls at,
(I've truncate the line with the ellipses.) |
This is probably #52. |
Its not #52. I rebooted my computer a few times. No x windows would open |
Logging out and logging back in worked. It even solved a different artifact in my x-windows was having. I would say the title of this bug is easier to understand than #52 |
I completely deleted Xquartz, re-installed my OS, installed Xquartz 2.7, rebooted the computer. It did not completely solve the problem, I can use the terminal to call XQuartz but I still have 3rd party apps crashing because they cannot find xquartz. |
@VictorPoreeFr Please install 2.8.0_rc4 and file a new ticket if you have issues. Folks usually don't check closed tickets for comments. Thanks. |
I have the same problem and I temporarily fixed it.
|
Hi,
first of all, thank you for your work in maintaining Xquartz. I would like to report a possible bug.
I seem to have lost the ability to open any X window after I upgraded to XQuartz 2.8.0_beta3, as suggested by the prompt this morning. That includes xclock and any X11 application forwarded through ssh. Uninstalling Xquartz following the FAQ instructions and reinstalling version 2.7.11 does not fix the issue.
I am on Mac OS Big Sur 11.2 (11.1 seems to have the same issue).
Any help in troubleshooting would be greatly appreciated.
Best
Gianluca
The text was updated successfully, but these errors were encountered: