vncviewer black screen unless vncserver started as root

I have a couple of LEAP15 computers (laptop and server) that I tigerVNC into. The laptop works as expected, but the server gives a blank screen on the vncviewer unless I start vncserver as root - then it works as expected. I’ve tried all these fixes, but they don’t resolve the issue for me on the server. Does anyone know what the issue might be? There seems to be a dbus/kdeinit issue on the server (from the vncserver logfile) that isn’t mentioned in these fixes. Thank You!!

https://forums.opensuse.org/showthread.php/521229-VNC-black-screen?highlight=vncviewer+black
https://forums.opensuse.org/showthread.php/532320-vncserver-blank-screen?highlight=vncviewer

vncserver logfile (server)

Xvnc TigerVNC 1.8.0 - built ??? ?? ???? ??:??:??
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 11906000, The X.Org Foundation


Tue Jan 15 19:11:55 2019
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on all interface(s), port 5901
 vncext:      created VNC server for screen 0
kcm_input: Using X11 backend
startkde: Starting up...
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments
kdeinit5: Communication error with launcher. Exiting!
kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__1) failed: : Connection refused
Qt: Session management error: networkIdsList argument is NULL
Configuring Lock Action
ksmserver: "/run/user/1000/KSMserver"
ksmserver: KSMServer: SetAProc_loc: conn  0 , prot= local , file= @/tmp/.ICE-unix/2621
ksmserver: KSMServer: SetAProc_loc: conn  1 , prot= unix , file= /tmp/.ICE-unix/2621
ksmserver: KSMServer::restoreSession  "saved at previous logout"
startkde: Shutting down...
kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__1) failed: : Connection refused
Error: Can not contact kdeinit5!
startkde: Done.
Qt: Session management error: Could not open network socket
OpenGL vendor string:                   VMware, Inc.
OpenGL renderer string:                 llvmpipe (LLVM 5.0, 128 bits)
OpenGL version string:                  3.0 Mesa 18.0.2
OpenGL shading language version string: 1.30
Driver:                                 LLVMpipe
GPU class:                              Unknown
OpenGL version:                         3.0
GLSL version:                           1.30
Mesa version:                           18.0.2
X server version:                       1.19.6
Linux kernel version:                   4.12.14
Requires strict binding:                yes
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
kf5.kcoreaddons.desktopparser: Property type "Url" is not a known QVariant type. Found while parsing property definition for "X-KWin-Video-Url" in "/usr/share/kservicetypes5/kwineffect.desktop"

Tue Jan 15 19:12:10 2019
 Connections: accepted: 198.162.1.138::59274
 SConnection: Client needs protocol version 3.8
 SConnection: Client requests security type VeNCrypt(19)
 SVeNCrypt:   Client requests security type TLSVnc (258)

Tue Jan 15 19:12:14 2019
 VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
 VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian rgb888

Tue Jan 15 19:12:19 2019
 ComparingUpdateTracker: 0 pixels in / 0 pixels out
 ComparingUpdateTracker: (1:-nan ratio)

Tue Jan 15 19:12:30 2019
 Connections: closed: 198.162.1.138::59274 (Clean disconnection)
 EncodeManager: Framebuffer updates: 4
 EncodeManager:   Tight:
 EncodeManager:     Solid: 6 rects, 2.53809 Mpixels
 EncodeManager:            96 B (1:105755 ratio)
 EncodeManager:   Total: 6 rects, 2.53809 Mpixels
 EncodeManager:          96 B (1:105755 ratio)
 ComparingUpdateTracker: 2.53809 Mpixels in / 482.615 kpixels out
 ComparingUpdateTracker: (1:5.25904 ratio)

Oops - sorry - I didn’t realize this got bumped in ‘apps’

OK - some good intel on this - it’s related to LEAP 15. It turns out my laptop (which I could successfully use tigerVNC with) was LEAP 42.3. So I installed LEAP 42.3 on my server and now I can tigerVNC successfully to it.