Saturday, January 26, 2013

TOOL SOURCE Linux CVEs


http://fedoraproject.org/wiki/Bugs/Common
tallation issues

Media consistency check can't be skipped, its output is unhelpful

link to this item - Bugzilla: #891548 Bugzilla: #891551The installation medium is checked for errors during boot be default. The consistency check says Press [Esc] to abort check., but if you try to skip it, lots of errors are printed and you end up in an emergency mode. Use reboot command or hard-reset the machine. It is recommended to let the consistency check finish, but if you really want to skip it, boot the installer using Install Fedoramenu item instead of Test this media & install Fedora.If your media is corrupted, you will also receive lots of cryptic messages and end up in an emergency mode. The output will contain It is not recommended to use this media somewhere in the middle (see screenshot). The flood of error messages might be confusing, but the main message is clear - your media was either corrupted in the download process (check its checksum) or in the burning process (try to burn it again).

Automatic login does not work on Desktop Live image

link to this item - Bugzilla: #854722When you boot the Fedora 18 Desktop Live image, you will not be automatically logged in to the desktop, as was the case in previous releases and as is intended. The login screen will appear with 'Live System User' as the only available user account: clicking this user will log you into the live system, which will then work as usual. There are no further consequences of this bug beyond the minor inconvenience.

Text installation sets POSIX locale

link to this item - Bugzilla: #891379If you perform the installation in the text mode, the system will have a POSIX locale enabled by default. That can break some programs that expect unicode-enabled environment. You can change the default locale after installation by editing /etc/locale.conf and setting LANG="en_US.UTF-8" (or other locale).

Installer crashes after selecting "Malay (Malaysia)" language

link to this item - Bugzilla: #893026If you boot the installer and select Malay (Malaysia) at the language selection screen, the installer crashes immediately after clicking the Continue button. The work-around is to start the installer in English and add Malaysian keymap manually (if you need it). In the installed system you can then change the default language using graphical configuration tools in your desktop environment or by editing /etc/locale.conf. The Malaysian translation of the Fedora 18 installer is in any case very very incomplete, so in practice you would need to be able to read English to install anyway. We apologize to Malaysian-speaking users for this error.

Installer does not automatically set up multiple keyboard layouts and switch command

link to this item - Bugzilla: #892110Keyboard layout configuration has changed substantially between Fedora 17 and Fedora 18. This may catch speakers of some languages off guard.In Fedora 17 and earlier versions, Fedora had sophisticated handling of a fairly small range of languages and keyboard layouts. The installer, and Fedora's keyboard configuration tool, were aware of the 'correct' configurations for a given range of keyboard types. In particular, the installer was aware of several types of keyboard for which it should configure both a 'native' layout and the U.S. English layout, and a command to switch between them. This applies to keyboards such as Russian (and many other Cyrillic keyboards) where the 'native' layout does not provide the ability to input Roman characters (and other commonly-used ASCII characters). Users of such layouts are used to switching between their native layout and the U.S. English layout to input Roman characters.Maintaining this sophisticated handling was a development burden, though, and it made it hard to offer the full range of available keyboard layouts, and it did not offer the ability to configure more 'unusual' combinations of layouts. So in Fedora 18, the 'sophisticated' handling has been removed, and the installer now simply offers a fairly generic interface that offers all available keyboard layouts and lets you enable as many of them as you like.On the very first screen of the installation process, where you select your language, there is a checkbox marked "Set keyboard to default layout for selected language". It is natural to assume that this checkbox does something similar to the previous 'sophisticated' behaviour: however, it does not, exactly. It just uses a fairly simple algorithm to try and pick the single keyboard layout whose name most closely matches the name of the language you selected. It will never configure more than one layout. So picking the Russian language and checking this box will only configure the Russian layout, it will not also configure a U.S. layout. This applies to all layouts where it is 'normal' to also configure the U.S. layout: just checking that box and not performing any further keyboard configuration is likely to give you a result you do not want.If you need more than one layout, whether you check the box or not, be sure to visit the Keyboard screen in the installer and add any additional layouts you need. Also make sure you configure a command to switch between layouts: you may well need to use it during the user creation stage of installation. Previous Fedora releases automatically configured 'both shift keys' as the keyboard command to switch layouts, but in Fedora 18 you can choose between several commands in the Keyboard screen.If you become stuck at the user creation stage without access to the U.S. layout, you can try and workaround the problem from a text mode boot, but it may be simplest to restart installation and make sure you add the U.S. layout and a layout switch command.

Keyboard layout testing and selection during installation does not work as expected

