{"action":"created","issue":{"url":"https://api.github.com/repos/systemd/systemd/issues/1615","repository_url":"https://api.github.com/repos/systemd/systemd","labels_url":"https://api.github.com/repos/systemd/systemd/issues/1615/labels{/name}","comments_url":"https://api.github.com/repos/systemd/systemd/issues/1615/comments","events_url":"https://api.github.com/repos/systemd/systemd/issues/1615/events","html_url":"https://github.com/systemd/systemd/issues/1615","id":112227569,"number":1615,"title":"System hangs at reboot/shutdown - Arch Linux","user":{"login":"prescott66","id":735265,"avatar_url":"https://avatars.githubusercontent.com/u/735265?v=3","gravatar_id":"","url":"https://api.github.com/users/prescott66","html_url":"https://github.com/prescott66","followers_url":"https://api.github.com/users/prescott66/followers","following_url":"https://api.github.com/users/prescott66/following{/other_user}","gists_url":"https://api.github.com/users/prescott66/gists{/gist_id}","starred_url":"https://api.github.com/users/prescott66/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/prescott66/subscriptions","organizations_url":"https://api.github.com/users/prescott66/orgs","repos_url":"https://api.github.com/users/prescott66/repos","events_url":"https://api.github.com/users/prescott66/events{/privacy}","received_events_url":"https://api.github.com/users/prescott66/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":37,"created_at":"2015-10-19T20:36:04Z","updated_at":"2016-05-16T16:52:18Z","closed_at":null,"body":"Hi.\r\nWhen i try to shutdown/reboot arch linux, my system hangs to cca 90 seconds and then shutdown or reboot.\r\nI have created bug report at arch's bugzilla, but there is no one, who can find the problem.\r\nIt looks like there is problem with systemd, because after update to v227 issue is fixed for few reboots, then is back.\r\nPLEASE take a look at my logs in bug report. Maybe you will find problem:\r\n\r\nhttps://bugs.archlinux.org/task/46709"},"comment":{"url":"https://api.github.com/repos/systemd/systemd/issues/comments/219478962","html_url":"https://github.com/systemd/systemd/issues/1615#issuecomment-219478962","issue_url":"https://api.github.com/repos/systemd/systemd/issues/1615","id":219478962,"user":{"login":"layus","id":632767,"avatar_url":"https://avatars.githubusercontent.com/u/632767?v=3","gravatar_id":"","url":"https://api.github.com/users/layus","html_url":"https://github.com/layus","followers_url":"https://api.github.com/users/layus/followers","following_url":"https://api.github.com/users/layus/following{/other_user}","gists_url":"https://api.github.com/users/layus/gists{/gist_id}","starred_url":"https://api.github.com/users/layus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/layus/subscriptions","organizations_url":"https://api.github.com/users/layus/orgs","repos_url":"https://api.github.com/users/layus/repos","events_url":"https://api.github.com/users/layus/events{/privacy}","received_events_url":"https://api.github.com/users/layus/received_events","type":"User","site_admin":false},"created_at":"2016-05-16T16:52:18Z","updated_at":"2016-05-16T16:52:18Z","body":"@evverx Thanks for explaining this. It seems that you are right, SIGHUP is sent by the kernel, not systemd. This is quite a relief regarding my programming skills, because I could not find the offending line in systemd codebase :-).\r\n\r\nMeanwhile, the issue remains. While we know that applications mishandling signals are the real offenders here, we do not know why it started breaking around v229 of systemd, nor if systemd is responsible for the change of behavior.\r\nOf course, the bug is in the applications themselves (apparently conky and chromium) but the fact is that that bug never revealed itself before, so something must have changed in between. What could it be ? \r\n\r\nAll I can think of is a change in the order in which applications are killed. Systemd is quite aggressive when killing all the processes. It sends SIGSTOP to everyone without trusting the process hierarchy to do its job. Or maybe a change in cgroups implementation by the kernel;\r\n\r\nThe strange thing is, I do not observe the \"a stop job is running for...\" message anymore, but systemd still indirectly waits for my running conky when trying to unmount /home, and so for 90 seconds."}}