Black screen after connecting between 1.7.0 server and 1.9.0 client

bal...@nowtech.hu

unread,

Jan 9, 2019, 12:02:04 PM1/9/19

to TigerVNC User Discussion/Support

Dear All,

I know there are already black screen topics, but this VNC world is so mystic to me that I was happy to resolve a security negotiation problem.

Client version is TigerVNC Viewer 64-bit v1.9.0

Client process is (established through an SSH tunnel)
vncviewer -SecurityTypes VncAuth,None 127.0.0.1:1

Server version is tigervnc-standalone-server 1.7.0+dfsg-7 amd64 on Debian 9

Server process is
/usr/bin/Xtigervnc :1 -desktop vb-server:1 (nowtech) -auth /home/nowtech/.Xauthority -geometry 1600x900 -depth 24 -rfbwait 30000 -rfbauth /home/nowtech/.vnc/passwd -rfbport 5901 -pn -localhost -SecurityTypes VncAuth

So the server log for a black screen session is:

Wed Jan 9 17:40:42 2019
Connections: accepted: 127.0.0.1::60272
SConnection: Client needs protocol version 3.8
Connections: closed: 127.0.0.1::60272 (Clean disconnection)
EncodeManager: Framebuffer updates: 0
EncodeManager: Total: 0 rects, 0 pixels
EncodeManager: 0 B (1:-nan ratio)

Wed Jan 9 17:41:54 2019
Connections: accepted: 127.0.0.1::60274
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)

Wed Jan 9 17:41:59 2019
VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888

Wed Jan 9 17:42:00 2019
VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888
VNCSConnST: FramebufferUpdateRequest 1600x900 at 0,0 exceeds framebuffer
1400x900
process 3776: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1367.
This is normally a bug in some application using the D-Bus library.

Wed Jan 9 17:43:53 2019
Connections: closed: 127.0.0.1::60274 (Clean disconnection)
EncodeManager: Framebuffer updates: 1
EncodeManager: Tight:
EncodeManager: Solid: 1 rects, 1.26 Mpixels
EncodeManager: 16 B (1:315001 ratio)
EncodeManager: Total: 1 rects, 1.26 Mpixels
EncodeManager: 16 B (1:315001 ratio)

What is missing?
Thank you in advance: Balázs Bámer

Pierre Ossman

unread,

Jan 11, 2019, 9:14:35 AM1/11/19

to bal...@nowtech.hu, TigerVNC User Discussion/Support

On 09/01/2019 18:02, bal...@nowtech.hu wrote:
> Dear All,
>
> I know there are already black screen topics, but this VNC world is so mystic to me that I was happy to resolve a security negotiation problem.
>
> Client version is TigerVNC Viewer 64-bit v1.9.0
>
> Client process is (established through an SSH tunnel)
> vncviewer -SecurityTypes VncAuth,None 127.0.0.1:1
>
> Server version is tigervnc-standalone-server 1.7.0+dfsg-7 amd64 on Debian 9
>
> Server process is
> /usr/bin/Xtigervnc :1 -desktop vb-server:1 (nowtech) -auth /home/nowtech/.Xauthority -geometry 1600x900 -depth 24 -rfbwait 30000 -rfbauth /home/nowtech/.vnc/passwd -rfbport 5901 -pn -localhost -SecurityTypes VncAuth
>

How have you configured and started your server? Starting just Xvnc will
indeed just give you a black screen. You need to get a desktop
environment running as well. The vncserver script usually sets that up
correctly by default. However Debian has their own version of that
script, so we can't really support that. Please try our builds instead
and see how that works.

Regards
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600 https://plus.google.com/+CendioThinLinc

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

bal...@nowtech.hu

unread,

Jan 12, 2019, 11:25:34 AM1/12/19

to TigerVNC User Discussion/Support

Dear Pierre,

Thank you for your answer.

Once I had TightVNC configured by a former collegue, which used to work, but not any more. I have read it is better when the VNC client and server makes are the same, so removed TightVNC and installed Debian's TigerVNC. I use the vanilla Debian config and start it up so:
vncserver -geometry 1920x1080

I don't know anything about desktop environments, so I will try a TigerVNC build when I get there again.

Best regards: Balázs Bámer

Pierre Ossman

unread,

Jan 16, 2019, 10:27:58 AM1/16/19

to bal...@nowtech.hu, TigerVNC User Discussion/Support

On 12/01/2019 17:25, bal...@nowtech.hu wrote:
> Dear Pierre,
>
> Thank you for your answer.
>
> Once I had TightVNC configured by a former collegue, which used to work,
> but not any more. I have read it is better when the VNC client and server
> makes are the same, so removed TightVNC and installed Debian's TigerVNC. I
> use the vanilla Debian config and start it up so:
> vncserver -geometry 1920x1080
>
> I don't know anything about desktop environments, so I will try a TigerVNC
> build when I get there again.
>

Hopefully their startup script is better suited for their distribution
though.

Is this a new machine? Perhaps there isn't any desktop environment
installed?

