vnc session crashes after some time

Bug #1738203 reported by Stefan Sahlender
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu
Confirmed
Undecided
Unassigned
tightvnc (Ubuntu)
Confirmed
Undecided
Unassigned
xfce (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Sys-Info:
lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10

Packages:
apt-cache policy tightvncserver
tightvncserver:
  Installiert: (keine)
  Installationskandidat: 1.3.10-0ubuntu3
  Versionstabelle:
     1.3.10-0ubuntu3 500
        500 http://ch.archive.ubuntu.com/ubuntu artful/universe amd64 Packages

apt-cache policy xfce4-session
xfce4-session:
  Installiert: 4.12.1-3ubuntu3
  Installationskandidat: 4.12.1-3ubuntu3
  Versionstabelle:
 *** 4.12.1-3ubuntu3 500
        500 http://ch.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
        100 /var/lib/dpkg/status

Hello after updating to Ubuntu 17.10 / Artful my vnc session / xfce sessions keeps on crashing after some time ... some time can be between 5 mins or 24 hours.

It doesn't matter if it is a vm or a physical machine.

It always starts with the following messages ( it is taken from vnc log )

xfce4-session-Message: Got disconnected from D-Bus. Unless this happened during session shutdown, this is probably a bad thing.

** (zeitgeist-datahub:6142): WARNING **: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!

** (xfsettingsd:6129): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed

** (xfsettingsd:6129): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed

(xfsettingsd:6129): xfconf-CRITICAL **: IA__xfconf_channel_set_bool: assertion 'XFCONF_IS_CHANNEL(channel) && property' failed

** (xfsettingsd:6129): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed

** (xfsettingsd:6129): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed

** (xfsettingsd:6129): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed

** (xfsettingsd:6129): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed

** (xfsettingsd:6129): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed

** (xfsettingsd:6129): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed

** (xfsettingsd:6129): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed

** (xfsettingsd:6129): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
The program 'wrapper-1.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 1011 error_code 3 request_code 4 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(xfce4-panel:5596): xfce4-panel-WARNING **: Failed to connect to the D-BUS session bus: Failed to connect to socket /run/user/1000/bus: Datei oder Verzeichnis nicht gefunden
xfce4-panel: Es ist bereits eine laufende Instanz vorhanden

After that when I connect to the vnc session i just see the grey x-server background.

Revision history for this message
Stefan Sahlender (ssahlender) wrote :

Small update, vncserver is started with:

vncserver -geometry 1900x1000

Content of xstartup:

cat xstartup
#!/bin/sh
unset SESSION_MANAGER
autocutsel -fork
startxfce4 &

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tightvnc (Ubuntu):
status: New → Confirmed
Changed in ubuntu:
status: New → Confirmed
Changed in xfce (Ubuntu):
status: New → Confirmed
Revision history for this message
Stefan Sahlender (ssahlender) wrote :

Actually, i think i solved it:

The "magic" is to modify xstartup:

dbus-launch startcfce4 &

And then it works

Revision history for this message
Theo Linkspfeifer (lastonestanding) wrote :
Changed in xfce (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.