Hello, I’ve just installed openSUSE Tumbleweed and so far I’m enjoying it so much that I definetle want to overcome this problem which is harming me so heavily.
I use snap to keep up to date several softwares, like slack, skype, phpstorm, godot engine.
On openSUSE I’ve been facing this strange behaviour that when opening godot engine from app laucher it just fails to launch with no messages (the label on the bottom bar just disappers after some sseconds) and from command line it prints the following
No protocol specified
ERROR: initialize: X11 Display is not available
phpstorm seems not to be affected by this problem, while slack and skype also fail to start but with no messages at all (launching them from command line)
trying to nail down into it it seems that there are too many processes keeping X11 display busy (maybe it has n pipelins available… unfortunately this is kinda a new topic for me) and looking at the processes I have this output:
Just throwing out a highly speculative possibility since you didn’t post anything specific pointing to the following issue…
If you’re configured to use Wayland, you might want to re-configure to use xorg instead.
If an application tries to access your X server by some “external” method (even if the application is running on the same machine), I imagine the application needs to know how to access using a socket instead of an X server.
An common example of where this is documented is when you set up a VNC server (Remote Administration) on LEAP 15/TW.
There is a good chance Skype could be affected by this, but I wonder about Slack which AFAIK is a collection of web parts so I’d be surprised if affected…
I interpreted the error to mean that the application isn’t “talking” to the X11 server in a way both app and X11 both understand, that’s why I speculated that the API or sockets each assume should be using aren’t matching.
The easiest cause I could think of was as I described, but maybe there’s another possibility.
If communication is through a network socket (or other external means), besides the X server used for your local GUI, you may need to have a 2nd X server running to handle external connections. As I described in my earlier post, connections from another machine (like ssh -X) would absolutely require this, but an application installed on the same machine might or might not require a 2nd X server.
You can run a second X server, that’s one of the recommended options for Wayland users who don’t want to learn “native” ways to access.
Are you logged in differently at work?
Using your machine in a different way?
Although I would have expected a different error, it may again be relevant for how your problem apps are connecting (through an external connection or not)