From Mandriva Community Wiki
This page contains the Errata for Mandriva Linux 2009. This means it contains information on known problems with Mandriva Linux 2009 and, where available, how to fix, avoid or work around them. You should also see the Release Notes, which contain more general information on the Mandriva Linux 2009 release.
Errata for earlier Mandriva Linux releases
Other errata pages are also available for older versions:
Testing Candidate Updates
When an issue in Mandriva Linux 2009 is identified, the maintainer of the package concerned may build a package he believes will fix the bug, and upload it to a certain Mandriva software repository named /main/testing which is dedicated to testing potential fixes for such issues. This package can then be tested by users affected by the issue and by the Mandriva quality assurance team. If this testing determines that the package resolves the issue and does not cause any new ones, the package will be issued as an official update which will be provided to all Mandriva Linux 2009 users via MandrivaUpdate.
If you are affected by an issue for which a candidate update package is available and you would like to help test the candidate package, you may configure your system so the Mandriva package management tools will recognize the /main/testing repository as a source of installable packages. For instructions on how to do this, please see installing and removing software (advanced use: backports and candidate updates).
There is also a /contrib/testing repository which performs the same function for packages in the /contrib section (although please note that we do not guarantee issues with /contrib packages will be fixed, the maintainers of each package may choose whether to issue updates at their own discretion). Configuring this repository is covered on the same page.
Updates for packages in the /main, /non-free and /contrib sections of Mandriva Linux can be installed using Mandriva Update. You can run Mandriva Update from the Mandriva Control Center by navigating to the Software Management tab and clicking on the link labelled "Update your system". Unless you disable it, you will also be notified of updates by the Mandriva Online update notification system, which displays an icon in the system tray to notify you when updates are available.
This section contains issues that have been resolved by official updates.
NVIDIA proprietary driver does not work with kernel-server
The proprietary NVIDIA driver shipped with Mandriva Linux 2009 did not work with the kernel-server kernel. This problem was most obvious on recent, powerful desktop machines with 4GB of RAM or more; kernel-server is installed on all systems with 4GB of RAM or more in order to make sure all the RAM is accessible. An updated set of nvidia-current packages, nvidia-current-177.70-2.3mdv2009.0, was released through the official update channels on October 16th, 2008 that resolves this issue. Use MandrivaUpdate to fetch and install this update.
Missing module dependency information slightly increases boot time
See also update advisory MDVSA-2008:224. A small bug in the kernel package included with Mandriva Linux 2009 slightly increased boot time. You could work around this by running the command depmod, as root. This should reduce boot time by around two to three seconds. An updated set of kernel packages, kernel-18.104.22.168-1mnb-1-1mnb2, was released through the official update channels on November 4th, 2008 that resolves this issue. Use MandrivaUpdate to fetch and install this update.
Installing VMware on Mandriva fails due to wrong GCC version used to compile kernel
See also update advisory MDVSA-2008:224. In the i586 version of Mandriva Linux 2009, the kernel was built with an earlier GCC version than the one included in the final release, so VMWare (and possibly other third party applications which use kernel modules) would refuse to build their kernel modules when you attempted to install them on Mandriva Linux 2009. Please note that this applies only to installing a VMware application on Mandriva Linux 2009, not installing Mandriva Linux 2009 as a VMware guest. An updated set of kernel packages, kernel-22.214.171.124-1mnb-1-1mnb2, was released through the official update channels on November 4th, 2008 that resolves this issue. Use MandrivaUpdate to fetch and install this update.
Eee systems do not shut down correctly
See also Bug #44752 and update advisory MDVSA-2008:224. Several users reported that Eee systems including at least the 701 did not shut down correctly. The shut down process goes all the way to the end and the screen is blanked, but the power light is not turned off and the system is not properly powered down. To work around this issue, add this line to the top of the file /etc/init.d/halt:
An updated set of kernel packages, kernel-126.96.36.199-1mnb-1-1mnb2, was released through the official update channels on November 4th, 2008 that resolves this issue. Use MandrivaUpdate to fetch and install this update.
No network response (TCP packet header ordering issue)
See also Bug #43372 and update advisory MDVSA-2008:224. Prior to version 2.6.27, due to a bug, the Linux kernel did not include the timestamp field in TCP packets. Now this bug has been fixed, and kernel 2.6.27 (and later) does include this field. However, in adding this field, the order of fields within the TCP headers was re-arranged. It appears that some networking hardware (mainly routers) expects these headers to be in a particular order, and does not work if they happen to be in a different order. An updated set of kernel packages, kernel-188.8.131.52-1mnb-1-1mnb2, was released through the official update channels on November 4th, 2008 that resolves this issue. Use MandrivaUpdate to fetch and install this update.
If this issue seems to be preventing you from installing the updates in the first place, you can run this command, as root: sysctl -w net.ipv4.tcp_timestamps=0. It should resolve the problem temporarily, allowing you to access the internet and install the updates. When you reboot to the updated kernel, the problem should be permanently resolved.
Continuous loud noise from the sound device
See also Bug #44703 and update advisory MDVA-2008:168. Several users reported that as soon as the sound driver is loaded on Mandriva Linux 2009, a loud unpleasant noise is played continuously over the system speakers or headphones. This can be fixed by running a mixer, like kmix or alsamixer, and disabling / muting the Analog Loopback channel(s). An updated sound-scripts package, sound-scripts-0.56-1.1mdv2009.0, was released through the official update channels on November 7th, 2008 that resolves this issue. Use MandrivaUpdate to fetch and install this update. As noted in the advisory, as this issue affects configuration data, the change will not be applied automatically. You can either apply the change manually as described above, or run the command reset_sound with root privileges after installing the update.
Evolution cannot send messages when using an Exchange server
See also Bug #44908 and update advisory 2008:186 and update advisory 2008:186-1. A bug in the evolution package provided with Mandriva Linux 2009 prevented outgoing mails from being sent when the outgoing mail server was an Exchange server (via the evolution-exchange plugin). Evolution appeared to be sending the mail, but the operation never completed. An updated set of evolution packages, evolution-2.24.2-1.1mdv2009.0, was released through the official update channels on December 1st, 2008 that resolves this issue. Use MandrivaUpdate to fetch and install this update. Please note that the initial update was incorrectly built, and would cause Evolution to crash on startup. A fixed set of updated packages, evolution-2.24.2-1.2mdv2009.0, was issued the following day to resolve this problem.
Problems after doing an in-line upgrade from 2008 Spring to 2009
A new feature with 2009 is the ability to do a graphical in-line upgrade, via the Mandriva Online update notification system, from 2008 Spring to 2009. 2008 Spring users started being notified of a new release, and offered an upgrade to it, on October 10th, 2008. Users who attempted to use the system at this time may have found the upgrade did not seem to work correctly: on rebooting into the 'upgraded' system, it may be impossible to log in graphically, or various things may seem to be broken or missing. This is because the process was not made robust enough against several potential problems that could occur during the upgrade, including busy mirrors causing packages to fail to be downloaded (and hence upgraded), or there not being enough disk space on the system successfully to complete the upgrade.
If you are suffering from a problematic upgrade, the following procedure may well resolve it. Press ctrl-alt-F1 to get a console log in screen. Log in as root, and run this command:
urpmi --auto-update -v
and follow it through. It should then upgrade the packages that were not upgraded during the initial upgrade. If the process indicates that some packages were still not able to be upgraded due to mirror problems, run the command over, until all possible upgrades have been correctly installed. Once this is complete, type reboot to restart the system. The upgrade should now be correctly completed.
Periodic freeze of the graphical system
See also Bug #42833. Some users of Mandriva Linux 2009 have experienced a bug where the system freezes periodically when running in graphical mode. When this occurs, it is still possible to use the ctrl-alt-F1 key sequence to access a text console. This issue is caused by a bug in the kernel DRM modules causing the X.org graphical server to enter an infinite loop. To diagnose this issue, examine the X.org log file /var/log/Xorg.0.log, from the text console after the graphical desktop freezes. The presence of the following recurring lines is the indication of this bug:
[mi] EQ overflowing. The server is probably stuck in an infinite loop. [mi] EQ overflowing. The server is probably stuck in an infinite loop. [mi] EQ overflowing. The server is probably stuck in an infinite loop.
To work around this issue, at the Mandriva Linux 2009 boot menu, select the option labeled linux-nonfb, rather than the default option. You can set this as the permanent default in the Mandriva boot configuration tool, accessible from the Mandriva Control Center, in the Boot tab, labeled Set up boot system. Doing this will disable the video framebuffer, which means you will not see the graphical boot and shut down screens.
Boot pauses indefinitely at various points until a key is pressed
See also Bug #44342. On several systems, including the Sony Vaio PCG-GRT-815E, the boot process will pause indefinitely at several points until you press a key. When a key is pressed, it will continue. If you press a key each time it pauses, eventually the boot will complete without problems.
This issue is currently under investigation, and a fix may be provided in a future official kernel update. It may be possible to work around this problem by adding the following lines to the file /etc/modprobe.d/blacklist-mdv:
blacklist thermal blacklist processor
or by using the following kernel parameter:
Kernel parameters can be added using the Mandriva boot configuration tool, available in the Mandriva Control Center.
Resume from hibernation fails with a blank screen
Several users have reported that when they hibernate their system (suspend to disk) and then later try to resume it, it shows the Mandriva boot screen for a short time and then hangs at a blank screen.
There are many reasons for a laptop not resuming correctly even if most of the kernel modules (since 2.6) have been revisited in order to allow correct resuming. Waking up the video is another challenge and many quirks are available for various laptops and, as Mandriva uses
hal, a good reference is http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-index.html . Please report there if your laptop is not mentioned in the quirks (and you found a solution).
The easy but leasy workaround is to click on Escape just after the colored splash screen. If your resuming process works after that early click it means, according to http://fixunix.com/mandriva/544016-cant-kill-splash-screen.html , that the cause of the hang is
splashy . The standard way should be to change the default
splash=silent in your boot loader (lilo or grub) to
splash=verbose, but because of a bug somewhere any mention of the word
splash in the boot options launches
splashy. Thus the current workaround consists in suppressing any
splash . And I suppressed any splash word from my lilo.conf lines
append="resume=UUID=xxxxx splash=verbose" vga=788
- to :
- As you can see, we kept the framebuffer vga=788 because it was not a framebuffer freeze. And during the resume process you will get the other grey Mandriva splash screens which hide the verbose resuming.
For some users, this issue can be worked around by disabling the framebuffer-based graphical boot system. If your boot menu has an entry labelled 'linux-nonfb', you can boot from this entry to achieve this. Otherwise, you can do it from the Mandriva Control Center. Go to the Boot tab and click Set up boot system. On the first screen, just click Next. On the second screen, make sure the default entry is selected, and click Modify. Look through the Append line. If there is already an entry of the form vga=788 - the number may be different - change it to vga=normal. If there is no vga= entry, just add vga=normal to the end of the line. Then click OK. Then click Finish, and you are done. Reboot the system, and then see if hibernation works. You will notice that on boot you now see a text screen instead of the graphical Mandriva boot screen. This is an inevitable side-effect of disabling the framebuffer.
Some Wireless chips doesn't get an IP
See also Bug #45062. The default DHCP client used by Mandriva - dhclient - does not work on some wireless cards. The problem is that dhclient is unable to accept a DHCPNAK when it tries to request its last-used IP address from a different server. Switching to dhcpcd should fix the problem immediately.
Install the package dhcpcd from Free/Powerpack DVD or from /Main-repository. After that, go to the Mandriva Control Center (aka Configure your computer) and choose Set up an new network interface (...) in the Network & Internet section. There you can set up your wireless card as normal, until you reach the section for IP settings. Use the Advanced button to get an extra dialog where you can choose dhcpcd for the DHCP-Client
Wireless networking stops working if disabled and then re-enabled with Fn+F2 on Eee models
See also Bug #43332. Due to a bug in the kernel driver used to support it, the wireless networking chip in most Eee models stops working if you disable and then re-enable it using the Fn+F2 key combination. It turns off and then back on again correctly, but will no longer be able to connect to an access point or transfer any data. You can work around this issue by adding the following line to the file /etc/modprobe.conf:
options pciehp pciehp_force=1
And rebooting. After that, disabling and enabling the wireless adapter should work correctly.
A candidate fix has been uploaded to the /main/testing package repository: kernel-184.108.40.206-0.uc2mnb2. If you would like to help test the candidate fix, please read the "Testing Candidate Updates" section, above, for instructions on setting up your system to install packages from the /main/testing repository. Follow these instructions, then install the updated kernel packages. Please ensure you install the appropriate flavor (desktop, desktop586, or server) for your hardware - the uname -r command will tell you which flavor you are currently using - and also install the matching -devel package for the kernel you install; unless you do this, externally-compiled modules (like the NVIDIA and ATI proprietary graphics card drivers) will likely stop working.
Marvell 88SE61 series drive controllers do not work
See also Bug #43975. Some users have reported that Mandriva Linux 2009 does not work with the Marvell 88SE61 series of drive controllers present on several motherboards, including the Asus P5E3 and the MSI P965Neo-F V2. If your optical drive, or the hard disk to which you wish to install Mandriva Linux 2009, is attached to this controller, this will prevent you from installing Mandriva.
We are currently working to identify the cause of this issue and see if fixes and / or workarounds can be provided.
Frequent pauses while running 3D-accelerated applications with NVIDIA hardware
See also this NVNews discussion thread. A bug in the NVIDIA proprietary driver can cause frequent short pauses - once every half-second, or second - while running 3D applications, if the kernel feature PAT attributes (X86_PAT) is enabled and supported. This option is enabled by default in Mandriva, so this bug will appear on systems whose processor supports PAT attributes. If you are suffering from this issue, it can be resolved by adding nopat to the kernel boot parameters. You can use the Mandriva boot configuration utility, drakboot, to add kernel boot parameters. It can be found in the Mandriva Control Center, on the Boot tab, with the name Set up boot system.
No sound on various snd-hda-intel-based sound devices
See also Bug #44855 and Bug #44727. Due to changes in the upstream driver, several Intel HDA codec-based sound devices which worked in previous Mandriva Linux releases do not work in Mandriva Linux 2009. This issue is made more complex by the fact that there are dozens of slightly different hardware implementations of the Intel HDA codec, all supported by the same driver; some are affected by this issue, and some are not.
Some of these cases have been resolved by the official kernel updates so far released for Mandriva Linux 2009: kernel-220.127.116.11-1mnb-1-1mnb2, kernel-18.104.22.168-2mnb-1-1mnb2, and kernel-22.214.171.124-2mnb-1-1mnb2. If you have not done so already, run Mandriva Update to update your system to the latest packages, and reboot. This may resolve the problem.
There is also a more recent update candidate kernel in the /main/testing package repository: kernel-126.96.36.199-0.uc1mnb2. If the latest official update kernel does not resolve your problem, you may want to try the latest update candidate. If you would like to help test the candidate fix, please read the "Testing Candidate Updates" section, above, for instructions on setting up your system to install packages from the /main/testing repository. Follow these instructions, then install the updated kernel packages. Please ensure you install the appropriate flavor (desktop, desktop586, or server) for your hardware - the uname -r command will tell you which flavor you are currently using - and also install the matching -devel package for the kernel you install; unless you do this, externally-compiled modules (like the NVIDIA and ATI proprietary graphics card drivers) will likely stop working.
Slow or no internet response (particularly web browsing)
See also Bug #27070. There is a known problem with all Linux distributions that enable IPv6 networking (the new standard for network addresses which uses a longer, hexadecimal address format to provide a much larger number of possible addresses. The old standard is IPv4, which gives the four-groups-of-three-digits decimal address format most people are familiar with, e.g. 188.8.131.52). Some systems and networks do not cope well if your system has IPv6 networking enabled. If you experience sluggish response on the Internet - especially when browsing web sites - and cannot find the cause, you should try disabling IPv6. To do this, edit the file /etc/modprobe.conf, add the following line, and reboot:
install ipv6 /bin/true
TCP window scaling
See also Bug #27073. If this does not resolve the problem, there is another possibility. Most Linux distributions, including Mandriva, enable a kernel feature called TCP window scaling. This is useful for increasing the speed of transfers over very high bandwidth connections. However, a change was made in the default values for TCP window scaling in kernel 2.6.17, which seems to cause very slow network performance for some users with some internet sites. To see if TCP window scaling is the problem, you can disable it with this command:
sysctl -w net.ipv4.tcp_window_scaling=0
If this resolves the problem, you can make the change permanent by adding this line to the file /etc/sysctl.conf:
This will disable TCP window scaling at every boot. If you do use a very high bandwidth network connection - for instance, you regularly transfer large files over a local 100Mbit or 1Gbit network - you may notice that disabling TCP window scaling results in slower performance over this connection. In this case, you could try restoring the pre-2.6.17 default settings rather than disabling TCP window scaling entirely. To do this, add the following line to /etc/sysctl.conf, instead of (not in addition to) the previously suggested one:
net.ipv4.tcp_rmem=4096 87380 174760
This will change the default window scaling settings at every boot.
Slow network response with some wireless internet adapters (using the rt2500pci driver)
See also Bug #42180. It has been reported that some wireless adapters which use the rt2500pci driver will connect at a very slow speed by default. To remedy this, re-configure the card using the Mandriva network configuration tool (available in the Mandriva Control Center). During configuration there is a field which allows you to enter "iwconfig command extra arguments". In this field, enter the following text:
This should cause the connection to work at full speed in future.
Wireless access at Dana-Farber Cancer Institute with Intel 3945 wifi card
You cannot connect to the wireless network unless "allow access point roaming" is disabled(the checkbox is unchecked) during the wireless setup.
Printer configuration tool not installed by default in One editions
See also Bug #43635. The new printer configuration tool, system-config-printer, is not installed by default when installing a One edition of Mandriva Linux 2009. This means there is no available option to configure a printer. To resolve this problem, simply use the Mandriva software management tools to install the system-config-printer package. After doing so, the printer configuration tool will be available in the Mandriva Control Center, in the Hardware tab.
One editions fail to boot to a graphical desktop (xorg.conf not created)
See also Bug #43870. Several users have reported that One editions of Mandriva Linux 2009 fail to create the file /etc/X11/xorg.conf when booting.
This can then result in several possible scenarios. What happens is X.org will attempt to automatically detect the card and load the appropriate driver. If you are lucky, this will work, and you will likely never notice the problem.
If X.org auto-configuration fails entirely, this results in the graphical desktop failing to start. In this case, One will boot to a text login screen.
In the worst case, X.org auto-configuration finds a valid driver but it fails to work due to conflicts with the framebuffer system, resulting in an apparent failed boot: a blank screen with a cursor flashing at the top-left hand corner. There are two approaches if you find yourself in this situation. You can reboot and use the text mode, rather than graphical, boot - this option is available from the One boot screen after pressing F3. This should result in a successful graphical boot, although the most optimal driver for your hardware is most likely not being used. You can then run the graphics card configuration tool from the Mandriva Control Center to generate the /etc/X11/xorg.conf file, if you wish; you should do this if you intend to install One permanently. If you do this and then install One to your hard disk, the issue should not recur when booting the installed system.
Alternatively, when you see the blank screen, press Alt+F2 to get to a text login screen. You can then log in as user root (no password) and run drakx11. Accept all the default settings in this tool, and then close it. Then run the command service -f dm, and the graphical desktop should start up correctly. If you then install One to hard disk, the issue should not recur when booting the installed system. However, it will recur each time you boot live from the One CD.
If you wish to verify that this is indeed the problem you are suffering from, simply check whether the file /etc/X11/xorg.conf exists.
Encrypted partitions are not mounted during boot
See also Bug #44464. If you use the new feature of diskdrake to create encrypted partitions, and set these partitions to be mounted during boot (or they are system partitions), you may find you are not prompted for the passphrases during boot, and the partitions are not mounted. If they are system partitions, this can cause the system to fail to boot. This is due to the new graphical initialization system, splashy, lacking support for the cryptsetup encryption software. Therefore, we strongly recommend that you do not use the Mandriva tools to encrypt any system partition - that is, any partition which would contain any of the following directories:
bin/ boot/ dev/ etc/ home/ lib/ media/ mnt/ opt/ root/ sbin/ tmp/ usr/ var/
There is no known reliable workaround for this issue. We are working to address it with an official update as quickly as possible. Once that has been done, you will be able to install a system with encrypted partitions and boot without trouble as long as you agree to install official updates at the end of the installation process, when you are offered this option. If you do not, then the problem as described above will still occur.
Mandriva network configuration tool does not display list of available access points when configuring a wireless connection
See also Bug #43613. The Mandriva wizard for initially creating a network connection, drakconnect, may fail to display a list of available access points when attempting to configure a wireless adapter. The window which should display the list of available wireless networks will simply be empty.
It may be possible to work around this issue by simply waiting for a minute or two; if the adapter is able to associate with any network it will do so, and you will be able to press the Next button and continue to configure it. It may also be possible to finish configuring the interface using the Mandriva network configuration center, draknetcenter. If this workaround does not work for you, run drakconnect directly from a console, using this command:
This will launch the console, text-only version of the tool. This version is not subject to the bug, so you will be able to configure your interface successfully.
This issue is currently being investigated and may be addressed by a future official update.
Mandriva network configuration tool cannot configure Broadcom wireless adapters using native driver
See also Bug #44740. If your system uses a Broadcom wireless network adapter, you will not be able to set it up correctly using the Mandriva network connection wizard if you choose to use the native driver (which is the default choice) rather than ndiswrapper. This is a because the driver will not work without extra firmware which must be extracted from a driver file you provide (as described here), but a bug prevents the step where it asks for this file and then extracts the firmware from operating.
To work around this issue, you must extract the firmware manually. To do this, first download the driver file - named broadcom-wl-184.108.40.206.tar.bz2 - as described in the Release Notes. Extract this archive somewhere convenient. Then, change into that directory, and run the following command, as root:
b43-fwcutter -w /lib/firmware driver/wl_apsta_mimo.o
This will extract the required firmware to the appropriate location. You can then use the Mandriva network configuration wizard to set up the adapter, and it will work correctly (although please also note the other Errata entry that immediately precedes this one). This Errata entry relates only to using the native driver for Broadcom devices, b43. This is the default selection in the Mandriva network configuration wizard. If you instead select Use a Windows driver via ndiswrapper, this Errata entry is not relevant to you. You should not try and use the driver discussed in this Errata entry with ndiswrapper: it is not a Windows driver and will not work. The driver you need to use a Broadcom wireless card with ndiswrapper is usually named bcmwl5: you need both bcmwl5.sys and bcmwl5.inf to be in the same directory, and then when the wizard asks for a Windows driver, select bcmwl5.inf from that directory.
Mandriva network configuration tools do not correctly handle wireless encryption keys containing some special characters
See also Bug #40065. The Mandriva network configuration tools do not correctly handle wireless encryption passphrases that contain some characters. There are two workarounds for this issue. You can simply change your wireless encryption passphrase not to contain any of these characters. If you do not wish to do this, you can edit the appropriate configuration file to contain the correct key. For the default access point for your interface, edit the file /etc/sysconfig/network-scripts/ifcfg-interface - for instance, if the interface is named wlan0, edit the file /etc/sysconfig/network-scripts/ifcfg-wlan0. For any other access point, edit the file /etc/sysconfig/network-scripts/wireless.d/MAC, where MAC is the MAC address of the access point. In both cases, edit the line which begins with the word WIRELESS_ENC_KEY to look like this:
Where KEY is the key. So if the key was FOOBAR!@%=, you would edit the line to read:
The exception is if the key contains the double quote (") character, in which case you would use single quotes (') to enclose the key, for example:
This issue will be addressed in a future official update.
Mandriva tool for accessing Windows / SMB / CIFS / Samba shares does not work
See also Bug #42483. The Mandriva tool for accessing SMB / CIFS / Samba (Windows-type) network shared drives and partitions, available in the Mandriva Control Center on the Network Sharing tab with the name Access Windows (SMB) shared drives and directories, does not work. It will find available shares, but will not be able to mount them. This is because it attempts to mount the partitions using the deprecated smbfs type, rather than the correct cifs type.
To work around this issue, we simply advise you do not use this tool, but use some other method of browsing and accessing this type of shared drive or partition. For instance, in both KDE and GNOME desktop environments, you can browse to the location smb:/ using the default file manager to access SMB / CIFS-type shares on the local network. In order to mount shares (so that they are available to non-KDE/GNOME applications), smb4k can be used instead.
This issue will be addressed in a future official update.
Compiz and Metisse do not work in KDE 4 if started via startx
If you enable Compiz or Metisse via the drak3d utility, and then attempt to start KDE 4 from a virtual console using the startx command after booting at init level 3 (rather than booting to a graphical login manager and logging in to KDE 4 that way, as most users do), Compiz or Metisse will not be used. Currently, they will only work if you log in to KDE 4 from a graphical login manager rather than logging in at a console and starting KDE 4 via startx.
Graphical corruption with NVIDIA GeForce 7xxx series graphics cards
See also Bug #43716. There are known problems with graphical performance in KDE 4 using the proprietary NVIDIA graphics card driver. In order to mitigate these issues, we have applied two NVIDIA driver configuration changes by default: InitialPixmapPlacement=2 and GlyphCache=1. This has been tested and confirmed to improve performance in almost all cases. However, it seems it can also occasionally cause graphical corruption issues (in all environments, not just KDE 4) on a few other NVIDIA cards, apparently from the GeForce 7xxx series. If you use an NVIDIA card and are experiencing display bugs, try removing the file /etc/X11/xinit.d/01nvidia-performance.
Long delay opening the dialog to save or open files in GTK+-based applications
See also Bug #44532. Due to a bug in the beagle package shipped with Mandriva Linux 2009, on some systems, there is a long delay - which makes it appear that the application has hung - when trying to open or save a file in GTK+-based applications (notably Mozilla Firefox, Opera, or any Mandriva tool). If you are affected by this problem, you can work around it by removing the beagle package, but this will cause all Beagle-based applications to be removed. Mandriva and GNOME developers are working to identify and fix the bug that causes this problem, and an update will be made available as soon as possible.
A candidate fix has been uploaded to the /main/testing package repository: libbeagle-0.3.5.1-3mdv2009.0. If you would like to help test the candidate fix, please read the "Testing Candidate Updates" section, above, for instructions on setting up your system to install packages from the /main/testing repository. Follow these instructions, then install the updated libbeagle packages.
Extended keys (multimedia keys) not supported in KDE 4
See also Bug #43130. The extended keys present on many modern keyboards - commonly referred to as multimedia keys - are not supported in Mandriva Linux 2009's KDE 4 desktop. This is due to the fact that the KDE application which handles these keys, kmilo, is not yet available in a KDE 4 version. This issue will be partly addressed in a future update, by associating the volume and mute keys with the kmix mixer by default, but the other extended keys cannot be handled until a KDE 4 version of kmilo becomes available. Please note that these keys do function correctly in GNOME and Xfce.
You can manually associate the volume and mute keys with the kmix mixer applet by following these steps. Right click on the volume icon in the system tray, and click Show Mixer Window. Then, on the window that appears, click the button labelled Mixer. Try changing the settings on each channel to see which best controls your card (usually it will be the left-most channel). Then right click on the best channel and click Configure Shortcuts.... It should show three shortcuts - Decrease Volume, Increase Volume, and Toggle Mute. Click on Decrease Volume, then click on the button labeled None, and press the volume down key on your keyboard. Then click on Increase Volume, click on the button labeled None, and press the volume up key on your keyboard. Finally, Click on Toggle Mute, then click on the button labeled None, and press the mute key on your keyboard. Then click OK.
Enabling LCD sub-pixel rendering in KDE 4
In KDE4, QT4 has built-in sub-pixel rendering but there's a bug in the font configuration tool in the KDE control centre (systemsettings) that makes it check for LCD sub-pixel rendering only in FreeType. FreeType LCD sub-pixel rendering is disabled by default in Mandriva's FreeType libraries because it's covered by patents, that's why the dialogue is greyed out in the KDE4 control centre, while in fact it can fall back to QT4's own built-in sub-pixel rendering.
To overcome this, edit ~/.fonts.conf (this file is in your /home/username folder, this is a hidden file, to be able to view it open Konqueror or Dolphin and then open View>Show hidden files). You can edit .fonts.conf with any text editor, such as kwrite. Change:
<edit mode="assign" name="rgba" > <const>none</const> </edit>
<edit mode="assign" name="rgba" > <const>rgb</const> </edit>
To check it worked, open the KDE control centre>Appearance>Fonts, make sure anti-aliasing is Enabled and then open Configure. "Use sub-pixel rendering" should be checked even though it's still greyed out.
This will affect only newly started applications (i.e. applications that are opened after you set this), so best to log out then log in to see the full effect of this setting.
Most monitors use RGB sub-pixels, while some use BGR, so edit .fonts.conf accordingly.
KDE 4 panel displays graphical corruption when running GTK+-based applications
See also Bug #42420. Particularly on NVIDIA graphics cards, the KDE 4 panel may display graphical corruption (color changes, going blank) when running GTK+-based applications, like Mozilla Firefox or OpenOffice.org, with NVIDIA graphics adapters. The corruption is a purely aesthetic issue: it does not affect the functionality of the system or the panel. We are working on identifying the cause of this issue and a fix for it, and it will be resolved by an official update if possible.
KDE 4 cannot play many video formats as installed
See also Bug #44586. The default video player in KDE 4, DragonPlayer, is incapable of playing many video formats as installed. If you try and play a video in an unsupported format, DragonPlayer will launch, but will not show the video, only a blank white window.
This issue can be mitigated by installing the gstreamer0.10-decoders package, which will install several video and audio codecs that will allow DragonPlayer to play many types of video. If your video is still unsupported, you can try installing the totem package, which provides the Totem media player. You can find it in the Sound & Video section of the system menu, with the name Movie Player. It can use the Codeina framework to attempt to identify and locate a downloadable codec which can play the video in question.
KDE 4 applications cannot play audio CDs (digital mode)
See also KDE Bug #164043. Due to this known bug in the Gstreamer backend for KDE 4's Phonon multimedia framework, which Mandriva Linux 2009 uses by default, standard KDE 4 applications - kscd and DragonPlayer - cannot play audio CDs in digital mode (which is used by most people and is the default). There are several workarounds for this.
If you particularly wish to use kscd or DragonPlayer, you can install the phonon-xine package. This should cause KDE to switch to using the Xine (rather than Gstreamer) backend for Phonon, which allows Phonon-based applications to play audio CDs without problems. However, it may in turn cause certain other types of audio or video files not to be playable. You can switch between the Gstreamer and Xine backends to resolve this. Run the KDE System Settings tool (not the Mandriva Control Center) by clicking on the screwdriver and wrench icon in the panel, or from the menu under Tools, System Tools, Configure Your Desktop. Then click on Sound. Go to the Backend tab, and you can adjust the priority ordering of the two backends.
If you just wish to listen to a CD, you can use several alternative applications. You can install the totem package, which will make totem available in the Sound & Video section of the system menu, with the name Movie Player. This application can play audio CDs without trouble. Other applications you can find in the Mandriva repositories that will be able to play audio CDs include vlc, kaffeine4 and kmplayer.
KDE 4 does not suspend when laptop lid is closed
See also Bug #43283. The kde4powersave utility included with KDE 4, which handles power management, does not react correctly to the lid of a laptop being closed. It will not perform any action configured to happen when the lid is closed - including the standard and most popular configuration, to suspend the system.
To work around this issue, you must either manually suspend the laptop before closing the lid, or replace kde4powersave with an alternative. The alternative power manager guidance-power-manager is available in the official repositories, and has been reported to work correctly with lid close events.
Bogus error message when entering an incorrect password to log in or unlock a KDE 4 session
See also Bug #44027. Due to a bug in the PAM authentication framework, if you enter an incorrect password when logging in (using the KDM login manager) or when unlocking a KDE 4 session which has been locked, a bogus error message will be displayed, similar to the following:
Cannot unlock the session because the authentication system failed to work; you must kill krunner_lock (pid XXXX) manually.
The error message is worrying but harmless and misleading. You will then be returned to the login or unlock screen. If you then enter the password, things will proceed as normal.
KDE 4 applications cannot run as root via su
Many users are used to running individual applications as root by using the su command at a console and then launching the application, like this:
[adamw@lenovo ~]$ su Password: [root@lenovo adamw]# kwrite
However, for most KDE 4 applications in Mandriva Linux 2009, this will not work. To make it work, you must use the su - command, like this:
[adamw@lenovo ~]$ su - Password: [root@lenovo adamw]# kwrite
What this does is create a complete root environment rather than simply giving you root privileges, but the important thing is, this way it works.
Mandriva interactive firewall configuration tool too large for low-resolution displays
See also Bug #38904. The configuration application for the Mandriva interactive firewall, drakids, is too large to fit into a low-resolution display, such as those on most netbook systems. To work around this issue, in most window managers, you can hold down the Alt key and then drag the window. This will allow you to drag it off the top or bottom of the screen, and so by degrees access all sections of the window.
Webcams do not work in some applications (including Skype)
Several webcams will not work with certain applications, including Skype, out of the box. If your webcam works with some applications but not others, you can work around it by launching the application using the following command:
So for Skype, you would run:
The package libv4l must be installed for this to work.
For x86-64 users, use the above command exactly as written for Skype. You must have the i586 (not x86-64) version of the libv4l package installed. You can do this by downloading the package and installing it by running the following command as root:
rpm -Uvh libv4l-0.4.3-1mdv2009.0.i586.rpm
from the directory to which you downloaded the file. However, for most other applications (which will be x86-64 applications, unlike Skype, which is an i586 application) you should install the x86-64 version of the libv4l package, and run applications using this command:
Mandriva Linux 2009 fails to boot when installed as a KVM guest system
See also Bug #42358. Due to the use of an older version of the graphical grub bootloader, a Mandriva Linux installation with the default configuration will not boot as a KVM (virtualization system) guest. To work around this issue, when installing Mandriva, change the bootloader to non-graphical grub, or lilo.
Some OpenOffice.org functions do not work in One edition
See also Bug #44644. The One edition of Mandriva Linux 2009 does not include a Java environment, due to lack of space. OpenOffice.org relies on Java for several features, so these features will not work from the One edition when running live, and will also not work from the One edition after installation until you install the openoffice.org-java-common package, using the Mandriva package management tools. A brief summary of features which will not work without Java follows:
- Creating databases, forms and user controls in Base
- Accessing any type of database in Base which would use the JDBC connector
- Saving / exporting to AportisDoc (Palm) (.pdb), DocBook (.xml), Microsoft Word 2003 XML (.xml), OpenDocument Text (Flat XML) (.fodt), Pocket Word (.psw), Unified Office Format text (.uot), BibTex, Latex 2e and MediaWiki in Writer
- Saving / exporting to Pocket Excel (.pxl), Microsoft XML 2003 Excel format (.xml) , OpenDocument SpreadSheet(Flat XML)(.fods) and Unified Office Format spreadsheet (.uos) in Calc
- Saving / exporting to OpenDocument Presentation (Flat XML) (.fodp) and Unified Office Format presentation (.uop) in Impress
- Saving / exporting to Saving file as to: OpenDocument Drawing (Flat XML) (.fodg) in Draw
- Letter, Fax, Agenda and Web Page wizards in all modules
- Exporting to XHTML (.xhtml, .html) in all modules
Again, to restore these functions, simply install the openoffice.org-java-common package.
Libraries in libopenmotif3 package cannot be used
See also Bug #43808. The package libopenmotif3 is available in the Mandriva Linux 2009 repositories. No official package depends on this library, but you may find some third party software which requires one of its library files, like libXm.so.3. If you try to install this package to provide the library, you will find that the library still cannot be found by the application. This is because the file is located in /usr/X11R6/lib, and Mandriva is no longer configured to look for libraries in this location.
As a quick workaround, you may copy or link the files from /usr/X11R6/lib to /usr/lib. This issue will not be fixed, as it would require the introduction of a new source package for an old version of openmotif, which we do not wish to do at this point. The libopenmotif3 package will not be available in future Mandriva Linux releases.
Smart broken with lzma compressed metadata
See also Bug #27697 (notice only last part of bugzilla entry being relevant here). For the version of the Smart package manager shipped with Mandriva Linux 2009, support for the new 'info.xml.lzma' metadata were added in the last minute. Required functionality for this were also added to the python lzma module, but unfortunately this version accidentaly didn't make it into the release. An updated 'python-liblzma-0.4.0-1mdv2009.0' package can be found in the 'contrib/testing' (will be moved to 'contrib/updates' when verified) section. Notice that since this might've broken smart preventing it from installing this update for you, you might have to manually download and install it with 'rpm -Uvh python-liblzma-0.4.1-1mdv2009.1.*.rpm' or use urpmi in stead of smart.
3D-accelerated desktop and video playback
See also Bug #25572. If you use the 3D accelerated desktop technologies included in Mandriva Linux 2009 (AIGLX or Xgl), you may notice that video playback does not work very well - moving, resizing, maximizing the video window will cause problems, or you may see strange artifacts in or through the video. You may also notice that, if you use the 'cube' feature of compiz, the video does not play while you rotate the cube. There are two ways to avoid this problem.
If you have an Intel graphics adapter, you can try using the Compiz Video Playback plugin. Using the ccsm configuration tool for Compiz, scroll down to the Utility section and you should see a plugin labelled Video Playback. Enable this plugin. This should allow video playback to work in several applications.
If you have a different video adapter, or you still experience problems with the Video Playback plugin enabled, you should set your video player to use an output driver which does not use video overlay. If you use AIGLX, you should use the x11 / xshm output driver. If you use Xgl, you can use the x11 / xshm driver or the OpenGL output driver (which may be smoother and offer more features, such as brightness / contrast control, than the x11 / xshm driver). The way to do this is different for different video players.
- For players that use gstreamer - which includes the default Mandriva video players in both KDE 4 (DragonPlayer) and GNOME (Totem) - run the command gstreamer-properties, go to the "Video" tab, and set the video output to "X Window System (No Xv)". If gstreamer-properties does not exist, you should install the package gnome-media.
- For mplayer, for x11 / xshm output, add this line to ~/.mplayer/config (and also to ~/.mplayer/mplayerplug-in.conf if you use the mplayerplugin browser plugin):
For OpenGL output, add the following line instead:
- For xine, go to the settings menu, set your configuration experience level to "Advanced", then go to the video tab and change "video driver to use" to "xshm" for x11 / xshm output or "openGL" for OpenGL output. Alternatively, you can use these console commands. For x11 / xshm output:
perl -pi -e 's|#video.driver:auto|video.driver:xshm|' ~/.xine/config
For OpenGL output:
perl -pi -e 's|#video.driver:auto|video.driver:openGL|' ~/.xine/config
- For the KDE 3 version of Kaffeine, go to the settings menu, select "Xine backend configuration" and in the video tab change the driver to "xshm" for x11 / xshm output or "openGL" for OpenGL output.
- For Totem in Xine mode, run this command for x11 / xshm output:
perl -pi -e 's|#video.driver:auto|video.driver:xshm|' ~/.config/totem/xine_config
Or this command for OpenGL output:
perl -pi -e 's|#video.driver:auto|video.driver:openGL|' ~/.config/totem/xine_config
- For x11 / xshm output in KMplayer, go to Settings -> Configure KMplayer. Then in the "General Options" section go to the Output tab. In this section change Video Driver to "X11Shm".
- For X11 output in VLC, open Tools -> Preferences -> Video and change Output to X11 video output.