Rocketraman (talk | contribs) No edit summary |
(→what do log errors look like?: new section) |
||
| Line 24: | Line 24: | ||
{{command|restorecon -rv /var/lib/rpm/}} | {{command|restorecon -rv /var/lib/rpm/}} | ||
--[[User:Rocketraman|Rocketraman]] ([[User talk:Rocketraman|talk]]) 02:00, 29 November 2014 (UTC) | --[[User:Rocketraman|Rocketraman]] ([[User talk:Rocketraman|talk]]) 02:00, 29 November 2014 (UTC) | ||
== what do log errors look like? == | |||
Please give us a grep command we can use to quickly check if there are any errors in the log file. It's a waste of time to scroll down am 8,000-line file, not knowing exactly what an error line will look like. | |||
<br> | |||
[[User:Daveyost|Daveyost]] ([[User talk:Daveyost|talk]]) 07:23, 8 February 2015 (UTC) | |||
Revision as of 07:23, 8 February 2015
Older Version References
Do we need to reference upgrades from Fedora 16? Fedora 16 reached EOL in February of 2013.
User Experiences
There should be a place for user experiences to help the next person during their install woes. - Kitchm (talk) 19:50, 20 December 2013 (UTC)
About Post upgrade
I think the issue with chrome and the upgrade is obsolete, could it be that it was inserted for the upgrade to fedora 19 (or 18 even)? I did not have an issue with chrome after the upgrade to fedora 20. --Jringoot (talk) 08:09, 27 February 2014 (UTC)
I didn't have any problem with the Chrome Beta on the upgrade to Fedora 21 Beta. --Rocketraman (talk) 02:00, 29 November 2014 (UTC)
Proposed addition after --rebuilddb recommendation:
Due to bug #1167946 rebuilddb causes the selinux context of the files in /var/lib/rpm to be lost. Fix this via:
restorecon -rv /var/lib/rpm/
--Rocketraman (talk) 02:00, 29 November 2014 (UTC)
what do log errors look like?
Please give us a grep command we can use to quickly check if there are any errors in the log file. It's a waste of time to scroll down am 8,000-line file, not knowing exactly what an error line will look like.
Daveyost (talk) 07:23, 8 February 2015 (UTC)