Bug#841740: systemd periodically kills gnome-terminal session

[luke]

Package: systemd
Version: 231-9
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

systemd is periodically killing a bunch of userspace daemons
(including gnome terminal sessions, and gvfs)

```
Oct 22 23:41:42 donbot systemd[1087]: Starting GNOME Terminal Server...
Oct 22 23:41:42 donbot dbus-daemon[20090]: Successfully activated service 'org.gnome.Terminal'
Oct 22 23:43:12 donbot systemd[1087]: gnome-terminal-server.service: Start operation timed out. Terminating.
Oct 22 23:43:12 donbot systemd[1087]: gvfs-daemon.service: Start operation timed out. Terminating.
Oct 22 23:43:12 donbot systemd[1087]: at-spi-dbus-bus.service: Start operation timed out. Terminating.
Oct 22 23:43:12 donbot systemd[1087]: Failed to start Virtual filesystem service.
Oct 22 23:43:12 donbot systemd[1087]: gvfs-daemon.service: Unit entered failed state.
Oct 22 23:43:12 donbot systemd[1087]: gvfs-daemon.service: Failed with result 'timeout'.
Oct 22 23:43:12 donbot systemd[1087]: Failed to start GNOME Terminal Server.
Oct 22 23:43:12 donbot systemd[1087]: gnome-terminal-server.service: Unit entered failed state.
Oct 22 23:43:12 donbot systemd[1087]: gnome-terminal-server.service: Failed with result 'timeout'.
Oct 22 23:43:12 donbot systemd[1087]: Failed to start Accessibility services bus.
Oct 22 23:43:12 donbot systemd[1087]: at-spi-dbus-bus.service: Unit entered failed state.
Oct 22 23:43:12 donbot systemd[1087]: at-spi-dbus-bus.service: Failed with result 'timeout'.
Oct 22 23:43:36 donbot dbus-daemon[20090]: Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service'
Oct 22 23:43:36 donbot systemd[1087]: Starting Accessibility services bus...
Oct 22 23:43:36 donbot dbus-daemon[20090]: Successfully activated service 'org.a11y.Bus'
Oct 22 23:43:36 donbot at-spi-bus-launcher[25807]: Activating service name='org.a11y.atspi.Registry'
Oct 22 23:43:36 donbot at-spi-bus-launcher[25807]: Successfully activated service 'org.a11y.atspi.Registry'
Oct 22 23:43:36 donbot org.a11y.atspi.Registry[25812]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Oct 22 23:43:42 donbot dbus-daemon[20090]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
Oct 22 23:43:42 donbot systemd[1087]: Starting Virtual filesystem service...
Oct 22 23:43:42 donbot dbus-daemon[20090]: Successfully activated service 'org.gtk.vfs.Daemon'
Oct 22 23:43:42 donbot gvfsd[25821]: fuse: bad mount point `/run/user/1000/gvfs': Transport endpoint is not connected
Oct 22 23:43:42 donbot dbus-daemon[20090]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service'
Oct 22 23:43:42 donbot systemd[1087]: Starting GNOME Terminal Server...

This happens every couple of minutes and I can't mount disks from within the
 cinammon UI, or use gnome-terminal
   * What led up to the situation?
I'm not sure. The last update to systemd or gnome-terminal were a month ago, but
this only started happening after the last reboot.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
The init system is not my area of expertise so I haven't been able
to find a workaround for this, and I'm not quite sure how to go about debugging
this either (though if you can advise how to attach to the correct process, I'm
happy to try anything out). AFAICS, though - the syslog output suggests that
systemd is unable to detect a working `gnome-terminal-server` (why this needs to
 be run directly by systemd rather than simply forking from my cinammon session
is perhaps best answered by a gnome-developer), but I was unable to determine by
 what metric systemd assume the process has timed out.

This issue makes `gnome-terminal` (at least) unusable, and I'm also unable to
mount media from the cinammon desktop, so I've filed this against `systemd`, as
the it is the common component in these breaking applications.
(The application runs correctly until `systemd` kills it for not running correctly ;)


-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser         3.115
ii  libacl1         2.2.52-3
ii  libapparmor1    2.10.95-5
ii  libaudit1       1:2.6.7-1
ii  libblkid1       2.28.2-1
ii  libc6           2.24-5
ii  libcap2         1:2.25-1
ii  libcryptsetup4  2:1.7.2-5
ii  libgcrypt20     1.7.3-2
ii  libgpg-error0   1.24-1
ii  libidn11        1.33-1
ii  libip4tc0       1.6.0-4
ii  libkmod2        22-1.1
ii  liblzma5        5.2.2-1.2
ii  libmount1       2.28.2-1
ii  libpam0g        1.1.8-3.3
ii  libseccomp2     2.3.1-2
ii  libselinux1     2.5-3
ii  libsystemd0     231-9
ii  mount           2.28.2-1
ii  util-linux      2.28.2-1

Versions of packages systemd recommends:
ii  dbus            1.10.12-1
ii  libpam-systemd  231-9

Versions of packages systemd suggests:
ii  policykit-1        0.105-17
pn  systemd-container  <none>
pn  systemd-ui         <none>

Versions of packages systemd is related to:
ii  udev  231-9

-- no debconf information