Bug 532860
Summary: | Does not process latest fedora-release properly | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jesse Keating <jkeating> |
Component: | gnome-system-monitor | Assignee: | Søren Sandmann Pedersen <sandmann> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | dcantrell, kem, mclasen, sandmann |
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: | 2009-11-04 04:24:41 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: | |||
Bug Depends On: | |||
Bug Blocks: | 473303 |
Description
Jesse Keating
2009-11-04 03:34:42 UTC
Turns out this is because gnome-system-monitor uses lsb_release to figure out the release. This would mean dragging in redhat-lsb for every install, yuk. mclasen says he's going to fix this. Fixed in gnome-system-monitor-2.28.0-3 Tagged for release. |