Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 1
    Systemd only signals processes directly under it's control. Things like chrome are not one of those processes. Systemd will signal your display manager (xdm, gdm, kdm, whatever), it's then up to the display manager to signal its children, and so on down the line until you get to chrome. If nothing signals chrome, it dies when the xorg server is shut down and it's display goes away. Commented Apr 1, 2014 at 16:37
  • @Patrick: thanks, I guessed so. That's why I tried adding 'TimeoutStopSec=90s' to '[Service]' section of ' /etc/systemd/system/display-manager.service' according to this: freedesktop.org/software/systemd/man/systemd.service.html but nothing changes... :( Commented Apr 1, 2014 at 16:51
  • Chrome should be under systemd's control - systemd is pid 1 - but Chrome execs out of its wrapper script in a subshell and invokes child processes afterward. Still, it will do what it needs to kill its zygotes so long as your system is properly configured. Are you using one of those temp-space solutions for chrome that you'll find recommended in the Arch wiki? Commented Apr 3, 2014 at 8:19
  • 1
    I run into a similar problem with KDE and Firefox on Arch. I have never gotten around to trying to figure out why. Commented Apr 3, 2014 at 8:53
  • 2
    GDM is not signaling processes. GDM is essentially a dumb way to hook up Xorg and PAM. the real culprit is gnome-session. Commented Jun 30, 2014 at 20:37