link to this item - Bugzilla: #854557On the Keyboard screen during Fedora 18 installation there is a text entry box labelled 'Test the selected layout below:'. This label is confusing. The box does not let you test the layout currently highlighted in the list on the left hand side of the screen, but the layout that is active. There is no indicator for the active layout, so it is not easy to know which layout is active. The layout that was in the list when you first entered the screen will stay active until you do one of two things: remove it, or configure a layout switch key combination and use it. So if the English (U.S.) layout was in the list when you first entered the screen, if you add the French (French) layout, it will not be active. If you highlight it in the list, it will not be active. If you move it to the top of the list, it will still not be active. But if you remove the English (U.S.) layout, French (French) will become the active layout. Alternatively, if you add French (French), then click the 'Options' button, pick one or more keyboard layout switch combination(s), click 'OK', and then press a layout switch combination you just configured, French (French) will become active: press it again, and English (U.S.) will be active again. This should be reflected in the test box.As there is no indication of the current active layout throughout installation, if you are configuring multiple layouts, we recommend you ensure the layout you wish to use for the rest of the install process is active using the test box before leaving the Keyboard screen, and then do not switch layouts until installation is complete.

DVD install does not include LibreOffice by default

link to this item - Bugzilla: #880653Though it has historically been part of the default Fedora package set, the LibreOffice office suite is not included in a default DVD or network installation of Fedora 18 (it is included in the Desktop live image installation, though, where it was not before). This is partly an oversight and partly due to technical limitations which prevented it being included by default but de-selectable for those users who do not want it.If you wish to have LibreOffice installed as part of your DVD or network installation, make sure to enter the Software Selection screen and check the LibreOffice option on the right-hand side.

Disk encryption with national keyboard layout often doesn't work

link to this item - Bugzilla: #743281The 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.

Insufficient system memory during installation might seem as a packaging error

link to this item - Bugzilla: #893987The required amount of system memory (RAM) for installation might vary depending on the installation options you choose. If you receive an error message during installation saying There was an error installing the xyz package. This is a fatal error and installation will be aborted. (screenshot), there is some chance that this error occured due to insufficient system memory. Either increase the system memory, or set up a larger swap partition and repeat the installation.

Windows 8 installed in UEFI mode are not present in the Fedora bootloader menu

link to this item - Bugzilla: #873207If you install Windows 8 in the UEFI mode and then install Fedora 18 into dual-boot, Windows will not be present in the bootloader menu (GRUB) that appears right after your computer starts. This is not a bug per se, UEFI systems handle operating system selection in a different way. Your computer should support a hotkey that triggers an OS selection dialog before GRUB even loads. In this dialog you should see the Windows system. Your OS preference should also be configurable in BIOS.

UEFI boot of Fedora 18 CD or DVD disc on Mac hardware falls to a prompt

link to this item - Bugzilla: #893839If you boot a Fedora 18 CD or DVD disc - an actual silver disc - via UEFI on an Apple Mac system, instead of reaching the normal boot menu and hence the Fedora installer, it will drop to a bootloader prompt.This bug does not affect boot of Fedora 18 CD or DVD images written to a USB stick using one of the supported methods, so the easiest way to avoid this bug on Mac hardware is simply to boot the install from a USB stick rather than an actual optical disc. If you must use an optical disc for some reason, you can cause the installation to proceed from the prompt by entering this command: configfile (cd0,apple3)/EFI/BOOT/grub.cfg.

Partitions on Solaris 10-formatted disks may appear as free space to installer

link to this item - Bugzilla: #892269It can difficult to install to free space within an LVM volume group (VG) using the custom partitioning mode of Fedora 18.This applies whether you begin the partitioning process with free space within an existing volume group, or you plan to remove or shrink existing LVs (but not to remove the entire volume group) as part of your partitioning approach.When you come to create the new mount points, after having scheduled removal or shrink of existing LVs if necessary, you will find that the installer's free space counter does not account for the free space within the existing VG - it will show zero, or a very small number representing the available space outside the VG. If you then create a new volume and leave its size unspecified, the installer will create a new LV within the existing VG, but only of the size it believed was available as 'free space' (so, uselessly tiny). You will not be able to make the new LV any larger, even though there really is space available within the VG.It is possible to make this work, however. What you have to do is specify the correct intended size for each new volume as you create it. The installer will allow this. So if you have 100GB of free space within your existing VG, you could, say, create a / mount point and specify its size as 30GB, then create a /home mount point and specify its size as 70GB. The installer will allow this and will create these as LVs within the existing VG. Note that you will not be able to increase the size of an LV after you 'create' it, within the installer - even if there really is space available within the VG. However, you get as many tries as you like, when dealing with this bug - if you get it wrong, you can just remove the LVs and try again, as in the new installer, no operations are actually performed until you complete the partitioning step and start the installation. All the 'creations' and 'removals' are just planned operations. So don't be afraid to fiddle around until you nail it.

Crash when installing to disks containing identically-named LVM volume groups (VGs)

