In the past I have been able to run an xlib-based program from a virtual console (assuming I have a valid X session on display :0.0) with a simple command such as: $ DISPLAY=:0.0 xterm After upgrading to gdm3, I am unable to do this because gdm3 apparently sets an XAUTHORITY var to a file under /var/run/gdm3/... Which is fine -- I just need to set XAUTHORITY to the proper value when I launch an app from a virtual console. The problem is that the error message I got did not give any indication that the auth token was the problem. It would be nice if the error message was a bit more helpful than this: $ DISPLAY=:0.0 xrandr No protocol specified Can't open display: :0.0
*** This bug has been marked as a duplicate of bug 25722 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.