[systemd-bugs] [Bug 77416] New: systemctl poweroff/reboot does not bring down user services respectfully

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=77416

          Priority: medium
            Bug ID: 77416
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: systemctl poweroff/reboot does not bring down user
                    services respectfully
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: vimregisters at gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

I have a .service file that goes something like

[Unit]
Description=Google Chrome Browser
After=startx.service

[Service]
ExecStart=/usr/bin/google-chrome
KillMode=process
KillSignal=SIGTERM

When I do 'systemctl --user stop/restart chrome' or 'systemctl --user default' 
systemd performs perfectly and the expected happens, chrome exits cleanly or
restarts cleanly.

However, when I do something like 'systemctl reboot', the order in which the
services are brought down is respected (i.e. chrome and pekwm before X) but the
method of bringing the services down is not. After a reboot, chrome whines
about being improperly shutdown, and sometimes even has a lock on the profile
preventing chrome from opening again.

I suspect this is a systemd problem since using any of the commands like --user
isolate/default/stop/restart etc, it works perfectly, but it all goes to crap
when I do systemctl reboot

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140414/a5d34622/attachment.html>