Bug 441898
Summary: | Errors in install.log should be highlighted at firstboot. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | archimerged Ark submedes <archimerged> |
Component: | firstboot | Assignee: | Chris Lumens <clumens> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-11-07 18:16:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
archimerged Ark submedes
2008-04-10 17:48:19 UTC
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping There's simply no way we can tell what an error looks like in this log file, though. I suppose we could look for any line that starts with something other than "Installing..." but what about packages with bad spec files that just like to print stuff out when running scriptlets? And then once you've displayed these error messages to the user in firstboot, what can they do about it? They will just have to click next anyway, login, become root, and do something with them then. I don't see there being much benefit to displaying these errors during firstboot when what we really should be doing is fixing the packaging errors to begin with. Ok, then email all lines not matching "^Installing|^FYI:" to root with subject line "possible installation errors in /root/install.log" The user who reads root email will be notified, and others who never read root email will not. However, I was suggesting the firstboot screen for rawhide -- users who are installing rawhide would like to hear about these errors (and knowing about them would save valuable volunteer testing time), and pointing them out noisily would lead to their correction (or addition of "FYI:") long before the next alpha release. Then you could leave the screen in for F11 since it wouldn't be triggered. So how about re-opening this as a bug against F11's rawhide? |