(wrapper-2.0:9449): Gtk-WARNING **: 15:01:10.369: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkToggleButton) (wrapper-2.0:9454): Gtk-WARNING **: 15:01:10.367: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner XfceArrowButton) (wrapper-2.0:9449): Gtk-WARNING **: 15:01:10.358: Attempting to add a widget with type GtkToggleButton to a container of type XfcePanelPlugin, but the widget is already inside a container of type XfcePanelPlugin, please remove the widget from its existing container first. (wrapper-2.0:9449): GLib-GObject-CRITICAL **: 15:01:10.358: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Gpg-agent: a gpg-agent is already running - not starting a new one usr/bin/startxfce4: X server already running on display :1 mieq: warning: overriding existing handler (nil) with 0x562410d9e400 for event 3ģNI3X0 New Xtigervnc server 'cucumber:1 (monitor)' on port 5901 for display :1.ģNI3X0 Use xtigervncviewer -SecurityTypes VncAuth -passwd /home/monitor/.vnc/passwd :1 to connect to the VNC server. mieq: warning: overriding existing handler (nil) with 0x562410d9e400 for event 2 Vncext: Listening for VNC connections on local interface(s), port 5901 Underlying X server release 12101003, X.Org Here's the output in /home/monitor/.vnc/cucumber:5901.log: Xvnc TigerVNC 1.12.0 - built 17:06Ĭopyright (C) 1999-2021 TigerVNC Team and many others (see README.rst) success!Īpr 23 14:23:38 cucumber systemd: Deactivated successfully.Īpr 23 14:23:38 cucumber systemd: Consumed 2.477s CPU time. a couple of 'activating service'/'successfully activated' statements hereĪpr 23 14:23:38 cucumber : X connection to :1 broken (explicit kill or server shutdown).Īpr 23 14:23:38 cucumber : A connection to the bus can't be madeĪpr 23 14:23:38 cucumber xfconfd: Name lost on the message dbus, exiting.Īpr 23 14:23:38 cucumber tumblerd: Name 1 lost on the message dbus, exiting.Īpr 23 14:23:38 cucumber tumblerd: Name 1 lost on the message dbus, exiting.Īpr 23 14:23:38 cucumber tumblerd: Name 1 lost on the message dbus, exiting.Īpr 23 14:23:38 cucumber vncserver: Killing Xtigervnc process ID 5456. vncserver outputs its entire -help output hereĪpr 23 14:23:35 cucumber systemd: Started Start TigerVNC server at startup.Īpr 23 14:23:35 cucumber vncserver: Starting /usr/bin/Xtigervnc :1 -localhost=1 -desktop cucumber:1 (monitor) -rfbport 5901 -PasswordFile /home/mon>Īpr 23 14:23:35 cucumber vncserver: New Xtigervnc server 'cucumber:1 (monitor)' on port 5901 for display :1.Īpr 23 14:23:35 cucumber vncserver: Use xtigervncviewer -SecurityTypes VncAuth -passwd /home/monitor/.vnc/passwd :1 to connect to the VNC server.Īpr 23 14:23:35 cucumber vncserver: Starting session via '/home/monitor/.vnc/xstartup'Īpr 23 14:23:35 cucumber vncserver: Log file is /home/monitor/.vnc/cucumber:5901.log
journalctl shows the following log output: Apr 23 14:23:35 cucumber systemd: Starting Start TigerVNC server at startup.Īpr 23 14:23:35 cucumber vncserver: vncserver: Option 2>&1: Unrecognized!Īpr 23 14:23:35 cucumber vncserver: vncserver usage: However, using sudo systemctl start doesn't work. There are no error messages or warnings shown at all. Running the start command /usr/bin/vncserver -verbose -depth 24 -geometry 1280x800 -localhost in the command line manually works fine, and I can successfully connect using a remote SSH-tunnelled VNC connection. I've created a file at to make the service start on start-up, using the following configuration: ĭescription=Start TigerVNC server at startupĮxecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1ĮxecStart=/usr/bin/vncserver -verbose -depth 24 -geometry 1280x800 -localhost :%i I've set up TigerVNC server on Ubuntu 22.04LTS.
0 kommentar(er)
