Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#46890 - [systemd] systemctl poweroff etc. kill session not graciously

Attached to Project: Arch Linux
Opened by Manuel Schneider (manuelschneid3r) - Tuesday, 27 October 2015, 19:51 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 18 June 2016, 13:05 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Thomas Bächler (brain0)
Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
This is rather vague, because I dont know how to find more sophisticated information. From what I see systemctl poweroff kills the session hard. At least my application has no time to save its settings.

Additional info:
Everything is up to date.



Steps to reproduce:
e.g. rm .bash_history, run bash, enter some commands, finally do "systemctl poweroff -i", restart machine an recognize that bash hat no time to save its history to .bash_history.
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 18 June 2016, 13:05 GMT
Reason for closing:  Fixed
Additional comments about closing:  Seems fixed, maybe by https://github.com/systemd/systemd/commi t/fbffe09d692c1bd92e3d552031d096e77c3886 51
Comment by Evangelos Foutras (foutrelis) - Wednesday, 28 October 2015, 04:50 GMT
Sounds like this bug: https://github.com/systemd/systemd/issues/317
Comment by Dave Reisner (falconindy) - Sunday, 12 June 2016, 19:00 GMT
I can't reproduce this with systemd v230. Shell history even shows the last command as being 'systemctl reboot'.

Loading...