Common F16 bugs

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(add a note on bash /etc/shells SNAFU (752827))
m (Reverted edits by Alberto783 (talk) to last revision by Morgancoxuk)
 
(39 intermediate revisions by 10 users not shown)
Line 50: Line 50:
 
When the page is in pre-release state and a new pre-release becomes available, simply remove any issues that are now fixed from the page entirely.
 
When the page is in pre-release state and a new pre-release becomes available, simply remove any issues that are now fixed from the page entirely.
 
-->
 
-->
 +
 +
== Resolved issues ==
 +
 +
{{Anchor|xfce-power-crash}}
 +
=== Xfce power manager crashes on login ===
 +
<small>[[#xfce-power-crash|link to this item]] - [[rhbug:736727|Bugzilla: #736727]]</small>
 +
 +
There was a bug in the {{package|xfce4-power-manager}} shipped with Fedora 16 which caused it to crash frequently, including on initial login, for many users. This issue has been fixed with an update, but you may still notice it on initial installation of Fedora 16 Xfce if you do not enable the updates repository during installation.
 +
 +
This issue was fixed in the updated [https://admin.fedoraproject.org/updates/FEDORA-2011-15825 xfce4-power-manager-1.0.10-2.fc16] package. To solve the issue, update your Fedora 16 installation as usual. You should no longer encounter this issue after updating to that version or later of {{package|xfce4-power-manager}}.
 +
 +
{{Anchor|preupgrade-bootloader-fail}}
 +
=== Upgrade from Fedora 14 or 15 to Fedora 16 with preupgrade leaves bootloader in previous configuration ===
 +
<small>[[#preupgrade-bootloader-fail|link to this item]] - [[rhbug:737731|Bugzilla: #737731]]</small>
 +
 +
If you used the {{command|preupgrade}} utility to upgrade from Fedora 14 or 15 to Fedora 16, the bootloader configuration may have been left in its previous state. This was due to preupgrade not recognizing that anaconda cannot 'update' the bootloader configuration in such an upgrade, due to the migration from grub to grub2 that should occur as part of the upgrade. This would result either in the system attempting to boot with a Fedora 14 kernel, or failing to boot entirely (depending on whether the previously-installed kernel is still present following the upgrade).
 +
 +
This issue was fixed for Fedora 14 in the updated [https://admin.fedoraproject.org/updates/FEDORA-2011-16047/preupgrade-1.1.10-1.fc14 preupgrade-1.1.10-1.fc14] package and for Fedora 15 in the updated [https://admin.fedoraproject.org/updates/FEDORA-2011-14766/preupgrade-1.1.10-1.fc15 preupgrade-1.1.10-1.fc15] package. To ensure you do not encounter this issue, check that you have at least this version of preupgrade installed before upgrading to Fedora 16.
 +
 +
{{Anchor|boot-kernel-loading}}
 +
=== After a kernel update, ''Loading...'' message on boot refers to the wrong kernel ===
 +
<small>[[#boot-kernel-loading|link to this item]] - [[rhbug:732654|Bugzilla: #732654]]</small>
 +
 +
After you first installed an updated kernel on a Fedora 16 system, the line which shows up briefly during the boot process - ''Loading (kernel version)...'' - would refer to the wrong kernel. This was because the {{command|grubby}} utility Fedora uses to update the bootloader configuration file did not correctly update this line.
 +
 +
The bug was entirely cosmetic: the correct kernel is loaded in all cases, only the message is incorrect.
 +
 +
This issue was fixed in the updated [https://admin.fedoraproject.org/updates/FEDORA-2011-16908/grubby-8.3-2.fc16 grubby-8.3-2.fc16] package. To solve the issue, update your Fedora 16 installation as usual. Kernels installed after grubby is updated will have correct ''Loading...'' lines. Kernels installed before grubby is updated will not be corrected by the update.
  
 
== Installation issues ==
 
== Installation issues ==
Line 62: Line 90:
 
You can also manually workaround the issue by copying the contents of {{filename|/var/lib/rpm/}} to the root filesystem volume prior to attempting the upgrade. Anaconda will then detect your current installation and be able to upgrade it.
 
You can also manually workaround the issue by copying the contents of {{filename|/var/lib/rpm/}} to the root filesystem volume prior to attempting the upgrade. Anaconda will then detect your current installation and be able to upgrade it.
  
{{Anchor|boot-on-softraid}}
+
{{Anchor|gpt-no-boot}}
 +
=== Some systems, particularly Apple Macs, cannot boot GPT-labelled disks ===
 +
<small>[[#gpt-no-boot|link to this item]] - [[rhbug:735733|Bugzilla: #735733]] [[rhbug:749325|Bugzilla: #749325]] [[rhbug:696482|Bugzilla: #696482]]</small>
  
 +
Fedora 16 uses the newer [https://en.wikipedia.org/wiki/GUID_Partition_Table GPT] disk label format, when formatting an entire disk during installation. (If you choose to install to some space on a disk that is already formatted, not having the entire disk reformatted, Fedora will not change the formatting of the disk). This new format brings several advantages. However, some systems have trouble booting from GPT-labelled disks.
 +
 +
Many Lenovo systems are known to be affected by this. Consequently, Fedora 16 does not in fact use the GPT label format for Lenovo systems; they are blacklisted to use the old MS-DOS format instead. Lenovo users should therefore not be affected by this issue, but it explains why you will get an MS-DOS disk label rather than a GPT one when installing Fedora 16 to a Lenovo system.
 +
 +
It is now also known that Apple Macs cannot boot from GPT-labelled disks in BIOS compatibility mode. They can, of course, boot from GPT-labelled disks when booting natively via EFI (the GPT format is associated with the UEFI standard). Fedora 16 cannot successfully boot on some Apple Macs in native EFI boot mode, however (see elsewhere in this page), and on such systems, you will need to install Fedora in BIOS compatibility mode; but then you must also work around this issue.
 +
 +
The symptoms of this issue are simply that the installation completes correctly and without errors but the installed system entirely fails to boot, not even reaching the bootloader menu. The system may report some kind of error - it may claim that no bootable disk is present - or it may simply drop to a blank screen or a flashing cursor or something of the kind. There are other problems which can cause such behaviour, but inability to boot from a GPT-labelled disk is one of the most likely.
 +
 +
If you are affected by this problem, you can work around it by passing the parameter ''nogpt'' to the Fedora installer. To do this, at the initial bootloader menu for the Fedora installation, where you can select to install, install in basic graphics mode, boot to the rescue mode and so on, hit the Tab key, then edit the command line for the Fedora installer and add the word ''nogpt''.
 +
 +
In some cases, the system BIOS is capable of booting from a GPT-labelled disk, but only if the protective MBR entry (see [https://en.wikipedia.org/wiki/GUID_Partition_Table#Legacy_MBR_.28LBA_0.29 here] for more details on this) is marked as bootable ('active'). Setting the protective MBR entry as active is a violation of the GPT specification, and so Fedora does not do so by default. We do not have a detailed list of systems which will boot from a GPT-labelled disk only if the protective MBR is marked active, but this seems to be the case with at least some HP machines, some Sony machines, and some Intel motherboards. On such a system, the more 'drastic' workaround listed above (instructing Fedora not to use a GPT disk label at all) will work, but you can also try a more limited workaround: install as normal, with a GPT disk label, and then manually set the 'active' flag on the protective MBR.
 +
 +
To do so, use the {{command|fdisk}} utility - do '''not''' use a utility which actually understands GPT disk labels, as it will edit the attributes of the GPT partition table, not the protective MBR. You can run the commands from a live Linux (Fedora or any other distribution), Fedora's rescue mode, or from a console within the Fedora installer after completing installation but before rebooting - hit ctrl-alt-F2 to access a console.
 +
 +
Usually, you would run these commands, with root privileges:
 +
<pre>
 +
fdisk /dev/sda
 +
a
 +
1
 +
w
 +
q
 +
</pre>
 +
/dev/sda should be the actual correct device for the hard disk to which Fedora has been installed. The rest of the commands toggle the 'active' flag on the first partition, which will almost certainly be the correct one - it is very unlikely the protective MBR will list more than a single partition. The 'w' command writes the changes, so if you want to check, you can run 'p' before 'w', to print the partition table. It should show a single large partition with an asterisk (*) under the 'Boot' column, like so:
 +
<pre>
 +
  Device Boot      Start        End      Blocks  Id  System
 +
/dev/sda1 *            1  125045423    62522711+  ee  GPT
 +
</pre>
 +
 +
{{Anchor|grub2-raid1-sector63}}
 +
=== Boot sometimes fails when installing to a pre-existing partition layout with complex boot configuration (e.g. software or firmware RAID-1) ===
 +
<small>[[#grub2-raid1-sector63|link to this item]] - [[rhbug:737508|Bugzilla: #737508]]</small>
 +
 +
Versions of Fedora prior to Fedora 16, and many other operating systems, will by default use the MS-DOS disk label format, and create the first partition on a hard disk at sector 63. This leaves a gap of 32KiB between the MBR and the first partition. This is the space into which the core of the system bootloader must be installed on an MS-DOS labelled disk.
 +
 +
The core part of Fedora 16's bootloader, grub2, may not fit into this 32KiB space, if the required configuration to boot the system is complex. One known problematic case comes when the /boot partition is on a software or firmware (not hardware) RAID-1 device. In this case, the core grub2 image must include RAID support, and the inclusion of this makes the core image larger than 32KiB in size.
 +
 +
In more 'straightforward' cases, grub2's core image is smaller than 32KiB in size, so this bug will often not be encountered. Also, if you install Fedora 16 in such a way that the target drive is re-formatted, Fedora will use a GPT disk label and create a 1MiB 'BIOS Boot' partition. With the GPT disk label format, the bootloader core must reside on such a 'BIOS Boot' partition, and the 1MB size provides comfortably enough room for any necessary grub2 core image. The bug only occurs when installing Fedora 16 to an existing partition layout (and hence also when upgrading an existing configuration) which requires a complex grub2 core image.
 +
 +
When you encounter the bug, Fedora's installer may warn you that bootloader installation failed, but the installation will complete. However, the installed system will fail to boot. If you examine the installer logs you may find the message ''grub2-setup: warn: your core.img is unusually large, it won't fit in the embedding area''.
 +
 +
The safest workaround for the issue is to resize the first partition on the disk so that there is more empty space in front of it. A very small change will be sufficient - just having the partition start at 1MiB rather than 32KiB should suffice. Some partition types can be non-destructively resized from the beginning in this way, but in some cases it may be necessary to archive all the data on the partition, delete it, re-create it with a slightly later starting sector, and then restore the data. If you have to do this, you will likely wish to note the partition's UUID and partition label before destroying the partition, and ensure that they match when re-creating it. There are parameters you can pass to the various ''mkfs'' commands to force the UUID of the created partition: for instance, the parameter is -U for the ''mke2fs'' command.
 +
 +
An alternative workaround may be to manually install grub-legacy (rather than grub2) as the bootloader. However, the use of grub-legacy on Fedora 16 is not officially supported, and grub-legacy may well be removed entirely from future Fedora releases, so this is likely to be feasible only in the short term.
 +
 +
You may also compare [https://wiki.archlinux.org/index.php/GRUB2#MBR_aka_msdos_partitioning_specific_instructions Arch Linux's note on the same issue].
 +
 +
{{Anchor|boot-on-softraid}}
 
=== Cannot boot with /boot partition on a software RAID array ===
 
=== Cannot boot with /boot partition on a software RAID array ===
 
<small>[[#boot-on-softraid|link to this item]] - [[rhbug:750794|Bugzilla: #750794]]</small>
 
<small>[[#boot-on-softraid|link to this item]] - [[rhbug:750794|Bugzilla: #750794]]</small>
Line 71: Line 148:
 
To work around this issue, do not put the /boot partition on the RAID array. Create a simple BIOS boot partition and a /boot partition on one of the disks, and place the other system partitions on the RAID array. Alternatively, you can install the appropriate grub2 modules manually from anaconda's console before rebooting from the installer, or from rescue mode. Edit the file {{filename|/mnt/sysimage/boot/grub2/grub.cfg}} and add the lines:
 
To work around this issue, do not put the /boot partition on the RAID array. Create a simple BIOS boot partition and a /boot partition on one of the disks, and place the other system partitions on the RAID array. Alternatively, you can install the appropriate grub2 modules manually from anaconda's console before rebooting from the installer, or from rescue mode. Edit the file {{filename|/mnt/sysimage/boot/grub2/grub.cfg}} and add the lines:
 
<pre>
 
<pre>
 +
insmod part_msdos
 
insmod raid
 
insmod raid
 
insmod mdraid09
 
insmod mdraid09
Line 78: Line 156:
 
<pre>
 
<pre>
 
chroot /mnt/sysimage
 
chroot /mnt/sysimage
grub2-install /dev/sda
+
grub2-install --modules="part_msdos raid mdraid09 mdraid1x" /dev/sda
grub2-install /dev/sdb
+
grub2-install --modules="part_msdos raid mdraid09 mdraid1x" /dev/sdb
 
</pre>
 
</pre>
 
Adjust the device names as appropriate to the disks used in your system.
 
Adjust the device names as appropriate to the disks used in your system.
 +
 +
<pre>
 +
Edit: I spent several hours getting SWRAID to work - just following the above instructions I was still unable to boot.
 +
 +
I needed to do the following...
 +
 +
1) Install from DVD - Not the liveCD - using the livecd I couldn't chroot /mnt/sysimage - there was also no /mnt/sysimage/boot
 +
2) Boot the DVD with 'nogpt' kernel option enabled
 +
</pre>
  
 
{{Anchor|biosboot-two-drives}}
 
{{Anchor|biosboot-two-drives}}
 +
 
=== Cannot install over an existing RAID configuration ===
 
=== Cannot install over an existing RAID configuration ===
 
<small>[[#biosboot-two-drives|link to this item]] - [[rhbug:729640|Bugzilla: #729640]]</small>
 
<small>[[#biosboot-two-drives|link to this item]] - [[rhbug:729640|Bugzilla: #729640]]</small>
Line 97: Line 185:
 
Error message is shown when you try to create a new partition layout and don't create BIOS boot partition. It says "you have not created a bootloader stage1 target device". This obscure message wants to say, that user forget to create a BIOS boot partition. To avoid this, you have to create a new partition. It must be 1-2 MB large and file system type must be 'BIOS boot'.
 
Error message is shown when you try to create a new partition layout and don't create BIOS boot partition. It says "you have not created a bootloader stage1 target device". This obscure message wants to say, that user forget to create a BIOS boot partition. To avoid this, you have to create a new partition. It must be 1-2 MB large and file system type must be 'BIOS boot'.
  
{{Anchor|preupgrade-bootloader-fail}}
+
{{Anchor|mac-nvidia-fail}}
 +
=== Some Macs with NVIDIA graphics adapters cannot boot via EFI and display corrupted graphics when booted via BIOS emulation ===
 +
<small>[[#mac-nvidia-fail|link to this item]] - [[rhbug:650949|Bugzilla: #650949]]</small>
  
=== Upgrade from Fedora 14 to Fedora 16 with preupgrade leaves bootloader in previous configuration ===
+
Several Mac owners have reported that their systems are unable to boot Fedora 16 (and, in fact, previous Fedora release) images via EFI, and display distorted graphics when booted via BIOS emulation. This affects some or all Macs with NVIDIA graphics adapters. Affected models are known to include the Macbook Pro 3,1, the Macbook Air3,1,1, and the Macbook Pro 4,1. This affects both live and non-live Fedora images: it is a kernel issue.
<small>[[#preupgrade-bootloader-fail|link to this item]] - [[rhbug:737731|Bugzilla: #737731]]</small>
+
 
 +
If you attempt to boot via EFI, the boot process will get some distance but eventually freeze with no further progress after printing some messages about the graphics adapter.
 +
 
 +
If you attempt to boot via BIOS compatibility mode, the boot process will succeed, but the display will be distorted.
 +
 
 +
Booting via BIOS compatibility mode and using Fedora's 'Basic graphics' mode (available from the installer boot menu) should work, but will provide only basic, non-native resolution 2D graphics. Booting via EFI is only possible if you use the text mode installation, and the installed system will also be incapable of any graphical display. Only the text console will work.
 +
 
 +
{{Anchor|live-iscsi}}
 +
=== Cannot boot after install to iSCSI from live image ===
 +
<small>[[#live-iscsi|link to this item]] - [[rhbug:736893|Bugzilla: #736893]]</small>
  
If you use the {{command|preupgrade}} utility to upgrade from Fedora 14 to Fedora 16, the bootloader configuration will be left in its previous state. This is due to preupgrade not recognizing that anaconda cannot 'update' the bootloader configuration in such an upgrade, due to the migration from grub to grub2 that should occur as part of the upgrade. This will result either in the system attempting to boot with a Fedora 15 kernel, or failing to boot entirely (depending on whether the previously-installed kernel is still present following the upgrade).
+
If you attempt to install Fedora 16 to an iSCSI storage device from any of the live images, the installation will complete successfully, but the installed system will fail to boot.
  
This issue should be resolved with an update to the Fedora 14 preupgrade shortly. We recommend waiting for this update or upgrading via the DVD or network install image, rather than using a non-fixed preupgrade package. You may also pre-upgrade first to Fedora 15, and from there to Fedora 16.
+
There is no known workaround for the issue at this point. However, installations from non-live images (the DVD or boot.iso images) work correctly. It is highly recommended that you install from a non-live image if you wish to install Fedora 16 to an iSCSI storage device.
  
 
{{Anchor|enablement-status}}
 
{{Anchor|enablement-status}}
Line 143: Line 242:
  
 
{{Anchor|kickstart-clearpart}}
 
{{Anchor|kickstart-clearpart}}
=== Must explicitly specify ''clearpart=none'' to use an existing disk layout in kickstart ===
+
=== Must explicitly specify ''clearpart --none'' to use an existing disk layout in kickstart ===
 
<small>[[#kickstart-clearpart|link to this item]] - [[rhbug:752216|Bugzilla: #752216]]</small>
 
<small>[[#kickstart-clearpart|link to this item]] - [[rhbug:752216|Bugzilla: #752216]]</small>
  
Due to a bug in the Fedora installer, you must include either a ''clearpart'' or an ''autopart'' command in any Fedora 16 kickstart file, even if the disk layout you wish to use does not actually require existing partitions to be cleared or automatic partitioning to be done. So if you wish to re-use an existing partition layout, you must explicitly include the line ''clearpart=none'' in your kickstart, rather than relying on it as a default behaviour as you could in the past (and as the documentation indicates).
+
Due to a bug in the Fedora installer, you must include either a ''clearpart'' or an ''autopart'' command in any Fedora 16 kickstart file, even if the disk layout you wish to use does not actually require existing partitions to be cleared or automatic partitioning to be done. So if you wish to re-use an existing partition layout, you must explicitly include the line ''clearpart --none'' in your kickstart, rather than relying on it as a default behaviour as you could in the past (and as the documentation indicates).
  
 
{{Anchor|4096MB-minimum-live}}
 
{{Anchor|4096MB-minimum-live}}
Line 157: Line 256:
  
 
If you must install to a smaller device than is possible with the live image you wish to use, you may try a network or DVD installation. If you select a suitably small package set, these installation methods will allow you to install to a smaller storage device.
 
If you must install to a smaller device than is possible with the live image you wish to use, you may try a network or DVD installation. If you select a suitably small package set, these installation methods will allow you to install to a smaller storage device.
 +
 +
{{Anchor|4k-sectors}}
 +
=== Cannot boot from disks with logical 4K (4096 byte) sector size ===
 +
<small>[[#4k-sectors|link to this item]] - [[rhbug:743146|Bugzilla: #743146]]</small>
 +
 +
The bootloader included with Fedora 16 is not capable of booting from a disk with a 4K logical sector size.
 +
 +
This is not a regression in Fedora 16: no previous Fedora release is capable of this either. However, such disks were virtually unknown until recently.
 +
 +
So-called ''[https://en.wikipedia.org/wiki/Advanced_Format Advanced Format]'' disks with sector sizes larger than 512 bytes are now increasingly common. The 'Green' (high capacity, low spin rate) disks provided by most manufacturers are often AF drives, and some other 2TB and larger drives are also AF. Most such drives, however, have physical 4K (4096 byte) sectors but 'logical' 512 byte sectors: they appear to the operating system as if the sector size is 512 bytes. Fedora 16 is capable of booting from such drives. A few drives have both physical and logical 4K sectors - they do not present a 512 byte sector size to the operating system. Fedora 16 is not capable of booting from such drives.
 +
 +
To determine the exact status of a drive, run {{command|parted}} on it, and type 'print'. One line in the output will look like this:
 +
<pre>
 +
Sector size (logical/physical): 512B/512B
 +
</pre>
 +
If it reads 512B/512B then the drive is a conventional one and will have no problems. If it reads 512B/4096B then the drive is an AF drive but has a logical sector size of 512 bytes and should also work. If it reads 4096B/4096B then the drive is an AF drive with a logical sector size of 4096 bytes, and you cannot boot from it with Fedora 16's bootloader. Fedora 16 can read and write data from and to such drives without any problems, but its default bootloader cannot boot from them.
 +
 +
{{Anchor|preupgrade-3rdparty-repos}}
 +
=== Preupgrade may fail if third-party repositories (especially VirtualBox) are enabled ===
 +
<small>[[#preupgrade-3rdparty-repos|link to this item]] - [[rhbug:650854|Bugzilla: #650854]]</small>
 +
 +
Several users have reported that trying to upgrade Fedora using preupgrade with the third-party VirtualBox repository enabled can lead to severe problems. It seems that the configuration of this repository can result in an incomplete updated VirtualBox package being downloaded, and instead of recognizing the incomplete download and ignoring or re-downloading the package, Fedora will attempt to install it, which can cause the upgrade process to fail halfway through, leaving the system in an inconsistent and possibly unusable state.
 +
 +
Some users have been able to resolve this problem by manually downloading the problematic VirtualBox package and replacing the incomplete copy in {{filename|/var/cache/yum/preupgrade}}, and re-running the upgrade process. However, it is likely that this will not always work flawlessly.
 +
 +
We strongly recommend you disable all third-party repositories prior to performing a preupgrade of Fedora. You can re-enable them and upgrade their packages separately, once the main upgrade is complete.
 +
 +
{{Anchor|amd-apu-install-no-display}}
 +
=== Screen switches off when anaconda installation sets display resolution ===
 +
<small>[[#amd-apu-install-no-display|link to this item]] - [[rhbug:753518|Bugzilla: #753518]]</small>
 +
 +
Anaconda fails set display on systems with new AMD APU processors and monitor connected to this integrated graphics. Solution is to add <code>nomodeset</code> kernel boot parameter and choose text or vnc install method.
 +
 +
{{Anchor|systemd-syslog-ng-problems}}
 +
=== Systemd and syslog-ng interaction problems: system freezes / syslog-ng fails to start  ===
 +
<small>[[#systemd-syslog-ng-problems|link to this item]] - [[rhbug:742624|Bugzilla: #742624]] - [[rhbug:770810|Bugzilla: #770810]]</small>
 +
 +
Due to a unix socket type mismatch between systemd and syslog-ng you
 +
most likely experience system freezes during system start up (with syslog-ng 3.2.4)
 +
or syslog-ng premature terminations (with syslog-ng 3.2.5-2).
 +
 +
Fix: If you haven't made any changes to the syslog-ng configuration file (/etc/syslog-ng/syslog-ng.conf),
 +
an update to syslog-ng-3.2.5-2 will fix the problem for you. But if you have customized it,
 +
you will have to manually edit it and change the unix socket type of '/dev/log' from unix-stream
 +
to unix-dgram (example below):
 +
 +
<pre>
 +
...
 +
source s_sys {
 +
  file ("/proc/kmsg" program_override("kernel: "));
 +
- unix-stream ("/dev/log");
 +
+ unix-dgram ("/dev/log");
 +
  internal();
 +
  # udp(ip(0.0.0.0) port(514));
 +
};
 +
...
 +
</pre>
  
 
== Hardware issues ==
 
== Hardware issues ==
Line 165: Line 321:
  
 
If you try to install Fedora 16 to a Lenovo Ideapad S205 booted via UEFI, the installed system will fail to boot. We do not yet have a complete understanding of this issue, but it appears the S205 may have a buggy UEFI implementation which prevents the {{command|efibootmgr}} tool from correctly writing an UEFI bootloader entry for Fedora. At present there is no known workaround for this issue. Installing in BIOS compatibility mode should avoid the problem, but it is not entirely clear from user reports and publicly available information whether the S205 actually has a BIOS compatibility mode and, if so, how to use it.
 
If you try to install Fedora 16 to a Lenovo Ideapad S205 booted via UEFI, the installed system will fail to boot. We do not yet have a complete understanding of this issue, but it appears the S205 may have a buggy UEFI implementation which prevents the {{command|efibootmgr}} tool from correctly writing an UEFI bootloader entry for Fedora. At present there is no known workaround for this issue. Installing in BIOS compatibility mode should avoid the problem, but it is not entirely clear from user reports and publicly available information whether the S205 actually has a BIOS compatibility mode and, if so, how to use it.
 +
 +
{{Anchor|fx5x00-shell-corruption}}
 +
=== Graphical corruption in GNOME Shell (and other 3D-accelerated applications) with NVIDIA GeForce FX 5200 adapters ===
 +
<small>[[#fx5x00-shell-corruption|link to this item]] - [[rhbug:745202|Bugzilla: #745202]]</small>
 +
 +
Multiple users of NVIDIA GeForce FX 5200 graphics adapters have reported display corruption in GNOME Shell in Fedora 16. This includes the default login screen, which is in fact a special rendering case of GNOME Shell in GNOME 3.2. The panel (at the top of the screen) is multi-colored and text contained in it is garbled, among other instances of corruption. Similar corruption may affect other 3D-accelerated applications.
 +
 +
All indications are that this bug affects at least all FX 5200 adapters. It may affect other FX 5xxx adapters too. The bug is currently under investigation by the ''nouveau'' driver maintainer. There is no direct workaround for the bug, but it appears to affect only 3D-accelerated rendering, and so if you use a 2D desktop - such as the GNOME fallback mode, or Xfce - you will not see any corruption. Using the NVIDIA proprietary driver is also reported to avoid the bug, although the Fedora project does not support, encourage or endorse the use of proprietary software.
  
 
== Software issues ==
 
== Software issues ==
Line 184: Line 348:
 
* It prevents login to a VSFTPD server if the user's login shell is set to bash
 
* It prevents login to a VSFTPD server if the user's login shell is set to bash
 
* It prevents SELinux sandboxing from working correctly: attempts to launch an application inside a sandbox will fail with the error ''Error: User shell is not valid''
 
* It prevents SELinux sandboxing from working correctly: attempts to launch an application inside a sandbox will fail with the error ''Error: User shell is not valid''
 +
* It prevents the screen brightness from being set in GNOME (either automatically on battery power, or manually via keyboard commands or the control center applet)
  
 
Fortunately, the bug is at least easy to resolve: simply run the command {{command|su -c 'yum reinstall bash'}}. This will reinstall the bash package, which resolves the issue. If you have no network access in order to reinstall the package, you can simply re-add bash to {{filename|/etc/shells}} manually, it is entirely safe to do so.
 
Fortunately, the bug is at least easy to resolve: simply run the command {{command|su -c 'yum reinstall bash'}}. This will reinstall the bash package, which resolves the issue. If you have no network access in order to reinstall the package, you can simply re-add bash to {{filename|/etc/shells}} manually, it is entirely safe to do so.
  
 
{{Anchor|glibc-large-groups}}
 
{{Anchor|glibc-large-groups}}
 +
 
=== Glibc may cause applications to crash with large groups ===
 
=== Glibc may cause applications to crash with large groups ===
 
<small>[[#glibc-large-groups|link to this item]] - [[rhbug:750361|Bugzilla: #750361]]</small>
 
<small>[[#glibc-large-groups|link to this item]] - [[rhbug:750361|Bugzilla: #750361]]</small>
Line 199: Line 365:
 
Due to a change in the default {{filename|/etc/nsswitch.conf}} file, when using a non-file backed user account backend (as is common for remote authentication methods such as sssd), user's secondary group memberships are not correctly registered.
 
Due to a change in the default {{filename|/etc/nsswitch.conf}} file, when using a non-file backed user account backend (as is common for remote authentication methods such as sssd), user's secondary group memberships are not correctly registered.
  
A test build that should resolve this problem is available from Koji: [http://koji.fedoraproject.org/koji/buildinfo?buildID=272429 authconfig-6.1.16-2.fc16]. If you are affected by this issue, please test this update and report your results to the [[rhbug:750388|bug report]].
+
This issue was fixed in the updated [https://admin.fedoraproject.org/updates/FEDORA-2011-15563/authconfig-6.1.16-2.fc16 authconfig-6.1.16-2.fc16] package. To solve the issue after installation, update your Fedora 16 installation as usual, then run {{command|su -c 'authconfig --updateall'}}.  You may still run into this issue on fresh installations of Fedora 16 unless you enable the ''updates'' repository during installation in order to ensure the updated authconfig package is used at install time.
  
To resolve the issue manually, edit the file {{filename|/etc/nsswitch.conf}} and remove the line:
+
To resolve the issue manually, or if the authconfig-based fix does not work for your configuration, edit the file {{filename|/etc/nsswitch.conf}} and remove the line:
 
<pre>
 
<pre>
 
initgroups: files
 
initgroups: files
Line 214: Line 380:
 
The issue is caused by {{command|gnome-settings-daemon}} crashing when it encounters a color profile with an incorrect SELinux context: the correct context for color profiles changed between Fedora 15 and Fedora 16, but the upgrade process does not re-label existing profiles.
 
The issue is caused by {{command|gnome-settings-daemon}} crashing when it encounters a color profile with an incorrect SELinux context: the correct context for color profiles changed between Fedora 15 and Fedora 16, but the upgrade process does not re-label existing profiles.
  
To resolve the issue, boot to a different desktop or to a console and run the command {{command|restorecon -r ~/.local/share/icc}}. After doing this, GNOME login should work correctly.
+
To resolve the issue, boot to a different desktop or to a console and run the command {{command|su -c 'chcon -R -t icc_data_home_t ~/.local/share/icc'}}. After doing this, GNOME login should work correctly.
 +
 
 +
{{Anchor|gdm-upgrade-caribou}}
 +
 
 +
=== Starting GDM (login manager) fails on x86_64 systems after upgrade from Fedora 15 due to i686 caribou package being installed ===
 +
<small>[[#gdm-upgrade-caribou|link to this item]] - [[rhbug:741075|Bugzilla: #741075]]</small>
 +
 
 +
Several users have reported that, after upgrading from the x86_64 version of Fedora 15 to Fedora 16, GDM (the default login manager) failed to start, displaying the "Oh no! Something has gone wrong" error screen. This issue is due to the i686 (32-bit) {{package|caribou}} package being installed during the upgrade, instead of the x86_64 version.
 +
 
 +
An updated [https://admin.fedoraproject.org/updates/FEDORA-2011-17041/caribou-0.4.1-3.fc16 caribou] package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and [https://admin.fedoraproject.org/updates/FEDORA-2011-17041/caribou-0.4.1-3.fc16 report to Bodhi] whether it solves the problem. To test the update, enable the ''updates-testing'' repository while upgrading from Fedora 15 to Fedora 16.
 +
 
 +
If you have already been affected by this problem, simply installing the x86_64 version of the {{package|caribou}} package - {{command|su -c 'yum install caribou.x86_64'}} - should resolve it.
  
 
{{Anchor|shell-monitor-cpu}}
 
{{Anchor|shell-monitor-cpu}}
Line 221: Line 398:
  
 
When the {{package|gnome-shell-extension-systemMonitor}} package - the System Monitor extension for GNOME Shell - is enabled, GNOME Shell can come to consume an excessive amount of CPU time. The issue can be worked around temporarily simply by restarting the Shell (a quick way to do this is to hit alt-f2 and enter the command as the single character 'r'). There is no known permanent workaround besides removing or disabling the extension.
 
When the {{package|gnome-shell-extension-systemMonitor}} package - the System Monitor extension for GNOME Shell - is enabled, GNOME Shell can come to consume an excessive amount of CPU time. The issue can be worked around temporarily simply by restarting the Shell (a quick way to do this is to hit alt-f2 and enter the command as the single character 'r'). There is no known permanent workaround besides removing or disabling the extension.
 
{{Anchor|boot-kernel-loading}}
 
=== After a kernel update, ''Loading...'' message on boot refers to the wrong kernel ===
 
<small>[[#boot-kernel-loading|link to this item]] - [[rhbug:732654|Bugzilla: #732654]]</small>
 
 
After you first install an updated kernel on a Fedora 16 system, the line which shows up briefly during the boot process - ''Loading (kernel version)...'' - will refer to the wrong kernel. This is because the {{command|grubby}} utility Fedora uses to update the bootloader configuration file does not correctly update this line.
 
 
The bug is entirely cosmetic: the correct kernel is loaded in all cases, only the message is incorrect. This issue will be resolved with an update to the {{package|grubby}} package.
 
  
 
{{Anchor|changed-time-breaks-boot}}
 
{{Anchor|changed-time-breaks-boot}}
Line 272: Line 441:
  
 
It may happen that you are presented with the error message, but you are not given any emergency shell. In that case please boot from the Fedora installation media and select ''Troubleshooting -> Rescue a Fedora system''. After the rescue tool mounts your system disks you can just reboot, everything should be corrected.
 
It may happen that you are presented with the error message, but you are not given any emergency shell. In that case please boot from the Fedora installation media and select ''Troubleshooting -> Rescue a Fedora system''. After the rescue tool mounts your system disks you can just reboot, everything should be corrected.
 +
 +
{{Anchor|bluetooth-file-transfer}}
 +
=== Cannot send files via Bluetooth ===
 +
<small>[[#bluetooth-file-transfer|link to this item]] - [[rhbug:753617|Bugzilla: #753617]]</small>
 +
 +
Due to changes in the kernel bluetooth interface, you will not be able to transfer files to another device via Bluetooth in Fedora 16. There is no known workaround for this issue besides transferring the files to the device in some other way (e.g. via USB cable or wifi).
 +
 +
{{Anchor|abrt-ccpp-service}}
 +
=== Abrt will not catch crashes after upgrade from a previous Fedora release ===
 +
<small>[[#abrt-ccpp-service|link to this item]] - [[rhbug:749603|Bugzilla: #749603]]</small>
 +
 +
When upgrading from a prior Fedora release, the abrt-ccpp service is not enabled. This will prevent the abrt program from catching software crashes, which will prevent users from reporting bugs. A workaround is to enable and start the service manually. You only need to run these commands once: on future system boots, the service will now start.
 +
<pre>
 +
# systemctl enable abrt-ccpp.service
 +
# systemctl start abrt-ccpp.service
 +
</pre>
 +
 +
{{Anchor|alternate-tab-crash}}
 +
=== GNOME Shell crashes when using the ''alternate-tab'' extension ===
 +
<small>[[#alternate-tab-crash|link to this item]] - [[rhbug:698939|Bugzilla: #698939]]</small>
 +
 +
If you install and enable the {{package|gnome-shell-extension-alternate-tab}} extension for GNOME Shell, you will likely find that the Shell often crashes when you use alt-tab or ctrl-tab. This problem is caused by bugs in the extension.
 +
 +
At present there is no known workaround for the problem except for removing or disabling the extension. We do not recommend the use of this extension in Fedora 16 at the present time.

Latest revision as of 14:32, 11 April 2012

This page documents common bugs in Fedora 16 and, if available, fixes or workarounds for these problems. If you find your problem in this page, do not file a bug for it, unless otherwise instructed. Where appropriate, a reference to the current bug(s) in Bugzilla is included.

Contents

[edit] Release Notes

Read the F16 Alpha release announcement and the Fedora 16 release notes for specific information about changes in Fedora 16 and other general information.

[edit] My bug is not listed

Not every bug is listed in this page, but Bugzilla should be a comprehensive database of known bugs. This page is a sampling of the bugs most commonly discussed on our mailing lists and forums.

To see if your bug has already been reported, you can search Bugzilla. If it has not yet been reported, we encourage you to do so to help improve Fedora for yourself and others. A guide to Bugs and feature requests has been prepared to assist you.

If you believe an already-reported bug report should be added to this page because it is commonly encountered, you can:

  • Add it yourself, if you have wiki access. Please follow the style and guidelines explained in the comments in the page source.
  • Or, add the CommonBugs keyword to the bug report. Someone from the QA team will then inspect the issue to determine whether the bug should be listed as a common bug. To expedite your request, please add a comment to the bug that includes
    1. a summary of the problem
    2. any known workarounds
    3. an assessment on the impact to Fedora users

For reference, you can query Bugzilla for bugs tagged CommonBugs:

  • CommonBugs? (bugs with CommonBugs keyword, but do not yet have a link to this page)
  • CommonBugs+(bugs with CommonBugs keyword and contain a link to this page)


[edit] Resolved issues

[edit] Xfce power manager crashes on login

link to this item - Bugzilla: #736727

There was a bug in the Package-x-generic-16.pngxfce4-power-manager shipped with Fedora 16 which caused it to crash frequently, including on initial login, for many users. This issue has been fixed with an update, but you may still notice it on initial installation of Fedora 16 Xfce if you do not enable the updates repository during installation.

This issue was fixed in the updated xfce4-power-manager-1.0.10-2.fc16 package. To solve the issue, update your Fedora 16 installation as usual. You should no longer encounter this issue after updating to that version or later of Package-x-generic-16.pngxfce4-power-manager.

[edit] Upgrade from Fedora 14 or 15 to Fedora 16 with preupgrade leaves bootloader in previous configuration

link to this item - Bugzilla: #737731

If you used the preupgrade utility to upgrade from Fedora 14 or 15 to Fedora 16, the bootloader configuration may have been left in its previous state. This was due to preupgrade not recognizing that anaconda cannot 'update' the bootloader configuration in such an upgrade, due to the migration from grub to grub2 that should occur as part of the upgrade. This would result either in the system attempting to boot with a Fedora 14 kernel, or failing to boot entirely (depending on whether the previously-installed kernel is still present following the upgrade).

This issue was fixed for Fedora 14 in the updated preupgrade-1.1.10-1.fc14 package and for Fedora 15 in the updated preupgrade-1.1.10-1.fc15 package. To ensure you do not encounter this issue, check that you have at least this version of preupgrade installed before upgrading to Fedora 16.

[edit] After a kernel update, Loading... message on boot refers to the wrong kernel

link to this item - Bugzilla: #732654

After you first installed an updated kernel on a Fedora 16 system, the line which shows up briefly during the boot process - Loading (kernel version)... - would refer to the wrong kernel. This was because the grubby utility Fedora uses to update the bootloader configuration file did not correctly update this line.

The bug was entirely cosmetic: the correct kernel is loaded in all cases, only the message is incorrect.

This issue was fixed in the updated grubby-8.3-2.fc16 package. To solve the issue, update your Fedora 16 installation as usual. Kernels installed after grubby is updated will have correct Loading... lines. Kernels installed before grubby is updated will not be corrected by the update.

[edit] Installation issues

[edit] Attempting to upgrade a system with /var on a different partition or LV to / will fail

link to this item - Bugzilla: #748119

If you have your system set up with /var on a separate logical volume or partition to that used for the root filesystem (/), then the Fedora 16 installer will not find the RPM db in /var/lib/rpm/ and fail to offer the option to upgrade. This happens with preupgrade as well as upgrade from install media.

A fix for this problem is available as an update image for the installer. For more information on update images, see Anaconda/Updates. To use this updates image, pass the kernel parameter updates=http://clumens.fedorapeople.org/748119.img to the Fedora installer. You can edit the boot parameters after hitting the Tab key when the boot menu screen is shown, or if you are using preupgrade, you can also choose to edit /boot/grub/grub.conf and add the parameter after the preupgrade application has downloaded the update packages but before rebooting to complete the upgrade.

You can also manually workaround the issue by copying the contents of /var/lib/rpm/ to the root filesystem volume prior to attempting the upgrade. Anaconda will then detect your current installation and be able to upgrade it.

[edit] Some systems, particularly Apple Macs, cannot boot GPT-labelled disks

link to this item - Bugzilla: #735733 Bugzilla: #749325 Bugzilla: #696482

Fedora 16 uses the newer GPT disk label format, when formatting an entire disk during installation. (If you choose to install to some space on a disk that is already formatted, not having the entire disk reformatted, Fedora will not change the formatting of the disk). This new format brings several advantages. However, some systems have trouble booting from GPT-labelled disks.

Many Lenovo systems are known to be affected by this. Consequently, Fedora 16 does not in fact use the GPT label format for Lenovo systems; they are blacklisted to use the old MS-DOS format instead. Lenovo users should therefore not be affected by this issue, but it explains why you will get an MS-DOS disk label rather than a GPT one when installing Fedora 16 to a Lenovo system.

It is now also known that Apple Macs cannot boot from GPT-labelled disks in BIOS compatibility mode. They can, of course, boot from GPT-labelled disks when booting natively via EFI (the GPT format is associated with the UEFI standard). Fedora 16 cannot successfully boot on some Apple Macs in native EFI boot mode, however (see elsewhere in this page), and on such systems, you will need to install Fedora in BIOS compatibility mode; but then you must also work around this issue.

The symptoms of this issue are simply that the installation completes correctly and without errors but the installed system entirely fails to boot, not even reaching the bootloader menu. The system may report some kind of error - it may claim that no bootable disk is present - or it may simply drop to a blank screen or a flashing cursor or something of the kind. There are other problems which can cause such behaviour, but inability to boot from a GPT-labelled disk is one of the most likely.

If you are affected by this problem, you can work around it by passing the parameter nogpt to the Fedora installer. To do this, at the initial bootloader menu for the Fedora installation, where you can select to install, install in basic graphics mode, boot to the rescue mode and so on, hit the Tab key, then edit the command line for the Fedora installer and add the word nogpt.

In some cases, the system BIOS is capable of booting from a GPT-labelled disk, but only if the protective MBR entry (see here for more details on this) is marked as bootable ('active'). Setting the protective MBR entry as active is a violation of the GPT specification, and so Fedora does not do so by default. We do not have a detailed list of systems which will boot from a GPT-labelled disk only if the protective MBR is marked active, but this seems to be the case with at least some HP machines, some Sony machines, and some Intel motherboards. On such a system, the more 'drastic' workaround listed above (instructing Fedora not to use a GPT disk label at all) will work, but you can also try a more limited workaround: install as normal, with a GPT disk label, and then manually set the 'active' flag on the protective MBR.

To do so, use the fdisk utility - do not use a utility which actually understands GPT disk labels, as it will edit the attributes of the GPT partition table, not the protective MBR. You can run the commands from a live Linux (Fedora or any other distribution), Fedora's rescue mode, or from a console within the Fedora installer after completing installation but before rebooting - hit ctrl-alt-F2 to access a console.

Usually, you would run these commands, with root privileges:

fdisk /dev/sda
a
1
w
q

/dev/sda should be the actual correct device for the hard disk to which Fedora has been installed. The rest of the commands toggle the 'active' flag on the first partition, which will almost certainly be the correct one - it is very unlikely the protective MBR will list more than a single partition. The 'w' command writes the changes, so if you want to check, you can run 'p' before 'w', to print the partition table. It should show a single large partition with an asterisk (*) under the 'Boot' column, like so:

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1 *             1   125045423    62522711+  ee  GPT

[edit] Boot sometimes fails when installing to a pre-existing partition layout with complex boot configuration (e.g. software or firmware RAID-1)

link to this item - Bugzilla: #737508

Versions of Fedora prior to Fedora 16, and many other operating systems, will by default use the MS-DOS disk label format, and create the first partition on a hard disk at sector 63. This leaves a gap of 32KiB between the MBR and the first partition. This is the space into which the core of the system bootloader must be installed on an MS-DOS labelled disk.

The core part of Fedora 16's bootloader, grub2, may not fit into this 32KiB space, if the required configuration to boot the system is complex. One known problematic case comes when the /boot partition is on a software or firmware (not hardware) RAID-1 device. In this case, the core grub2 image must include RAID support, and the inclusion of this makes the core image larger than 32KiB in size.

In more 'straightforward' cases, grub2's core image is smaller than 32KiB in size, so this bug will often not be encountered. Also, if you install Fedora 16 in such a way that the target drive is re-formatted, Fedora will use a GPT disk label and create a 1MiB 'BIOS Boot' partition. With the GPT disk label format, the bootloader core must reside on such a 'BIOS Boot' partition, and the 1MB size provides comfortably enough room for any necessary grub2 core image. The bug only occurs when installing Fedora 16 to an existing partition layout (and hence also when upgrading an existing configuration) which requires a complex grub2 core image.

When you encounter the bug, Fedora's installer may warn you that bootloader installation failed, but the installation will complete. However, the installed system will fail to boot. If you examine the installer logs you may find the message grub2-setup: warn: your core.img is unusually large, it won't fit in the embedding area.

The safest workaround for the issue is to resize the first partition on the disk so that there is more empty space in front of it. A very small change will be sufficient - just having the partition start at 1MiB rather than 32KiB should suffice. Some partition types can be non-destructively resized from the beginning in this way, but in some cases it may be necessary to archive all the data on the partition, delete it, re-create it with a slightly later starting sector, and then restore the data. If you have to do this, you will likely wish to note the partition's UUID and partition label before destroying the partition, and ensure that they match when re-creating it. There are parameters you can pass to the various mkfs commands to force the UUID of the created partition: for instance, the parameter is -U for the mke2fs command.

An alternative workaround may be to manually install grub-legacy (rather than grub2) as the bootloader. However, the use of grub-legacy on Fedora 16 is not officially supported, and grub-legacy may well be removed entirely from future Fedora releases, so this is likely to be feasible only in the short term.

You may also compare Arch Linux's note on the same issue.

[edit] Cannot boot with /boot partition on a software RAID array

link to this item - Bugzilla: #750794

Attempting to boot after installing Fedora 16 with the /boot partition on a software RAID array will fail, as the software RAID modules for the grub2 bootloader are not installed. Having the /boot partition on a RAID array has never been a recommended configuration for Fedora, but up until Fedora 16 it has usually worked.

To work around this issue, do not put the /boot partition on the RAID array. Create a simple BIOS boot partition and a /boot partition on one of the disks, and place the other system partitions on the RAID array. Alternatively, you can install the appropriate grub2 modules manually from anaconda's console before rebooting from the installer, or from rescue mode. Edit the file /mnt/sysimage/boot/grub2/grub.cfg and add the lines:

insmod part_msdos
insmod raid
insmod mdraid09
insmod mdraid1x

Now run these commands:

chroot /mnt/sysimage
grub2-install --modules="part_msdos raid mdraid09 mdraid1x" /dev/sda
grub2-install --modules="part_msdos raid mdraid09 mdraid1x" /dev/sdb

Adjust the device names as appropriate to the disks used in your system.

Edit: I spent several hours getting SWRAID to work - just following the above instructions I was still unable to boot.

I needed to do the following...

1) Install from DVD - Not the liveCD - using the livecd I couldn't chroot /mnt/sysimage - there was also no /mnt/sysimage/boot
2) Boot the DVD with 'nogpt' kernel option enabled 

[edit] Cannot install over an existing RAID configuration

link to this item - Bugzilla: #729640

If you attempt to install Fedora 16 onto a disk which contains a RAID array, the installer may crash with an error of the format IOException: Partition(s) 3 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.

Currently the only known way to workaround the issue is to destroy the existing RAID array in some way, such as by wiping its metadata with mdadm --zero-superblock, prior to installing Fedora 16.

[edit] Error "you have not created a bootloader stage1 target device" appears in partitioning menu

link to this item - Bugzilla: #752063

Error message is shown when you try to create a new partition layout and don't create BIOS boot partition. It says "you have not created a bootloader stage1 target device". This obscure message wants to say, that user forget to create a BIOS boot partition. To avoid this, you have to create a new partition. It must be 1-2 MB large and file system type must be 'BIOS boot'.

[edit] Some Macs with NVIDIA graphics adapters cannot boot via EFI and display corrupted graphics when booted via BIOS emulation

link to this item - Bugzilla: #650949

Several Mac owners have reported that their systems are unable to boot Fedora 16 (and, in fact, previous Fedora release) images via EFI, and display distorted graphics when booted via BIOS emulation. This affects some or all Macs with NVIDIA graphics adapters. Affected models are known to include the Macbook Pro 3,1, the Macbook Air3,1,1, and the Macbook Pro 4,1. This affects both live and non-live Fedora images: it is a kernel issue.

If you attempt to boot via EFI, the boot process will get some distance but eventually freeze with no further progress after printing some messages about the graphics adapter.

If you attempt to boot via BIOS compatibility mode, the boot process will succeed, but the display will be distorted.

Booting via BIOS compatibility mode and using Fedora's 'Basic graphics' mode (available from the installer boot menu) should work, but will provide only basic, non-native resolution 2D graphics. Booting via EFI is only possible if you use the text mode installation, and the installed system will also be incapable of any graphical display. Only the text console will work.

[edit] Cannot boot after install to iSCSI from live image

link to this item - Bugzilla: #736893

If you attempt to install Fedora 16 to an iSCSI storage device from any of the live images, the installation will complete successfully, but the installed system will fail to boot.

There is no known workaround for the issue at this point. However, installations from non-live images (the DVD or boot.iso images) work correctly. It is highly recommended that you install from a non-live image if you wish to install Fedora 16 to an iSCSI storage device.

[edit] Upgrade from previous releases resets the enablement status of services

link to this item - Bugzilla: #752846

If you upgrade from a previous Fedora release, some services that you previously had enabled may be disabled and therefore they will not be started automatically on boot. This happens to services whose initscripts were converted to native systemd units. This is intentional. The rule for migration to systemd is to "start-over fresh" with default start and stop policy from the new package, and not to migrate what the user had previously configured. systemd provides a tool (systemd-sysv-convert --apply) to help do this conversion if you want after the package is updated. You can instead choose to inspect the services' enablement status manually by using systemctl list-unit-files and systemctl enable foo.service as needed.

[edit] Incorrect partition type assigned to /boot partition on GPT-labelled disks

link to this item - Bugzilla: #746895

When formatting the installation disk with a GPT disk label (which Fedora 16 will usually do when a disk is being completely reformatted, unless you use the nogpt kernel parameter) and creating a /boot partition, the Fedora 16 installer will set an incorrect partition type on the partition: it will be marked as an EFI System partition. This happens because anaconda attempts to set the 'bootable' flag on the partition, but on GPT disks there is no such flag, and the request gets translated into a request to set the partition type to EFI System. In most cases this will have no practical consequences, but if you have another EFI-booted operating system installed on the same disk, it may be confused by the apparent presence of two EFI system partitions.

To work around any issues caused by this, use a GPT-capable partition editor such as parted to correct the partition type on the /boot partition.

[edit] No workable bootloader action in text mode upgrade

link to this item - Bugzilla: #742207

If you use the text mode of the Fedora installer to perform an upgrade from Fedora 15 to Fedora 16, there is no usable option at the stage where you are asked what to do with the bootloader. The update option cannot be used due to the switch from grub to grub2, and the skip option will often result in an unbootable system as the kernel(s) referenced in the bootloader configuration will no longer be installed.

The easiest workaround for this issue is to avoid using the installer's text mode, if you can. If you cannot avoid this, you should select Skip bootloader and then manually update the bootloader configuration from the installer shell (available on VT2) or from another OS (such as a live boot) following the upgrade process.

[edit] Installer doesn't ask for wifi password

link to this item - Bugzilla: #751139

If you want to install Fedora from network repositories and you have only a wireless network adapter available, you need to provide a password manually in order to connect to a secured wifi network. After the installer asks you which wireless network to connect to and you confirm your choice, another dialog called Network Connections pops up. In this dialog go to the Wireless tab, edit your chosen network a provide your password in the Wireless Security tab (WEP Passphrase or WPA Personal are most commonly used security protocols).

[edit] Disk encryption with national keymap often doesn't work

link to this item - Bugzilla: #743281

The installer offers a possibility to encrypt your disk partitions. If you chose a non-US keyboard layout earlier in the installation process, there is a possibility that if you encrypt your disk with some language-specific characters you might not be able to decrypt the disk during system boot. This concerns only some languages and only some keyboard layouts, but the full list of affected layouts is unknown.

The recommended approach is to use ASCII-only characters in your disk encryption password, or (this is the safest approach) select the default US keyboard layout in the installation process, and set your custom keyboard layout only inside the desktop session.

[edit] Must explicitly specify clearpart --none to use an existing disk layout in kickstart

link to this item - Bugzilla: #752216

Due to a bug in the Fedora installer, you must include either a clearpart or an autopart command in any Fedora 16 kickstart file, even if the disk layout you wish to use does not actually require existing partitions to be cleared or automatic partitioning to be done. So if you wish to re-use an existing partition layout, you must explicitly include the line clearpart --none in your kickstart, rather than relying on it as a default behaviour as you could in the past (and as the documentation indicates).

[edit] Minimum space for Desktop live install incorrectly calculated

link to this item - Bugzilla: #753400

The minimum required space for the root partition of a Fedora 16 live installation is incorrectly defined in the Fedora installer. The actual minimum size of the target partition for the Desktop live image is 4096MiB, but the installer will attempt to install to partitions that are somewhat smaller, and fail with the error RuntimeError: error copying filesystem!

There is no exact workaround for this issue: it is simply required that the target partition be 4096MiB or greater in size for a Desktop live installation. The required size varies for some spins: for the Sugar on a Stick spin it is 2048MiB, for instance.

If you must install to a smaller device than is possible with the live image you wish to use, you may try a network or DVD installation. If you select a suitably small package set, these installation methods will allow you to install to a smaller storage device.

[edit] Cannot boot from disks with logical 4K (4096 byte) sector size

link to this item - Bugzilla: #743146

The bootloader included with Fedora 16 is not capable of booting from a disk with a 4K logical sector size.

This is not a regression in Fedora 16: no previous Fedora release is capable of this either. However, such disks were virtually unknown until recently.

So-called Advanced Format disks with sector sizes larger than 512 bytes are now increasingly common. The 'Green' (high capacity, low spin rate) disks provided by most manufacturers are often AF drives, and some other 2TB and larger drives are also AF. Most such drives, however, have physical 4K (4096 byte) sectors but 'logical' 512 byte sectors: they appear to the operating system as if the sector size is 512 bytes. Fedora 16 is capable of booting from such drives. A few drives have both physical and logical 4K sectors - they do not present a 512 byte sector size to the operating system. Fedora 16 is not capable of booting from such drives.

To determine the exact status of a drive, run parted on it, and type 'print'. One line in the output will look like this:

Sector size (logical/physical): 512B/512B

If it reads 512B/512B then the drive is a conventional one and will have no problems. If it reads 512B/4096B then the drive is an AF drive but has a logical sector size of 512 bytes and should also work. If it reads 4096B/4096B then the drive is an AF drive with a logical sector size of 4096 bytes, and you cannot boot from it with Fedora 16's bootloader. Fedora 16 can read and write data from and to such drives without any problems, but its default bootloader cannot boot from them.

[edit] Preupgrade may fail if third-party repositories (especially VirtualBox) are enabled

link to this item - Bugzilla: #650854

Several users have reported that trying to upgrade Fedora using preupgrade with the third-party VirtualBox repository enabled can lead to severe problems. It seems that the configuration of this repository can result in an incomplete updated VirtualBox package being downloaded, and instead of recognizing the incomplete download and ignoring or re-downloading the package, Fedora will attempt to install it, which can cause the upgrade process to fail halfway through, leaving the system in an inconsistent and possibly unusable state.

Some users have been able to resolve this problem by manually downloading the problematic VirtualBox package and replacing the incomplete copy in /var/cache/yum/preupgrade, and re-running the upgrade process. However, it is likely that this will not always work flawlessly.

We strongly recommend you disable all third-party repositories prior to performing a preupgrade of Fedora. You can re-enable them and upgrade their packages separately, once the main upgrade is complete.

[edit] Screen switches off when anaconda installation sets display resolution

link to this item - Bugzilla: #753518

Anaconda fails set display on systems with new AMD APU processors and monitor connected to this integrated graphics. Solution is to add nomodeset kernel boot parameter and choose text or vnc install method.

[edit] Systemd and syslog-ng interaction problems: system freezes / syslog-ng fails to start

link to this item - Bugzilla: #742624 - Bugzilla: #770810

Due to a unix socket type mismatch between systemd and syslog-ng you most likely experience system freezes during system start up (with syslog-ng 3.2.4) or syslog-ng premature terminations (with syslog-ng 3.2.5-2).

Fix: If you haven't made any changes to the syslog-ng configuration file (/etc/syslog-ng/syslog-ng.conf), an update to syslog-ng-3.2.5-2 will fix the problem for you. But if you have customized it, you will have to manually edit it and change the unix socket type of '/dev/log' from unix-stream to unix-dgram (example below):

...
 source s_sys {
  file ("/proc/kmsg" program_override("kernel: "));
- unix-stream ("/dev/log");
+ unix-dgram ("/dev/log");
  internal();
  # udp(ip(0.0.0.0) port(514));
 };
...

[edit] Hardware issues

[edit] UEFI install to Lenovo Ideapad S205 fails to boot

link to this item - Bugzilla: #748272

If you try to install Fedora 16 to a Lenovo Ideapad S205 booted via UEFI, the installed system will fail to boot. We do not yet have a complete understanding of this issue, but it appears the S205 may have a buggy UEFI implementation which prevents the efibootmgr tool from correctly writing an UEFI bootloader entry for Fedora. At present there is no known workaround for this issue. Installing in BIOS compatibility mode should avoid the problem, but it is not entirely clear from user reports and publicly available information whether the S205 actually has a BIOS compatibility mode and, if so, how to use it.

[edit] Graphical corruption in GNOME Shell (and other 3D-accelerated applications) with NVIDIA GeForce FX 5200 adapters

link to this item - Bugzilla: #745202

Multiple users of NVIDIA GeForce FX 5200 graphics adapters have reported display corruption in GNOME Shell in Fedora 16. This includes the default login screen, which is in fact a special rendering case of GNOME Shell in GNOME 3.2. The panel (at the top of the screen) is multi-colored and text contained in it is garbled, among other instances of corruption. Similar corruption may affect other 3D-accelerated applications.

All indications are that this bug affects at least all FX 5200 adapters. It may affect other FX 5xxx adapters too. The bug is currently under investigation by the nouveau driver maintainer. There is no direct workaround for the bug, but it appears to affect only 3D-accelerated rendering, and so if you use a 2D desktop - such as the GNOME fallback mode, or Xfce - you will not see any corruption. Using the NVIDIA proprietary driver is also reported to avoid the bug, although the Fedora project does not support, encourage or endorse the use of proprietary software.

[edit] Software issues

[edit] Bash entry in /etc/shells disappears after update

link to this item - Bugzilla: #752827

Due to an error in the %postun script of Package-x-generic-16.pngbash-4.2.10-4.fc16, the version of Bash that was included in the Fedora 16 release images, the first time you update from that version of the package, the entry for bash in /etc/shells will be removed.

A fixed bash-4.2.10-5.fc16 has already been released. However, the %postun script from a given package version is run when that package version is removed, so it is in fact impossible to fix the broken script in the -4 package with an update, as it will always be the version of the script from the -4 package which is run when updating from that version.

The result is that this bug will always happen on the first update of the Package-x-generic-16.pngbash package after a fresh Fedora 16 installation, unless you enable the updates repository during installation and so get a fixed version of the package. We will attempt to produce a fix which reverses the effect of the broken script on update, in order to mitigate the problem.

There are several consequences of this bug, likely including some we have not yet come across. Those we know about are listed below.

  • It will make it impossible to set bash as the login shell for newly-created user accounts
  • It prevents pkexec from working correctly: some other applications use pkexec to launch commands, so these will also be affected. The error returned by pkexec will be The value for the SHELL variable was not found the /etc/shells file
  • It prevents login to a VSFTPD server if the user's login shell is set to bash
  • It prevents SELinux sandboxing from working correctly: attempts to launch an application inside a sandbox will fail with the error Error: User shell is not valid
  • It prevents the screen brightness from being set in GNOME (either automatically on battery power, or manually via keyboard commands or the control center applet)

Fortunately, the bug is at least easy to resolve: simply run the command su -c 'yum reinstall bash'. This will reinstall the bash package, which resolves the issue. If you have no network access in order to reinstall the package, you can simply re-add bash to /etc/shells manually, it is entirely safe to do so.

[edit] Glibc may cause applications to crash with large groups

link to this item - Bugzilla: #750361

Groups with either a large number of users or simply a large number of characters forming the user list may have problems with the glibc shipped in the release. The symptoms of this will vary depending on how you store your group information. If using a file in /etc/group programs which attempt to access group information for a user in that group will crash. If using a local nss db, the group will simply fail to be added to the user's list of groups when the user logs in. The latter may be worked around by running "newgrp groupname". At this time, it's unknown how these bugs affect other nss backends.

[edit] Secondary group membership not correctly registered with non-disk backed user account backends

link to this item - Bugzilla: #750388

Due to a change in the default /etc/nsswitch.conf file, when using a non-file backed user account backend (as is common for remote authentication methods such as sssd), user's secondary group memberships are not correctly registered.

This issue was fixed in the updated authconfig-6.1.16-2.fc16 package. To solve the issue after installation, update your Fedora 16 installation as usual, then run su -c 'authconfig --updateall'. You may still run into this issue on fresh installations of Fedora 16 unless you enable the updates repository during installation in order to ensure the updated authconfig package is used at install time.

To resolve the issue manually, or if the authconfig-based fix does not work for your configuration, edit the file /etc/nsswitch.conf and remove the line:

initgroups: files

[edit] Starting GNOME Shell fails after upgrade from Fedora 15 with color profile installed

link to this item - Bugzilla: #741549

If you used the Package-x-generic-16.pnggnome-color-manager tool to install a color profile for any of your hardware in Fedora 15, then after upgrading to Fedora 16, you may not be able to log in to GNOME Shell with SELinux enabled. Login will fail with the "Oh no! Something has gone wrong" error screen that GNOME pops up if a component is crashing repeatedly.

The issue is caused by gnome-settings-daemon crashing when it encounters a color profile with an incorrect SELinux context: the correct context for color profiles changed between Fedora 15 and Fedora 16, but the upgrade process does not re-label existing profiles.

To resolve the issue, boot to a different desktop or to a console and run the command su -c 'chcon -R -t icc_data_home_t ~/.local/share/icc'. After doing this, GNOME login should work correctly.

[edit] Starting GDM (login manager) fails on x86_64 systems after upgrade from Fedora 15 due to i686 caribou package being installed

link to this item - Bugzilla: #741075

Several users have reported that, after upgrading from the x86_64 version of Fedora 15 to Fedora 16, GDM (the default login manager) failed to start, displaying the "Oh no! Something has gone wrong" error screen. This issue is due to the i686 (32-bit) Package-x-generic-16.pngcaribou package being installed during the upgrade, instead of the x86_64 version.

An updated caribou package has been submitted to the updates-testing repository for testing. Users experiencing this problem are encouraged to test this update and report to Bodhi whether it solves the problem. To test the update, enable the updates-testing repository while upgrading from Fedora 15 to Fedora 16.

If you have already been affected by this problem, simply installing the x86_64 version of the Package-x-generic-16.pngcaribou package - su -c 'yum install caribou.x86_64' - should resolve it.

[edit] GNOME Shell uses excessive CPU time with System Monitor extension installed

link to this item - Bugzilla: #748241

When the Package-x-generic-16.pnggnome-shell-extension-systemMonitor package - the System Monitor extension for GNOME Shell - is enabled, GNOME Shell can come to consume an excessive amount of CPU time. The issue can be worked around temporarily simply by restarting the Shell (a quick way to do this is to hit alt-f2 and enter the command as the single character 'r'). There is no known permanent workaround besides removing or disabling the extension.

[edit] Setting back system time breaks boot

link to this item - Bugzilla: #748920

If you set back your system time for more than one day into the past, Fedora will not boot on next system restart. It will complain about your disk mount time being too far in the future. Typically the error message looks like this (dracut shell):

/dev/mapper/VolGroup-lv_root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
 (i.e., without -a or -p options)
dracut Warning: e2fsck returned with 4
dracut Warning: /dev/mapper/VolGroup-lv_root: Superblock last mount time (Tue
Oct 25 14:40:08 2011,
dracut Warning: now = Sun Sep 25 14:41:50 2011) is in the future.
dracut Warning: *** An error occurred during the file system check.
dracut Warning: *** Dropping you to a shell; the system will try
dracut Warning: *** to mount the filesystem(s), when you leave the shell.

Or it can look like this (emergency mode shell):

systemd-fsck[605]: /dev/sda2: Superblock last mount time (Tue Oct 25 10:40:12
2011,
systemd-fsck[605]: now = Sun Sep 25 10:41:59 2011) is in the future.
systemd-fsck[605]: /dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
systemd-fsck[605]: (i.e., without -a or -p options)
[   13.652068] systemd-fsck[605]: fsck failed with error code 4.
Welcome to emergency mode. Use "systemctl default" or ^D to activate default
mode.
Give root password for maintenance
(or type Control-D to continue):

You have to use the shell to correct the filesystem that is claimed to be "inconsistent". If you have multiple partitions you may need to do the following procedure for all of them. The easiest approach is:

  1. Note that partition name in the error message (/dev/mapper/VolGroup-lv_root and /dev/sda2 in our examples).
  2. Run this command
    fsck <partition name>

    For example:

    fsck /dev/sda2
    and confirm you want to fix it.
  3. Run
    reboot

It may happen that you are presented with the error message, but you are not given any emergency shell. In that case please boot from the Fedora installation media and select Troubleshooting -> Rescue a Fedora system. After the rescue tool mounts your system disks you can just reboot, everything should be corrected.

[edit] Cannot send files via Bluetooth

link to this item - Bugzilla: #753617

Due to changes in the kernel bluetooth interface, you will not be able to transfer files to another device via Bluetooth in Fedora 16. There is no known workaround for this issue besides transferring the files to the device in some other way (e.g. via USB cable or wifi).

[edit] Abrt will not catch crashes after upgrade from a previous Fedora release

link to this item - Bugzilla: #749603

When upgrading from a prior Fedora release, the abrt-ccpp service is not enabled. This will prevent the abrt program from catching software crashes, which will prevent users from reporting bugs. A workaround is to enable and start the service manually. You only need to run these commands once: on future system boots, the service will now start.

# systemctl enable abrt-ccpp.service
# systemctl start abrt-ccpp.service

[edit] GNOME Shell crashes when using the alternate-tab extension

link to this item - Bugzilla: #698939

If you install and enable the Package-x-generic-16.pnggnome-shell-extension-alternate-tab extension for GNOME Shell, you will likely find that the Shell often crashes when you use alt-tab or ctrl-tab. This problem is caused by bugs in the extension.

At present there is no known workaround for the problem except for removing or disabling the extension. We do not recommend the use of this extension in Fedora 16 at the present time.