link to this item - Bugzilla: #887539Testing indicates that the Fedora 18 installer may crash if you attempt an install to a system containing two or more identically named LVM volume groups (VGs) - even if you choose to delete one or both as part of the installation process.If you are affected by this problem, there are several possible workarounds. Most simply, if you only need to install to one of the disks containing identically-named VGs, you can leave the other disk(s) out of the installation target disk set (selected on the first page of the Installation Destination spoke), or temporarily remove the other disk(s) from the system. If you need to keep the offending disks connected and use them as installation targets, you will need to remove or rename one of the VGs using another tool before beginning the Fedora installation.

Install to small btrfs volume may fail or crash

link to this item - Bugzilla: #893331, Bugzilla: #893758Two related bugs have been discovered in Fedora 18 installation when installing to a small btrfs volume. The Fedora installer attempts to check whether your planned disk layout will be big enough to accommodate your chosen package set, but this calculation is not strict enough for btrfs installations: it will allow installation to proceed in some cases even if there is actually not quite enough space available for the installation to succeed. This affects only quite a narrow 'band' of cases - for instance, in the reported test system, the installer would refuse to install to a 7GB disk due to lack of space, and install to a 9GB disk would succeed. An 8GB disk would trigger the bug.To ensure you do not run into this problem, if installing to a btrfs volume, try and ensure there will be sufficient space for the installation to succeed. You are unlikely to have trouble unless you are installing to a fairly small disk.If you do encounter this bug, you will find the failure case can be quite unpredictable - this is a result of the other related bug, which is that btrfs' behaviour on running out of space can vary, and result in different effects in the Fedora installer. It is very likely that it will crash in some way, but the precise nature of the crash may vary.

Installer boot options documentation is outdated

link to this item - Bugzilla: #864468There are currently two pages documenting the boot options of the installer of Fedora 18: Anaconda Boot Options and [1]. Both of them are at least partly outdated. We are hoping to update these pages soon, but in the mean time you can try to look at both and take a guess which of the boot options are current and which are obsolete, if you need to use them. Of course, if you are able to follow the source code, you can check out the anaconda sourceand derive the currently-valid options from that.Some old anaconda options - notably, several of the network configuration options - have been replaced by Dracut options, which are documented at Dracut/Options.

Installation source shows 'Nothing selected' for network installation

link to this item - Bugzilla: #873468It is possible that the Fedora 18 installer may fail to correctly set the default remote package source on occasion when booting the network installation image. Instead of showing 'Closest mirror' and 'GNOME Desktop', the 'Installation Source' and 'Software Selection' entries on the installer hub/home screen will show 'Nothing selected'. This will prevent installation from starting until it is rectified. Several possible causes of this bug were eliminated during development of Fedora 18, but it appears the bug may still occur in some rare cases.If you are affected by this bug, to work around it, you can either just reboot (it will often succeed on a second try), or enter the 'Installation Source' spoke, change the remote source URL to any specific address at all (it does not have to be valid), return to the hub screen, return to the 'Installation Source' spoke, change the source back to 'Closest mirror', and return to the hub screen once again.

Network installation incorrectly refreshes installation source for WiFi or slow network card

link to this item - Bugzilla: #892665If you boot the network installation image (netinst.iso) on a machine with just a wireless network connection, or a very slow wired network card, the installer may say Nothing selected below the Installation source icon and it will be marked as a problematic state (see screenshot). However, just opening the Installation Source dialog and ensuring that Closest Mirror is selected doesn't help. You need to manually trigger metadata refresh by first changing the network source to e.g. http://abc (hit Done), and only then switching it back to Closest Mirror.You can also use updates.img from http://rvykydal.fedorapeople.org/updates.nothingselected.img to fix this issue. Read Anaconda/Updates.

Cannot connect to WPA / WPA2 Enterprise network during installation

link to this item - Bugzilla: #892896The Fedora 18 installer is not capable of connecting to WPA / WPA2 Enterprise wireless networks for network installation. This is a temporary limitation and this capability should be added for future Fedora releases
Installer can become apparently 'stuck' in custom partitioning mode due to window focus problems

link to this item - Bugzilla: #875921Occasionally, the Fedora 18 installer can become apparently 'stuck' in custom partitioning mode, after opening several subsidiary dialogs. The typical manifestation of this bug is that you hit the button to add a new mount point or to change the properties of a mount point, the subsidiary dialog does not appear, and the installer seems to stop responding: the cursor will still move and change shape depending on what it is hovering over, but clicks will appear to have no effect.This is a window focus problem - the dialog has in fact appeared, but is behind the main anaconda window but still focused and taking all mouse/keyboard input. The issue can be resolved quite simply by pressing the Esc key, which will close the rogue dialog. This will restore normal behaviour. The bug has no further consequences.

Installer crashes if you need a network installation and have a local kickstart and a slow network card

link to this item - Bugzilla: #892669If you perform a kickstarted network installation and serve the kickstart locally (from a local partition, not from online location) on a machine with a slow network card, the installer will crash if it starts earlier than the network is set up.The solution is to serve the kic


--
Sent from hacked phone

No comments:

Post a Comment