Revision as of 04:43, 13 May 2010
- 1 Fedora 7 - Common Bugs and Known Issues
- 1.1 Release Summary, Announcement and Notes
- 1.2 My Bug Is Not Listed
- 1.3 Common Issues
- 1.4 Less Common Issues
- 1.5 List of F7 Bugs and RFE's
Fedora 7 - Common Bugs and Known Issues
This page documents common bugs in Fedora 7 and, if available, fixes or workarounds for these problems. If you find your problem in this page, do not file a bug for it. Where appropriate, a reference to the current bug(s) in Bugzilla is included.
Release Summary, Announcement and Notes
- http://fedoraproject.org/wiki/F7ReleaseSummary. Make sure you read this page and related references in detail.
My Bug Is Not Listed
Not every bug is listed in this page. You can use bugzilla queries in the bottom of this page for that. We have collected this based on commonly discussed issues in our mailing lists and forums. If you believe any particular bug report is missed out here and if you have wiki access, add it this page or contact RahulSundaram with the bugzilla report number explaining why you believe that particular report qualifies as a common issue.
Dell Dual Core Systems
Bug 241249 - Some Dell laptops with Intel dual-core CPUs (Core Duo, Core 2 Duo, Pentium Dual Core) may require the
maxcpus=1 option at installation boot time.
No "gdm" User in KDE Live Images
Bug 238783 - When the KDE Live images or an installation of the KDE Live images boots, the following error appears:
Starting system message bus: unknown username "gdm" in message bus configuration
This is only a cosmetic problem and does not have affect any functionality.
Partition table claimed to be invalid on previously working drive
Bug 241288 - Prior to Fedora 7, the host protected area of hard drives was often ignored and formatted as usable drive space. With Fedora 7 and the new libata driver subsystem, the host protected area is respected by default. As a result, its possible the Fedora 7 kernels will believe your drive has a partition that extends off the end of the disk, as the sectors of the hpa are masked out. The work-around to upgrade such systems is to pass the module parameter 'libata.ignore_hpa=1' when booting the installer. For example, when booting the installer cd, boot with:
boot: linux libata.ignore_hpa=1
Those upgrading from FC6 or earlier via yum on impacted systems can add a line to modprobe.conf along these same lines to allow an F7 kernel to boot their system. Ex:
options libata ignore_hpa=1
Fail to boot after install when using RAID or LVM
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241949#c26 or https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=244539 for the workarounds. Also related reports on Bug 241949 , Bug 242043 , Bug 242334 , and Bug 247415 .
F7 CDROM installation method fails to recognize CD/DVD drive
Fedora 7 no X with ati x1400
Bug 241491 . Workaround documented in the bug report. Fixed in a update.
Less Common Issues
hald fails to start with error "Unable to open cache"
Bug 243482 - hald fails to start with error "Unable to open cache" on Dell Latitude 610 and possibly other systems. Workaround is to change ownership of a directory by running
chown haldaemon:haldaemon /var/cache/hald
List of F7 Bugs and RFE's
See Bug Status for more information.
- Status = NEW
- Status = ASSIGNED
- Status = REOPENED
- Status = CLOSED
- Status = NEEDINFO
- Status = MODIFIED
- Status = NEEDINFO_REPORTER
- Status = NEEDINFO_ENG