i start a ubuntu desktop pc - cold boot - acpi bios crashes and also apache2??
no idea what happened there :-(
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apache2 2.4.27-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Apache2ConfdDirListing: False
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Nov 17 13:29:09 2017
InstallationDate: Installed on 2017-01-31 (289 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
LANGUAGE=de_DE
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: apache2
UpgradeStatus: Upgraded to artful on 2017-11-11 (6 days ago)
error.log:
[Fri Nov 17 00:07:33.475497 2017] [mpm_event:notice] [pid 889:tid 140527590350720] AH00489: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Fri Nov 17 00:07:33.475524 2017] [core:notice] [pid 889:tid 140527590350720] AH00094: Command line: '/usr/sbin/apache2'
[Fri Nov 17 00:14:31.371018 2017] [mpm_event:notice] [pid 889:tid 140527590350720] AH00491: caught SIGTERM, shutting down
[Fri Nov 17 13:19:58.050229 2017] [mpm_event:notice] [pid 888:tid 139941252640640] AH00489: Apache/2.4.27 (Ubuntu) configured -- resuming normal operations
[Fri Nov 17 13:19:58.255224 2017] [core:notice] [pid 888:tid 139941252640640] AH00094: Command line: '/usr/sbin/apache2'
Thank you for taking the time to file a bug report.
Unfortunately there is not enough information from the bug report to
help determine the root cause. Additional syslog or other log messages
would be required to further triage this issue.
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".
For local configuration issues, you can find assistance here:
http://