06-07-2019, 08:42 PM
(This post was last modified: 06-09-2019, 10:51 AM by Brian Beuken.)
This is an issue I had with Ubuntu 18.04 running on an Nvidia Nano but I have noted a couple of other Ubuntu systems would fail to run demos so this may be the cause for them too.
Basically if you can't get an X11 window to open from your VisualStudio deployed app, you have to make sure that you are indeed using the correct log in name for your SSH connection and the Target. This is very unlikely to be different.
The issue however seems to relate to autologin on Ubuntu if you are signing in manually, even as your expected user name, you can transfer build and run, but your builds will fail whenever they try to get an X11 display to set up graphics.
I figured it had to be something to do with access rights somewhere, so I went to the settings and checked the Securty and Privacy->Password settings. I didn't see anything odd there, but while I was in I switched to autologin to on.
Guess what.. that solves it.. My projects now happily build and run and can be executed from my VisualGDB debug command.
To double check I set autologin back to off and sure enough my VisualGDB failed again
So the secret is... ensure you have automatic login, with your matching ssh username
Bizzare issue...Dunno why this is happening, but very happy I resolved it.
Basically if you can't get an X11 window to open from your VisualStudio deployed app, you have to make sure that you are indeed using the correct log in name for your SSH connection and the Target. This is very unlikely to be different.
The issue however seems to relate to autologin on Ubuntu if you are signing in manually, even as your expected user name, you can transfer build and run, but your builds will fail whenever they try to get an X11 display to set up graphics.
I figured it had to be something to do with access rights somewhere, so I went to the settings and checked the Securty and Privacy->Password settings. I didn't see anything odd there, but while I was in I switched to autologin to on.
Guess what.. that solves it.. My projects now happily build and run and can be executed from my VisualGDB debug command.
To double check I set autologin back to off and sure enough my VisualGDB failed again
So the secret is... ensure you have automatic login, with your matching ssh username
Bizzare issue...Dunno why this is happening, but very happy I resolved it.
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