I have a remote headless server without a monitor attached with SSH access.
From what I found out the hard way, the default install does not support VNC (using vino) without a monitor attached.
Tried several things to get this working this without success.
I followed this guide on setting up x11vnc and lightdm: https://www.crazy-logic.co.uk/projects/computing/how-to-install-x11vnc-vnc-server-as-a-service-on-ubuntu-20-04-for-remote-access-or-screen-sharing
I then also tried to install xubuntu-desktop, which did not help.
The issue is:
VNC asks for password and connects. All good.
I see the session login window (with the panel at the top), everything looks ok. All good.
screenshot1
After login I only see a blank screen. Nothing responds. Right click on the desktop does not open a context menu. Not good.
screenshot2
Expected would be to see the desktop, panels, menus...etc.
How would one solve this? And what exactly is happening here. The session logs show everything is ok, no errors. But the computer is unresponsive on VNC, only the background is visible.
Note: I do not have physical access to this server. A solution via SSH would be best.
Related
We got users complaining that accessing remote client on Remote Desktop does not bring up anything. When I try logging in to its Azure AVD, it opens up with a black screen and disappears in a second.
A simple start and stop on Azure portal seems to have fixed the problem. A restart did not fix it though. But, I am not sure why it happened in the first place and couldn't find a reason for it. Could anyone offer some suggestions please?
I tried to reproduce same in my environment. I got same error.
To resolve this issue, try the below.
The reason of this issue is slow sign-in process A black screen will appear for a while, until the regular desktop appears.
When the back screen shows to return to the previous screen, press CTRL + ALT + END. This launches Task Manager you will see the Desktop right away after Task Manager is called like below:
Make sure to disable the Bitmap Caching on the Remote Desktop Protocol (RDP) client like below.
Persistent bitmap caching is the combination of memory caching and glyphs. It will be reused throughout client sessions and also provide a bigger amount of cache space, which will result in a black screen.
And try to adjust Display size of your remote host's display like below:
Now I am able to connect RDP without any issue like below.
I have installed tightvncserver on a remote server and can run it. I use Remmina to access the server via vnc protocol and it works, my only problem is the desktop does not show. The screen that shows up is just blank
Please reference the picture. Don't mind the background just the window shown.I have no idea why its showing like this
I'm working with an api that requires an app to be started, the app runs a GUI on linux.
I need to punsh in some login information and then hide the app.
Is there a way I can go to the machine start the GUI and then hide it, log out, and have other users log in with out having the GUI shown, but still having the app running?
You can take a look at Xvfb http://en.wikipedia.org/wiki/Xvfb
it's a framebuffer version of X.
It will launch an X11 server without displaying it (useful with selenium for example)
Xdotool can send input to anyb xwindow, including xvfb
I'm trying to run screen (version 4.0) in the latest version of Cygwin under 64-bit Windows Ultimate, and it doesn't want to work. I launch a new screen session using "screen -d -m -S screen1". When I connect to it using something like "screen -A -d -r screen1" the process hangs. When I list screens with "screen -list" it reports the screen as "possibly Dead".
Any idea how to get screen working in my environment?
I just ran the same commands you did, and had similar problems. But I use screen under 64-bit Windows 7 all the time.
I just use screen to start a screen session, and screen -dr to reattach to the same session later. (I've actually been using screen -U and screen -drU, but I just realized that with defutf8 on in my $HOME/.screenrc, the -U isn't necessary.)
I haven't figured out why your approach doesn't work.
I am also currently trying to get screen work on a cygwin installation on a windows server 2008 installation.
it works in principle, so I can reuse sessions, but its quite buggy:
1.) only sessions started through an rdp session (on the windows desktop) are able to access mounted network shares, sessions started through ssh can only access "c". (okey not really a screen bug, more cygwin in general)
2.) detach doesn't work through ssh. strg+a+d just freezes the terminal, by using these keys in that sequence: [strg+z, bg, %, strg+c] I can get back into the screen session I've last visited.
3.) this leads to the funny state that I can have the same screen session attached multiple times, and see the input and output on all instances
I have successfully started a vncserver and can connect to it through the browser via 111.111.111.111:5081.
It looks like it's working because I do see the Gnome cursor (X).
However, apart from the cursor I just have a black screen. No taskbar or anything. Right click provides nothing either.
Does anyone have any idea what I need to do to get the full desktop ? I have created a new user and wondered if there is any settings that need changing.
Thanks in advance,
Alex
Your VNC server is running, but there is nothing running in it. No window manager, no desktop environment (GNOME), nothing. The cursor you are seeing is a Xserver cursor, not a GNOME cursor.
That probably means you ran the VNC server directly without using some of the friendly wrapper scripts such as vncserver. For example, if you have tightvnc installed and you run Xtightvnc directly, that's what you'll get.
For example, I usually start a VNC session (or port 5901) like this:
vncserver -geometry 1024x768 :1
Alternately, you can use x11vnc to serve your existing X desktop (instead of starting a new one in the background).