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

X windows not opening after upgrading to XQuartz 2.8.0_beta3 #66

Closed
gianlisi opened this issue Feb 8, 2021 · 13 comments
Closed

X windows not opening after upgrading to XQuartz 2.8.0_beta3 #66

gianlisi opened this issue Feb 8, 2021 · 13 comments

Comments

@gianlisi
Copy link

gianlisi commented Feb 8, 2021

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

@gianlisi
Copy link
Author

gianlisi commented Feb 8, 2021

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

@alaudrain
Copy link

Hello,
I would like to add that I also see this issue on macOS 10.14.6 (Mojave).

export DISPLAY=:0.0

indeed solves the issue (by default it was set to a similar value as previously reported).

Thanks for the hint!

@mischievous
Copy link

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

@steventgk
Copy link

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!

@VictorPoreeFr
Copy link

Does XQuartz keep coming back for you too?
In my case (and few colleagues), we had to completely clear the XQuartz installation and re-install de 2.7 latest version. Then using the export DISPLAY=:0.0 command we can get the terminal to open XQuartz without to much issues (at least in my case, some colleague still experience issues). However it does not solve the problem for other apps (in our case FullProf4MAc) which won't even start. XQuartz always come back after quitting and only way to stop it is to log out or restart.
Some colleagues tried to re-install their MacOS or to go back to the previous back-up of their computer but without success.

@gianlisi
Copy link
Author

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")

@odinsbane
Copy link

This bug affects me too. Using export DISPLAY=:0.0 works. Also, starting an xterm from xquarts works, but that seems to be because the DISPLAY value is set already.

If I don't set the DISPLAY value then ssh -v -X myserver.x.y.z stalls at,

debug2: client_x11_get_proto: /opt/X11/bin/xauth -f /var/folders/wr/mh...

(I've truncate the line with the ellipses.)

@jeremyhu
Copy link
Member

This is probably #52.

@mischievous
Copy link

Its not #52. I rebooted my computer a few times. No x windows would open

@odinsbane
Copy link

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

@VictorPoreeFr
Copy link

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.

@jeremyhu
Copy link
Member

@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.

@handsomehu0627
Copy link

handsomehu0627 commented Nov 17, 2023

I have the same problem and I temporarily fixed it.
It is caused by processes communication issues, the sumo-gui process and the netedit process are depend on xquartz to visualize. But they do not find the xquartz process. This may be the environment variable problems or parameter problems.
So, solution for this is:

  1. use command line xquartz to explicitly open the xquartz process(program)
  2. use command line sumo-gui or netedit to open the corresponding app you want, this time they'll be able to find the quartz process which they depend on. It is also viable to click the icon to start the sumo-gui and netedit .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants