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!
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!
FS#54657 - [systemd] Journal is useless, no information in case of system freeze
Attached to Project:
Arch Linux
Opened by Philipp (hollunder) - Saturday, 01 July 2017, 09:02 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 01 July 2017, 09:35 GMT
Opened by Philipp (hollunder) - Saturday, 01 July 2017, 09:02 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 01 July 2017, 09:35 GMT
|
DetailsDescription:
I have a reproducible system freeze. What is also reproducable is that there is absolutely nothing to be found about it in the journal. The journal is thus not performing its core functionality. I have reported this problem years ago to the systemd devs and I thought they had done something about that. Apparently not. Additional info: * package version(s) libsystemd 232-8 * config and/or log files etc. Default Arch config. I wish there were any log files. Steps to reproduce: Get the system to freeze, journalctl -r. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 01 July 2017, 09:35 GMT
Reason for closing: None
Additional comments about closing: Nothing to be done here
Saturday, 01 July 2017, 09:35 GMT
Reason for closing: None
Additional comments about closing: Nothing to be done here