As with any release, there are still issues and bugs that may not have been resolved. This page documents those that may cause inconvenience and where possible details how they may be worked around.
It is recommended that you read the latest release notes on our wiki.
- 1 Authentication
- 2 Booting Live DVD/USB
- 3 Partitioning: General Information
- 4 Local Network Sharing
- 5 Parental Controls
- 6 Language Input Methods
- 7 Admin Privileges: The wheel group
- 8 Black Screen at Boot
- 9 Other Graphical Boot Issues
- 10 Backlight Issues
- 11 Boot to a dracut prompt
- 12 KMail Issue
- 13 Calamares Installer
- 14 Kdenlive (Video Editor)
- 15 Contact, Bug Reporting, Discussion
- 16 Helping the Project
We now use pam for authentication, but there are now fewer inconsistencies. Most programs requiring authentication will authenticate with the primary user password (the primary user is the first user created during install), other users will require the root password. Programs started from the command line by the primary user will still require the root password.
Booting Live DVD/USB
If you have a problem booting the live image with some hardware please report a bug detailing your hardware and any observations that you make if you are affected by this problem.
Partitioning: General Information
We recommend the the use of the KDE Partition Manager this is similar to that used in Calamares during the install.
Please note that due to the adoption of systemd the use of a separate /usr partition is no longer possible. It is still permissible to have a separate /usr/local partition which can be mounted on /usr/local.
If you wish to use diskdrake the custom partitioning tool to divide up a hard disk/s be aware that there is a minimum size requirement a root partition that contains the /usr directory of at least 5.0Gb, otherwise the partition manager will not function correctly.
Workaround: If you receive an error message stating that the partition is smaller than the minimum requirement then do not try to resize it as this will fail. Please use the auto-allocate function which will automatically create a partitioning scheme for you, which you may then delete or change to suit your own requirements. This will clear the error.
Local Network Sharing
The firewall service, firewalld is now enabled by default, if required it may be disabled via the OMA Contol Centre under the system entry. Additionally to aid local networking both nfs and samba ports are open over and above the usual ssh and other services.
Parental Controls are currently non-functional.
Workaround: None available at the moment.
Language Input Methods
Support has been provided for the Japanese and Chinese languages these need fctix, but there seems to be an issue that input method cannot be used with LibreOffice. A known workaround is to remove libreoffice-kde4 and install libreoffice-gnome. Detailed information is available in the bug report: Bug #1770.
Admin Privileges: The wheel group
Please note that the first user created on the system is part of the wheel group, which allocates special privileges that are usually only allocated for the root user. Users in wheel can bypass certain password dialogues to change system settings.
Workaround: This is intended behaviour. If you wish to disable this, remove users from the wheel group.
Black Screen at Boot
There is an issue with some systems that have two different graphics adapters but only one of them is operational. Typically this is a Nvidia GPU combined the either Intel or AMD/ATI. Due to the automated nature of driver selection in modern systems if the non-functional GPU is automatically selected then X will load the matching driver. Thus the working GPU never gets setup resulting in a black screen. We have recently added a new boot command line option to allow an Xorg driver to be blacklisted thus allowing the correct driver to be detected. It is also necessary to prevent the driver from loading in the initrd if you wish to have a graphical output from the alternate graphics adaptor
To use this feature you must edit the grub2 command line. You can do this by selecting your desired boot option and then pressing TAB. To the end of the line add the following:
rd.driver.blacklist=<driver to blacklist> xorg.blacklist=<driver to blacklist>
Usually it is the nouveau driver that needs to be blacklisted. Other likely ones are ati radeon amdgpu or i915.
To determine which driver needs to be blacklisted is probably best achieved by booting the system to a text mode and checking which driver has been loaded at boot time. A procedure for doing this is detailed below. In some circumstances this may not be possible and you will need to resort to your motherboard/Graphics card specifications or trial and error. It will be necessary to permanently add the line to the grub2 command line that boots the installation. This is described below.
There are other circumstances where a black screen may be encountered. For example if you wish to use the proprietary driver for your graphics adapter or where your graphics card is too new to be supported by the current drivers. To do this it may be necessary to inhibit the kernel mechanism that loads the free drivers. In these circumstances adding
to the kernel command line will normally be enough to allow installation of the OS or running with the manufacturers drivers .
If necessary the command may be added permanently by editing /etc/default/grub at the GRUB_CMDLINE_LINUX_DEFAULT label and adding the required command. Then run
To boot to text mode:
1: Boot from the DVD/USB stick and at the grub selection screen select the livecd option and press TAB. Edit the grub command line by and add the command
to the end and boot the machine. This will bring you to a command prompt where you can login.
2: Login as root and then type lsmod | less and observe the output. Look for the loaded graphics driver by finding the drm entry the graphics driver will be listed here. It will be typically nouveau, radeon or i915 (there may be others). The name used here will be the name to add to the xorg.blacklist= parameter
Other Graphical Boot Issues
Intel Users with older motherboard based Intel graphics hardware which may find issues when trying to use alternative graphics hardware. It is known that nVidia hardware does not start up properly in this configuration. Usually the result is a black screen. There are a number of things that can be tried but the best combination so far is to disable the Intel card from the command line using "i915.disable_display=true" and pre-loading the nouveau driver with "rd.driver.pre=nouveau" and adding "nomodeset". This may give a low res graphical screen. If you do no get a graphical screen use all the above options and boot into text mode (see above) by adding systemd.unit=multi-user.target to the end of the grub boot line. Once in text mode as root add the nouveau driver to /etc/modprobe.preload.d/modprobe-preload.conf. You will still need "i915.disable_display=true" and "nomodeset" on the grub command line but this should give a graphical boot but still at low res. Hopefully updates will bring a resolution to this problem.
There are some machines with Intel GPU's (Netbooks particularly) that may still give a black screen even with everything set up correctly; this is due to the screen backlight logic being inverted. This may be fixed by adding i915.invert_brightness=1 parameter to the boot command line. This may be needed in addition to the xorg.blacklist= parameter.
Boot to a dracut prompt
If this happens all is not lost. This may be indicative of the lack of disk driver for your hardware. Dracut indicates that it has produced a bug report which you can copy to a memory stick and then attach to a bug report you will need to mount your memory stick. Assuming it is FAT formatted then plug it in and type 'dmesg' the device name of your memory stick should be visible it will be in the form /dev/sd<x> the bracketed x will vary depending on how many drives have been found on your machine if for example you have one other drive then the entry might read /dev/sdb. Create a new directory /mnt with 'mkdir /mnt' then type 'mount -t vfat /dev/sdb1 /mnt' and the drive should be mounted. (Note the 1 added to the device name). You should then be able to copy files to your memory stick with 'cp <files> /mnt/' . Please take the trouble to report this type of problem as receiving these reports is the only way we can improve our distribution.
Unfortunately users are reporting issues with KMail. It is believed that KMail is broken upstream. (Some say badly broken, perhaps depends on how one uses an e-mail client).
If you experience difficulties using KMail it would be wise to try Thunderbird or some other e-mail client. There are other e-mail clients available in 'Install and Remove Software>Networking>Mail'.
What is reported by OMV users is:- Setups that use POP3 and local folders combined with filters and large mail traffic will find that kmail2s database database (Akonadi) is generating duplicate mail headers that don't have a message body. This prevents kmail from fetching ANY bodies even if they are not duplicates. When duplicates are present the akonadi clean up tool cannot fix them. The only fix is to then user has to completely (manually) rebuild Akonadi database. Unfortunately as soon as filters start acting on incoming mail the duplicates soon recur and kmail is broken again.
One can see that both of the bug reports have been around for a long time but are still active. This problem may be version dependent.
On some systems the standalone versions of Calamares do not start; if you experience this issue please report a bug. The problem does not seem to occur if Calamares is launched from the live system.
The Calamares installer supports EFI installs but not secure boot. If your system has an existing fat32 partition that is under 330MB Calamares will give and error message and warn that installation might fail. The reason for this is that the theoretical minimum size for creating a FAT32 partition is around 330Mb. If you wish to keep your existing partion then mark it FAT16 instead and the error message will go away and the install and boot proceed normally. Alternatively you can increase the size of the partition to >330Mb and the install should proceed normally with FAT32 selected as the filesystem.
Dual Installs (EFI and BIOS booting on the same disk) and BIOS install on GPT partitioned disks.
Please be aware that if you wish to perform a BIOS install on a GPT formatted disk you must ensure that the disk contains a small partition => 2Mb for grub to install the bootloader into. This partition can be located before or after the EFI partition. It does not need to be formatted but must have the "bios-grub" flag set.
i586 ISO UEFI
The i586 spin supports 32 bit UEFI this has not been tested as Virtual Box have discontinued support for it so your mileage may vary.
Kdenlive (Video Editor)
The Video Editor Kdenlive works but upon closing there is a dialog window about 'Segmentation Fault'. This is a known issue and being worked on but does not affect the overall operation of the program.
Contact, Bug Reporting, Discussion
You are invited to discuss this release on our:
Please report bugs to our OpenMandriva Issue Tracker.
For us to get the most information about your situation, it is a wise idea to install
Then, as root:
will generate an archive containing system information that can be attached to a bug or mailed to a maintainer. This will greatly help in the diagnosis of the reported issue. For more information about bug reporting you can read How to report a bug.
Helping the Project
The OpenMandriva development teams (Cooker & QA) are always looking for new contributors to assist in creating and maintaining packages and to assist bugfixing and testing. You are welcome to join us and help us in this work which is not only rewarding but also tremendous fun!
If you feel that your talents do not lie in the realm of software, then the OpenMandriva Workshop group, which is made up from the artwork, documentation, translation and Communication teams, is always open for the submissions of artwork and translations. New contributors who would like to help with these wide-ranging tasks should see the wiki for more details, and to learn how to join! Alternatively you may use our Forum.
It also costs time and money to keep our servers up and running. If you can, please donate to keep the lights on!
One can see that both of the bug reports have been around for a long time but are still active.