Could you attach the complete server log so we can see the startup?

bal...@nowtech.hu

unread,

Jan 16, 2019, 3:21:25 PM1/16/19

to TigerVNC User Discussion/Support

Dear Pierre,

Thank you for the answer. The machine is 1 year old, and there is a working X window system on it. A miracle must have happened, because now after restarting the server the previous method was successful. I see the desktop. Here is the latest log:

09/01/19 16:28:07 Xvnc version TightVNC-1.3.9

09/01/19 16:28:07 See http://www.tightvnc.com/ for information on TightVNC

09/01/19 16:28:07 Desktop name 'X' (vb-server:1)

09/01/19 16:28:07 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t

09/01/19 16:28:07 Listening for VNC connections on TCP port 5901

/usr/bin/startxfce4: X server already running on display :1

/home/nowtech/.vnc/xstartup: 22: /home/nowtech/.vnc/xstartup: vncconfig: not found

Xlib: extension "RANDR" missing on display ":1".

gpg-agent[1372]: WARNING: "--write-env-file" is an obsolete option - it has no effect

gpg-agent: a gpg-agent is already running - not starting a new one

(xfce4-session:1359): xfce4-session-WARNING **: gpg-agent returned no PID in the variables

Xlib: extension "RANDR" missing on display ":1.0".

(xfwm4:1375): xfwm4-WARNING **: The display does not support the XRender extension.

(xfwm4:1375): xfwm4-WARNING **: The display does not support the XRandr extension.

(xfwm4:1375): xfwm4-WARNING **: The display does not support the XComposite extension.

(xfwm4:1375): xfwm4-WARNING **: The display does not support the XDamage extension.

(xfwm4:1375): xfwm4-WARNING **: The display does not support the XFixes extension.

(xfwm4:1375): xfwm4-WARNING **: Compositing manager disabled.

xfwm4-Message: Unsupported keyboard modifier '<Super>Tab'

(xfwm4:1375): xfwm4-WARNING **: Cannot find visual format on screen 0

Xlib: extension "RANDR" missing on display ":1".

Xlib: extension "RANDR" missing on display ":1.0".

(xfsettingsd:1379): xfsettingsd-CRITICAL **: No RANDR extension found in display :1.0. Display settings won't be applied.

Xlib: extension "XInputExtension" missing on display ":1.0".

(xfsettingsd:1379): xfsettingsd-CRITICAL **: XI is not present.

(xfsettingsd:1379): xfsettingsd-CRITICAL **: Failed to initialize the Xkb extension.

(xfsettingsd:1379): xfsettingsd-CRITICAL **: Failed to initialize the Accessibility extension.

Xlib: extension "RANDR" missing on display ":1.0".

xfwm4-Message: Unsupported keyboard modifier '<Super>Tab'

Xlib: extension "RANDR" missing on display ":1.0".

process 1435: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1367.

This is normally a bug in some application using the D-Bus library.

Xlib: extension "XInputExtension" missing on display ":1.0".

09/01/19 16:40:06 Got connection from client 127.0.0.1

09/01/19 16:40:06 Using protocol version 3.8

09/01/19 16:40:06 rfbProcessClientSecurityType: client gone

09/01/19 16:40:06 Client 127.0.0.1 gone

09/01/19 16:40:06 Statistics:

09/01/19 16:40:06 framebuffer updates 0, rectangles 0, bytes 0

09/01/19 16:42:02 Got connection from client 127.0.0.1

09/01/19 16:42:02 Using protocol version 3.8

09/01/19 16:42:02 rfbProcessClientSecurityType: client gone

09/01/19 16:42:02 Client 127.0.0.1 gone

09/01/19 16:42:02 Statistics:

09/01/19 16:42:02 framebuffer updates 0, rectangles 0, bytes 0

(polkit-gnome-authentication-agent-1:1427): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.

Try running the command

gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache

to make things work again for the time being.

xfwm4-Message: Unsupported keyboard modifier '<Super>Tab'

PolicyKit daemon disconnected from the bus.

We are no longer a registered authentication agent.

PolicyKit daemon reconnected to bus.

Attempting to re-register as an authentication agent.

We are now a registered authentication agent.

Xlib: extension "XInputExtension" missing on display ":1.0".

xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.

xfwm4: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.

(xfsettingsd:1379): libxfce4ui-WARNING **: ICE I/O Error

(xfsettingsd:1379): libxfce4ui-WARNING **: Disconnected from session manager.

xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.

xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.

wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.

Xvnc TigerVNC 1.7.0 - built Apr 9 2017 14:38:13

See http://www.tigervnc.org for information on TigerVNC.

Underlying X server release 11903000, The X.Org Foundation

Wed Jan 9 17:30:06 2019

vncext: VNC extension running!

vncext: Listening for VNC connections on local interface(s), port 5901

vncext: created VNC server for screen 0

/usr/bin/startxfce4: X server already running on display :1

** (xfce4-session:3729): CRITICAL **: polkit_unix_process_set_property: assertion 'val != -1' failed

