tightvncserver crash on startup (s390x - int code 003b)

[Hank Calzaretta]

This is a new Ubuntu 16.04.1 LTS installation on the s390x platform.

tightvncserver package release: 1.3.10-0ubuntu3 s390x

Started the vnc server by issuing: vncserver -depth 8

Contents of xstartup file
-------------------------
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &

Contents of vnc server log
---------------------------
hecalzar@heclxct2:~/.vnc$ cat heclxct2\:1.log
25/08/16 15:51:03 Xvnc version TightVNC-1.3.10
25/08/16 15:51:03 Copyright (C) 2000-2009 TightVNC Group
25/08/16 15:51:03 Copyright (C) 1999 AT&T Laboratories Cambridge
25/08/16 15:51:03 All Rights Reserved.
25/08/16 15:51:03 See http://www.tightvnc.com/ for information on TightVNC
25/08/16 15:51:03 Desktop name 'X' (heclxct2:1)
25/08/16 15:51:03 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
25/08/16 15:51:03 Listening for VNC connections on TCP port 5901
Font directory '/usr/share/fonts/X11/Type1/' not found - ignoring
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring
xrdb: Connection reset by peer
xrdb: Can't open display ':1'
xsetroot: unable to open display ':1'
twm: unable to open display ":1"
xterm: Xt error: Can't open display: :1

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: tightvncserver 1.3.10-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic s390x
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: s390x
Date: Thu Aug 25 16:32:40 2016
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=C
 SHELL=/bin/bash
SourcePackage: tightvnc
UpgradeStatus: No upgrade log present (probably fresh install)

[Dimitri John Ledkov (xnox)]

Ubuntu on z, is an Ubuntu Server and Cloud offering, that is by default it is headless systems, without any graphical displays. No graphical Desktop Environments. The default experience of Ubuntu Server, Cloud, OpenStack, Juju, LXD, MAAS use command-line and web-app interfaces.

As there is no display, before using VNC, one must create one. However, I discourage you from using graphical apps. What applications and workloads are you trying to use, that require a display and/or remove VNC display?

[Hank Calzaretta (hecalzar)]

I have been supporting Linux on this platform since 1999 and am very familiar with the cautions of running graphical applications on headless systems.

Unfortunately, some software from IBM and other vendors includes a graphical installer which makes installation 100 times simpler. VNC is only used for this function and not to run a xwindows desktop.

[Launchpad Janitor (janitor)]

[Expired for tightvnc (Ubuntu) because there has been no activity for 60 days.]