Vnc server windows 7 black screen

What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange. All rights reserved. Covered by US Patent. Come for the solution, stay for everything else. Welcome to our community! I saw a suggestion that the black screen may have been a hangover from the machine having been accessed via remote desktop which it has. This is where I show that I don't really know what I'm doing: The black screen machine had a slew of remote desktop services running which I stopped the machine to which I connected successfully didn't and I tried to makle the connection again and got a black screen again.

Is the RDP theory valid, if so how do I get around this and not get a black screen? Join our community to see this answer!

The configuration file that ships with TigerVNC works great with That may not be TigerVNC's fault, but a change in The change you made to the xstartup file seems to get around a dbus issue in I'm using a very similar xstartup for Mate that also allows me to have multiple sessions for the same user.

Sorry, something went wrong. My only guess I have for you is I ran across the logged-in-locally problem you're describing on my test machine, so I made sure not to log in on my production machine even tried right after reboot launching the server via ssh then trying to connect , but it's still black.

A few differences between my test machine and production machine that could be triggering this black screen issue:. When I get a chance, I can try adding users to my test machine and see if I can get it to fail the same way. I'll also try setting it so all local users require typing a password first. I am kind of hoping that when the. From earlier: I wish I knew enough to understand why you said you wouldn't worry about the errors. I'd rather there not be a black screen more, though.

And Update: I rules out difference 2 by making all users type a password to login locally. I ruled out 3 by turning off the auto launch of the one program. Facing the same issue here, and I repeated all that you discussed in this thread and in Additionally, I discovered that running vncserver with sudo fixes the black screen, without the need to exec startxfce4.

I checked the permissions on Xauthority , xinitrc , and they all seem fine. The following is a bit more info:. I am running Desktop Ubuntu Both users have to enter passwords to log in.

The guake terminal emulator starts with login for both users. I installed Tiger VNC through the Ubuntu repositories, then purged that install to copy over the generic Tiger VNC build using rsync if that matters, as suggested in The command I use to spawn the vncserver is:.

I am attaching the logs produced with sudo and without. I am logged into the GUI of my user on the machine, and am launching the vncserver from a terminal. I am connecting to the spawned vncserver from the same machine using Remmina localhost It almost works perfectly with sudo because the Ubuntu However, a small dock does appear when I click on activities. Gnome shell extensions and other settings are carried over. Xresources is not created, and does not exist.

This is the case when run as user and as root. I'm trying to enable remote login for both users on the machine, using the method in this SO question and answer I asked. I'm not sure starting vncserver as root is a workable solution. I modified the xstartup file shared by jmadams1 by changing mate-session to gnome-session. I can get this modified xstartup file to work correctly if and only if I am logged in to the GUI of the physical machine.

If I am not logged in, I get org. Check the journalctl log file attached. Changing the mate-session to startxfce4 gives the Xfce4 desktop, without the errors dearZac reports I was getting the same errors with exec startxfce4 in the xstartup. I am working on a new, more systemd compatible, startup of vncserver. It sounds like it might solve the issues you guys are seeing. I also see a black screen on my Fedora 29 when launching the vnc through the systemd. If you run from the command line, then everything works fine.

I'm launching a VNC server at boot time, as a specific user. In the xstartup script, I circumvent the problem by testing the return status of the window manager in my case, twm and if there is an error, sleeping and restarting the Vnc server.

What I don't get is why it fails the very first time and succeeds the next. I suspected that some system services were not fully launched but to no avail. I had this issue too on ubuntu, and on my side it was the power management settings.

Just a FYI, that method will probably never be supported. In general a modern Linux system doesn't allow multiple sessions as the same user. So the VNC session will need to be started as a service, and the user cannot be logged in locally.

One problem I've had is that I've been able to connect and view the remote desktop, but any subsequent windows that were created are displayed on the actual desktop, not my viewer virtual desktop.

I can connect to the remote machine via ssh as a regular user, then run the following:. Thu May 23 vncext: VNC extension running! Thu May 23 Connections: accepted: It then prompts me for my password three times - the first to "create a color profile", the second to "refresh the system repositories" and the third to again "create a color profile. After authenticating, it displays the standard display manager screen, but running an application like a terminal or the file manager appears to start, but apparently displays on the console display, not my virtual display.

You cannot be logged in locally and have a VNC session running at the same time. This is a limitation of modern Linux systems, and not us, so it's not something we can do much about.

This is a well known bug in your desktop environment. Please nag them. It seems we need to be a lot of us before they consider this a priority to fix. I've pushed my current working copy to for those who want to see where things are heading.

It still requires a lot of work, so it's not ready for general use quite yet. This is still open, so I'm going to post my similar issue here. Let me know if I should move it. Others have recently posted similar issues.

See here for example. I am starting the server via this command: vncserver :1 -geometry x -depth A black screen is the result of the lock screen. After it the screen is locked there seems no way to login again through vnc, the screen keeps black. I figured it out Close the lid, and try to RDP into this machine. Another test, open the lid, connect with VNC. In reply to Charlie Klausen's post on June 5, In reply to DeLore's post on June 15, Thank you for the help.

RDP works fine. Lid closed or open. Tried the shutdown command. No luck. Lid closed, VNS still fails to work. Only fix was to rollback from to JRN Scott. In reply to Andre Da Costa's post on June 5, Please can you explain why? Is that to prevent upgrades or to resolve for those experiencing the problem?