gpg-agent[3742]: WARNING: "--write-env-file" is an obsolete option - it has no effect

gpg-agent: a gpg-agent is already running - not starting a new one

(xfce4-session:3729): xfce4-session-WARNING **: gpg-agent returned no PID in the variables

(xfwm4:3744): xfwm4-WARNING **: Error opening /dev/dri/card0: Permission denied

process 3776: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1367.

This is normally a bug in some application using the D-Bus library.

Wed Jan 9 17:30:18 2019

Connections: accepted: 127.0.0.1::60268

SConnection: Client needs protocol version 3.8

Connections: closed: 127.0.0.1::60268 (Clean disconnection)

EncodeManager: Framebuffer updates: 0

EncodeManager: Total: 0 rects, 0 pixels

EncodeManager: 0 B (1:-nan ratio)

Wed Jan 9 17:32:50 2019

Connections: accepted: 127.0.0.1::60270

SConnection: Client needs protocol version 3.8

Connections: closed: 127.0.0.1::60270 (Clean disconnection)

EncodeManager: Framebuffer updates: 0

EncodeManager: Total: 0 rects, 0 pixels

EncodeManager: 0 B (1:-nan ratio)

process 3776: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1367.

This is normally a bug in some application using the D-Bus library.

Wed Jan 9 17:40:42 2019

Wed Jan 9 17:58:58 2019

Connections: accepted: 127.0.0.1::60276

SConnection: Client needs protocol version 3.8

SConnection: Client requests security type VncAuth(2)

Wed Jan 9 17:59:03 2019

VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888

VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888

process 3776: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1367.

This is normally a bug in some application using the D-Bus library.

Wed Jan 9 17:59:53 2019

Connections: closed: 127.0.0.1::60276 (Clean disconnection)

EncodeManager: Framebuffer updates: 1

EncodeManager: Tight:

EncodeManager: Solid: 1 rects, 1.26 Mpixels

EncodeManager: 16 B (1:315001 ratio)

EncodeManager: Total: 1 rects, 1.26 Mpixels

EncodeManager: 16 B (1:315001 ratio)

process 3776: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1367.

This is normally a bug in some application using the D-Bus library.

thunar-volman: Unsupported USB device type "usb".

thunar-volman: Unsupported input device type "/dev/input/event0".

thunar-volman: Unsupported USB device type "usbhid".

thunar-volman: Unsupported USB device type "usb".

thunar-volman: Unsupported USB device type "usbhid".

thunar-volman: Unsupported input device type "/dev/input/event0".

thunar-volman: Unsupported USB device type "usb".

thunar-volman: Unsupported input device type "(null)".

thunar-volman: Unsupported input device type "/dev/input/event2".

thunar-volman: Unsupported USB device type "usbhid".

thunar-volman: Unsupported USB device type "usb".

thunar-volman: Unsupported USB device type "usbhid".

thunar-volman: Unsupported input device type "/dev/input/event0".

thunar-volman: Unsupported USB device type "usb".

thunar-volman: Unsupported USB device type "usbhid".

thunar-volman: Unsupported input device type "/dev/input/event0".

XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"

after 189 requests (189 known processed) with 2 events remaining.

xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.

xfwm4: Fatal IO error 104 (Connection reset by peer) on X server :1.0.

(xfsettingsd:3748): libxfce4ui-WARNING **: ICE I/O Error

(xfsettingsd:3748): libxfce4ui-WARNING **: Disconnected from session manager.

xfce4-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.

xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.

xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.

wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.

Xvnc TigerVNC 1.7.0 - built Apr 9 2017 14:38:13

See http://www.tigervnc.org for information on TigerVNC.

Underlying X server release 11903000, The X.Org Foundation

Wed Jan 16 21:11:51 2019

vncext: VNC extension running!

vncext: Listening for VNC connections on local interface(s), port 5901

vncext: created VNC server for screen 0

/usr/bin/startxfce4: X server already running on display :1

** (xfce4-session:10463): CRITICAL **: polkit_unix_process_set_property: assertion 'val != -1' failed

gpg-agent[10476]: WARNING: "--write-env-file" is an obsolete option - it has no effect

gpg-agent: a gpg-agent is already running - not starting a new one

(xfce4-session:10463): xfce4-session-WARNING **: gpg-agent returned no PID in the variables

(xfwm4:10478): xfwm4-WARNING **: Error opening /dev/dri/card0: Permission denied

process 10508: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1367.

This is normally a bug in some application using the D-Bus library.

Wed Jan 16 21:13:14 2019

Connections: accepted: 127.0.0.1::60278

SConnection: Client needs protocol version 3.8

SConnection: Client requests security type VncAuth(2)

Wed Jan 16 21:13:21 2019

VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888

VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888

VNCSConnST: FramebufferUpdateRequest 1920x1080 at 0,0 exceeds framebuffer

1400x900

(xfce4-terminal:10608): Gdk-CRITICAL **: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed

Reply all

Reply to author

Forward