Ask Your Question

emike's profile - activity

2017-09-12 13:12:30 -0500 answered a question F26 Tiger VNC server still has blank screen.

From what I can tell, vncserver failes when started from 'systemctl' but works when started from the command line.

I did both and checked gnome-session-binary:

emike 1932 1 0 03:22 ? 00:00:00 /usr/libexec/gnome-session-binary

emike 2684 1 0 03:24 pts/0 00:00:00 /usr/libexec/gnome-session-binary

The one on pts/0 was started from the command line. The other from systemctl.

Under the one started from the command line, there is a 'gnome-shell'. Not under the other. Also, a diff of the log files (:1 systemctl and :2 command line) the only noteable difference is:

< Failed to import environment: Process org.freedesktop.systemd1 exited with status 1

I can assume that this is because there is no controlling tty. This is definitely a bug. I don't yet know of a workaround.

Hope this helps.

emike

2017-09-12 13:12:27 -0500 answered a question F26 Tiger VNC server still has blank screen.

So far as I can tell, starting from the command line works, starting from systemctl does not:

emike 1932 1 0 03:22 ? 00:00:00 /usr/libexec/gnome-session-binary emike 2684 1 0 03:24 pts/0 00:00:00 /usr/libexec/gnome-session-binary

The gnome-session-binary on pts/2 was started from "vncviewer :2" on the command line. The other gnome-session-binary was started by 'systemctl start vncviewer#:1.service"

Further proof, "DISPLAY=:1 gnome-shell" from the command line will get the blank screen working.

From the .vnc logs for both :1 (blank) and :2 (working, command line) is this:

< Failed to import environment: Process org.freedesktop.systemd1 exited with status 1

Likely because there is no controlling tty. This is a bug. Don't know what the workaround would be.

emike at emike.org