09-23-2018, 05:23 PM
I've noted before that I had some trouble with ubuntu systems throwing up strange errors unable to open Displays causing failure of our test projects I thought it was limited to Ubuntu, but today I had it on a Tinkerboard system which is Debian, it did however throw a much more useful No Protocol supplied, error, which after a bit of googling resulted in some answers.
I can't honestly explain much about how any flavour of Linux works, its a total mystery to me and the way it seems to over protect things you want to directly access is frustrating, but it does seem that some of our issues are related to lock of display system by the OS.
If you don't have root access we know some things get hard to use, like keys and mouse, but it seems also the screen....
One solution is to enter
xhost +
on a terminal, and then you can finally open the screens.
But then of course you have all kinds of other issues
I can't honestly explain much about how any flavour of Linux works, its a total mystery to me and the way it seems to over protect things you want to directly access is frustrating, but it does seem that some of our issues are related to lock of display system by the OS.
If you don't have root access we know some things get hard to use, like keys and mouse, but it seems also the screen....
One solution is to enter
xhost +
on a terminal, and then you can finally open the screens.
But then of course you have all kinds of other issues
Brian Beuken
Lecturer in Game Programming at Breda University of Applied Sciences.
Author of The Fundamentals of C/C++ Game Programming: Using Target-based Development on SBC's
Lecturer in Game Programming at Breda University of Applied Sciences.
Author of The Fundamentals of C/C++ Game Programming: Using Target-based Development on SBC's