2010.0 Errata

From Mandriva Community Wiki

Jump to: navigation, search
This page contains the Errata for Mandriva Linux (2010.0). This means it contains information on known problems with Mandriva Linux 2010 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 2010 release.


Installation issues

Difficulty finishing the first boot greeting/registration window

There is a slight usability issue with the first boot greeting/registration window, in that it does not exit automatically. You need to press the 'close' button in the bottom right hand corner of the window. Some users have reported not noticing this button and so seemingly being unable to get past this initial greeting window. The issue is tracked in Image:bug_small.png Bug #55099

Default user UID is now 10001 and not 500

Please note that if during install you go with defaults at user set-up, your user will now have a UID of 10001. In previous releases of Mandriva this default was 500. You can easily set 500 or any other value during install. In the user set-up section (passwords etc) click 'Advanced' and set user and group there. This change might affect people for example doing a clean install and keeping their old /home partition, since by default the old user and group file permissions would no longer match the new user. Reported here in Image:bug_small.png Bug #55362

Kernel issues

Hardware issues

ACPI is enabled by default but not supported on HP mini 2133 netbooks

ACPI is enabled by default but not supported on HP mini 2133 netbooks. Logging out from desktop sessions will cause a blackscreen, though vt1~6 are still available. Please upgrade your BIOS to version F.06 or above. If it still happens, disable ACPI in boot options using drakboot. See Image:bug_small.png Bug #53985.

KMS is not well supported by some Intel graphic cards

KMS (Kernel Mode Setting) is not well supported by some Intel graphic cards. If while booting you can't see anything on your screen (laptop or desktop), try disabling KMS and using UMS mode.

To test if disabling KMS solves the problem, when booting, at the GRUB (the boot loader) screen press F3 (Kernel Options) select default then press Enter, in the command line that appears type:


then press Enter.

If this works then you can add this kernel parameter permanently by editing /boot/grub/menu.lst, (it's recommended to keep a backup of this file before editing it). To edit it, as root in terminal:

su -
kwrite /boot/grub/menu.lst

(kwrite is installed by default it KDE; replace it with gedit if you're running Gnome or whatever text editor you have). In the first entry add i915.modeset=0 next to the vga=XYZ bit (leave a space between them). Then save the file.

For more information see Image:bug_small.png Bug #53758.

Backlight controls don't work properly with Fujitsu Siemens esprimo mobile u9200

See Image:bug_small.png Bug #50485. The backlight control doesn't work properly with Fujitsu Siemens esprimo mobile u9200, try adding "acpi_backlight=vendor" to the kernel command line this will make backlight adjustment works flawlessly, all 8 levels are reachable. But you get no OSD and the gnome brightness applet is completely non-functional (shows the "failed to determine brightness level" icon - you can move the slider, but it doesn't change anything).

Slow or no internet response (particularly web browsing) because of IPv6 issues

See also Image:bug_small.png 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. 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, or if installing Firefox add-ons fails or stalls (see this), and you cannot find an apparent reason for this then you should try disabling IPv6. To do this, left-click the net_applet icon in the system tray this will open the Network Center, now open Advanced Settings and check Disable IPv6, then click OK and restart the system. (You can also reach the Network Center by opening the Mandriva Control Center > Network & Internet > Network Center).

USB removable storage devices and internal HD partitions can't be mounted from Dolphin or Nautilus

Sometimes when mounting usb removable devices or internal HD partitions (partitions that don't have entries in /etc/fstab) from the Dolphin or Nautilus Places panels you may get an error message including IsCallerPrivileged() failed instead of mounting the device, if it's a removable device, or seeing the expected authentication pop-up message to enter the root password to mount the partition, if it's an internal/fixed HD partition.

This bug has been fixed by an update, for more info read this update advisory MDVA-2010:017.

Sometimes you may see anomalies which may be caused by speedboot

Sometimes when speedboot is enabled you may see some odd behaviour, for example:

  • You may end up with a black screen upon booting.
  • With speedboot and autologin enabled you mayn't be able to load kmix in the KDE4 desktop, see Image:bug_small.png Bug #55010 for more info.
  • NTP (Network Time Protocol) service sometimes may not start correctly.
  • WIFI connection may not be up fast enough.
  • Suspend to RAM and/or suspend to disk invoked from KDE menu don't work.

To test if it's speedboot or not causing this, try disabling it, when booting, at the GRUB (the boot loader) screen press F3 (Kernel Options) select default then press Enter, in the command line that appears type:


then press Enter.

If this fixes the bug you're seeing you can disable speedboot permanently by editing /etc/sysconfig/speedboot. Or just use this command as root:

sed -i 's/=auto/=no/' /etc/sysconfig/speedboot

HP Scanners or All-in-One type HP printers scan function won't work

This is a known problem. Problem comes from task-printing-hp package. This package responsible for installing required packages for HP printers and scanners as a dependency. task-printing-hp package should install libsane-hpaio1 package; but it won't. Users should install libsane-hpaio1 package manually to get scanner work. Bug #46940

No Sound on Headphones

If you have an Intel sound card which requires snd-hda-intel driver but do not have any sound when plugging in headphones, try the following fix :

Create a file /etc/modprobe.d/alsa-base.conf, and put the following line in it :

options snd-hda-intel model=z71v position_fix=1

On Sony Vaio FZ21M, you have to insert the following options instead :

options snd-hda-intel model=vaio enable=1 index=0 position_fix=1

Then reboot.

The graphical X server fails to start with S3 Unichrome graphics chipsets

In a default set up the graphical X server fails to start with S3 Unichrome card, or you mayn't be able to login, i.e. when you try logging in you get thrown back to the login screen.

However there's a workaround, that is to disable the Composite Extension from XFdrake, the graphical server configuration tool in Mandriva. You can do this from the Mandriva Control Center Image:Drakconf-icon.png > Hardware > Set up the graphical server > Options.

If you can't login at all then you can follow the following steps:

  • When booting the system, at the GRUB screen press F3 (Kernel Options), select default then press Enter
  • In the command line that appears type 3 then press Enter, this will boot the system to run level 3
  • After the system boots, log in as root:
localhost login: root
  • Start drakx11:
  • Open Options, then uncheck Enable Translucency (Composite Extension)
  • Close drakx11 and agree to saving the changes.
  • Now get back to the text console, then go to run level 5 (which is the default run level the system boots to when you boot normally):
init 5

Now you should be able to log in normally.

Viewing videos fails on some GeForce 8400M cards with the proprietary driver

Some GeForce 8400M cards may fail to display videos in media player with the NVIDIA proprietary driver. The affected systems show black window instead of the actual video. This has been fixed in the newer versions of the NVIDIA driver. Install a newer version of x11-driver-video-nvidia-current from the Non-free Backports repository (select Backports from the dropdown list in Software Management). For details, see Image:bug_small.png Bug #55749.

Some Java applications may cause stability problems with NVIDIA driver

See Image:bug_small.png Bug #55374. Some Java applications that provide a system tray icon may cause stability problems with the proprietary NVIDIA driver. Updating the NVIDIA driver fixes it, or at least makes the problem far less frequent. Install a newer version of x11-driver-video-nvidia-current from the Non-free Backports repository (select Backports from the dropdown list in Software Management).

System freeze with the proprietary ATI driver with some hardware

See Image:bug_small.png Bug #55269. Some combinations of ATI video cards and other system hardware may cause the system to freeze when using the proprietary ATI fglrx video driver. This is fixed in the newer driver versions, which you can install by following this guide.

Alternatively, you can use the free driver to avoid the freeze, (with a cost in performance): Select your card in Mandriva Control Center > Hardware > Set up the graphical server > Graphics Card then select No if/when asked to use the proprietary driver for your card.

If you can't reach a graphical desktop, you can follow these steps:

  1. When booting the machine, select safe mode from GRUB, the boot loader, menu
  2. Start drakx11 and open Graphics Card, select your card, and answer No to installing a proprietary driver
  3. Save the settings and get back to the text console and reboot the machine by pressing Alt+Ctrl+Delete

If you are booting a One live CD, at the GRUB (the boot loader) screen press F3 (Kernel Options), select default then press Enter, in the command line that appears type:


then press Enter. This will cause a free driver to be used instead of the proprietary one, therefore allowing the desktop to appear correctly.

On boot you might see a message about waiting for a hard disk device to appear

When booting the machine you might see a message like:

waiting for device sdXY to appear (timeout 1 min)

This may be caused by changing the UUID of a partition, by e.g. formatting it, while the old UUID of this partition is listed in the initrd of the kernel you're booting with.

An example would be, you installed Mandriva and created a swap partition, ideally the UUID of that partition will be included in the initrd of the installed kernel; if later on you install another distro and that distro requires that you format the swap partition, or you format that partition for any other reason, then at boot the system is looking for that partition, marked by that particular UUID, but it can't find it, so it gives the above message, and waits for 1 minute at each boot.

To fix this problem follow these steps:

  • Get the UUID of the swap partition from the output of the blkid command:

note it down. For example if the output of the blkid command is:

/dev/sda1: UUID="07929ccf-0ab6-4857-9835-cafc2751cee7" TYPE="ext4"
/dev/sda5: UUID="a834c939-0f27-4684-85d5-e93059889df1" TYPE="swap"
/dev/sda6: UUID="52fd646b-0405-4b75-ac77-010400c67d96" TYPE="ext4"

then you'll take a834c939-0f27-4684-85d5-e93059889df1 (without the quotes), and put it in /etc/fstab for the swap partition, then do the same in /boot/grub/menu.lst for all resume=UUID= parts.

You need to edit /etc/fstab and /boot/grub/menu.lst as root (that is if the swap UUID isn't correct in either or both of them):

  • To edit /etc/fstab
su -
kwrite /etc/fstab

(replace kwrite with gedit in the above command if you're running Gnome, basically any text editor will do).

  • To edit /boot/grub/menu.lst:
su -
kwrite /boot/grub/menu.lst
  • Now you need to recreate the initrd for the kernel, you can do so by using this command in terminal:
bootloader-config --action rebuild-initrds

N.B. you won't see the "waiting for device sdXY" message if you use the graphical bootsplash, which is used by default. So if you experience unexplained long boots, where the system looks like idling, it's advised to press Esc to see the text boot messages to diagnose any problem(s).

HAL doesn't mount a SonyEricsson Xperia X10 even thou lsusb recognizes it.

When connecting the phone to the USB-port, there's no mode for the phone to become mounted like previous SonyEricsson mobile-phones.

This bug is tracked in this report Image:bug_small.png Bug #59110

Upgrade issues

Theme not updated in boot menu

When upgrading from a previous release of Mandriva Linux using installer, theme for boot menu might not be updated to the latest design. To fix this, as root, run grub-gfxmenu --update-theme.

Upon upgrading KDE4 you might find most of the desktop is black

Sometimes after upgrading KDE4.2.x to KDE4.3.x you may find that most of the desktop wallpaper is black except for a very small part at the top, see this screenshot: https://bzattachment.mandriva.com/attachment.cgi?id=15113

There're reports that this goes away after logging out then logging back in, as the plasma configuration files get touched.

If it persists then this will definitely fix it. Run these commands as user (not root) in terminal: kquitapp plasma-desktop rm -fv ~/.kde4/share/config/plasmarc plasma-desktop &

This bug is tracked in this report Image:bug_small.png Bug #54006

Samba accounts from a previous install may not work after upgrade

Samba 3.4 now defaults to storing Samba account details in the tdbsam backend, instead of the smbpasswd backend that was the default backend since 2.0 or before. The upgrade process does not migrate accounts. If you had samba accounts in the (default) smbpasswd backend, you can either:

  1. Migrate the Samba account details out of smbpasswd and into tdbsam (recommended), using a command (as root) such as: pdbedit -i smbpasswd -e tdbsam
  2. Continue using smbpasswd (not recommended), by adding the following line to the global section of /etc/samba/smb.conf: passdb backend = smbpasswd

See Image:bug_small.png Bug #55415 for more information.

Software issues


Using Install & Remove Software (aka rpmdrake) gives an error about missing packages

When using Install & Remove Software to install packages you may get an error about missing ones, even though the packages are available on the mirror urpmi is using and the urpmi database is up-to-date. This bug is triggered if you do more than one installation transaction, i.e. if you select more than one package and install them it'll work correctly, but if after that you select another package(s), without restarting rpmdrake, you get an error.

This bug has been fixed with an official update, for more information check out this update advisory MDVA-2010:042.

When logging in you may see a warning about password expiration

For user accounts, other than the ones created during the installation process, you may see a warning message that your password will expire in 99,999 days. This bug is fixed by an update as explained in this update advisory MDVA-2009:267.

After a fresh install or upgrading to 2010.0 you may see an notification to "upgrade to 2009.1"

Due to a bug in mdkonline you may see a pop-up message from mdkapplet (the update applet in the system tray) that a new release is available and it'll offer to upgrade to "2009.1" even though you did a fresh install of 2010.0 (or upgraded already). This bug has been fixed by mdkonline-2.77.8, all you need to do is:

  1. Right click mdkapplet in the system tray then select Check Updates
  2. After it checks for updates, right click it again and select Install updates

Alternatively you can update from terminal: su urpmi --auto-update -v

That's it, after the new mdkonline package is installed you won't be asked to "upgrade" to 2009.1 again.

Wireless regulatory domain

Mandriva 2010.0 uses the wireless regulatory domains in order to comply with the FCC requirements, using the US domain as default. Therefore, if you need access to country-allowed wireless settings (such as wireless channels 12 and 13), it is necessary to select the correct regulatory domain by opening Mandriva Control Center Image:Drakconf-icon.png > Network & Internet > Network Center > Advanced Settings and selecting your country from the list. See Image:bug_small.png Bug #54600.

Keyboard layout in virtual terminals ("console") not set on boot/defaults to us layout

The keyboard layout is not set according to what was chosen during installation, but instead Mandriva 2010 always boots with the us layout (the graphical desktop is not affected). To solve the problem add loadkeys <your layout> to /etc/rc.d/rc.local
As example: For a french layout you would add the line loadkeys fr. See Image:bug_small.png Bug #54946

Kaffeine does not play DVB channels

Attempting to play a DVB channel may give the error message "Could not open media source". This is fixed in kaffeine-1.0-0.pre3.1mdv2010.0, which has been provided as an update.

For more information, see Image:bug_small.png Bug #54791 and upstream KDE bug #188411.

File Managers hang when listing directories and files in user's /home

Due to a bug in gvfs-fuse, it sometimes hangs on ~/.gvfs, this prevents file manager e.g. Dolphin, Konqueror, Nautilus ...etc from listing the directories and files in the user's /home. This bug has been fixed by an update, for more info check this update advisory MDVA-2009:215.

Totem crashes when playing audio files

Due to a bug in the GOOM visualisation, Totem crashes when playing audio files. This plugin is disabled by default, but if you're using a user account with the same /home folder from a previous release you may still see this bug. You can easily fix it by disabling that problematic plugin, open Totem -> Edit -> Preferences -> Display, select any visualisation other than GOOM or disable the Visual Effects altogether.

Epiphany (or other webkit based applications) crash a lot on non-SSE2 processors (like Athlon XP)

The crashes occur because of upstream webkit-bug#29779. The JavaScript interpreter tries to use a SSE2-instruction even on processors that don't support it. The result is a crash with "illegal instruction" printed to the terminal. The workaround is to disable JavaScript. If you rely on JavaScript functionality, you need to use another browser that is not based on webkit (like for example Firefox) until an updated package of webkit is available for Mandriva Image:bug_small.png Bug #55533

Dump doesn't work at all with EXT4

Now that ext4 has been chosen as default filesystem, you will probably notice that dump no longer works. This is a known upstream problem still not solved, then, if you use dump for performing tasks like doing backups, you will need to migrate to a different tool. Please see Image:bug_small.png Bug #55384

Ctrl+Mouse Wheel doesn't Zoom in graphical desktop

If you are not able to zoom using Ctrl+Mouse Wheel, try removing the imwheel package. For more info see Image:bug_small.png Bug #50862.

If the system beep annoys you

If the system beep annoys you, it can be disabled/muted. There're two cases depending on your sound hardware:

  • For some sound cards the beep can be controlled using an audio mixer, e.g. alsamixer (which is a terminal/console mixer). Load alsamixer from terminal:
alsamixer -c 0

select the Beep channel and mute it by pressing M. Of course you can lower its volume if you don't want to mute it completely. You can also use this command to mute the Beep channel amixer set Beep mute

Then to make sure this will be saved, to survive a reboot, run this command as root in terminal:

alsactl store
  • For some sound cards where the Beep can't be controlled using a sound mixer, it can be disabled by blacklisting the pcspkr kernel module. This can be done by adding blacklist pcspkr to /etc/modprobe.d/blacklist-mdv on a separate line. Or you can simply use the following command as root in terminal:
echo "blacklist pcspkr" >> /etc/modprobe.d/blacklist-mdv

the reboot the system.

For an immediate (but non-permanent) fix use rmmod pcspkr, the module will be loaded when you reboot the system unless you blacklist it as explained above.

The lvm2 package is missing on the free-dual ISO

The lvm2 package is missing from the 2010.0 free-dual ISO (this will be fixed for the next release, 2010.1). So you can create an LVM using the free-dual installer but it won't work after the installation when you boot the system because of that missing package.

Unfortunately the 2010.0 free-dual ISO won't be recreated. For now you can set up ftp sources during the installation, that will install the lvm2 package from the online repos, or use the Free DVD which has this package on the ISO.

Mounting CIFS/SMB (Windows, Samba ...etc) shares no longer possible as non-root

Due to possible attack vectors in code that has not been sufficiently audited (such as recent symlink attacks), the Samba and Linux CIFS client teams have decided to disallow user mounting of shares with mount.cifs. Where previously, mount.cifs could be made setuid to allow this, this feature no longer works. The development teams strongly recommend that distributors not revert the change. In accordance with the developers wishes, Mandriva has not re-enabled this feature.

The recommended workarounds are:

  • Enabling the "Superuser" feature in smb4k (recommended for desktop users who need ad-hoc CIFS/SMB access for non-KDE applications)
  • Adding a sudo rule allowing specific trusted users to run mount.cifs as root (recommended for ad-hoc command-line mouting)
  • Adding entries to /etc/fstab (for specific, but on-demand mounting)
  • Using pam_mount to provide automatic mounting at login for multi-user machines where CIFS is required

Mandriva is following upstream developments, and is interested in the return of this useful feature assuming security risks can be mitigated adequately.


Enabling Nepomuk fails on a fresh install of KDE4 One Live CD

Due to space constraints on the KDE4 One ISO's no Soprano backend packages are included on the One ISO's (Soprano backends need a Java runtime environment and that was too big to fit on the One ISO's and Nepomuk isn't useful when running One Live).

When enabling Nepomuk from the KDE Control Center you'll get a message complaining that there're no Soprano backend available, this is easily fixed by installing a Soprano backend e.g. soprano-plugin-redland.

Printer configuration tool is not installed by default in KDE One editions

See also Image:bug_small.png Bug #49994. Because of space problem on CDs, the printer configuration tool, system-config-printer, is not installed by default when installing a KDE One edition of Mandriva Linux 2010.0. However as the corresponding entry is available in Mandriva Control Center in the Hardware tab, you just need to click on the corresponding icon, and all the needed packages will be installed automatically. Be sure to have configured correctly the Mandriva repositories and have a working internet connection beforehand, note that the repositories are added automatically on first boot of One Live CD installs if an active internet connection is available.

K3b is not available on the KDE One edition ISO's

The KDE burning application, K3b, is not installed by default when installing KDE any of the KDE One Live CD's due to space constraints. The k3b package can be installed from the Mandriva /main repositories simply by using the Mandriva packages management tools. After doing so, the burning application will be available in the applications menu, in the Tools section.

Adding openDesktop widget in KDE4 crashes plasma

Trying to add this widget will crash plasma, this is tracked in Image:bug_small.png Bug #52702.

Update: this bug has been fixed by an official update. See update advisory MDVA-2010:153.


Sound events enabled for various actions in GNOME

Some common actions (changing workspace, plugin / unplugin laptop power, etc..) might trigger sound events under GNOME. This behaviour will be fixed to be silent by default in a bugfix update.

No suspend/hibernate options from GNOME's battery applet/gnome-power-manager

This was an upstream decision. Enable the entries via gconf-editor (/apps/gnome-power-manager/ui/show_actions_in_menu) gnome-bug#597490


Clicking on a mailto link in Firefox doesn't open in the DE's default/preferred email application

Due to a bug that existed in Firefox when you clicked on a mailto link it sometimes doesn't load the DE's default/preferred email application. This has been fixed in 2010.0 and it should work for new Firefox profiles.

For already existing profiles you need to open Firefox > Edit > Preferences > Applications, then from the drop-down list for mailto select Use other, then browse to and select /usr/bin/xdg-email, this will make Firefox load the the DE's preferred application when you click a mailto link.

Alternatively you can directly select the executable of the application you want to use e.g. /usr/bin/kmail or /usr/bin/evolution ...etc.

Firefox sometimes marks all typed words as misspelled even though they are spelled correctly

For systems installed using the One Live CD typing in Firefox in a TEXTAREA, i.e. in a forum post or when sending an email, you might see that all words are underlined and marked as misspelled even though they're spelled correctly. This is easily solved by right clicking any erroneously underlined word and selecting the correct language from the Languages sub-menu.

This happens because the One CD's install a number of locales and myspell dictionaries, this seems to confuse Firefox and make it select a dictionary not matching the current system locale.

In Firefox flash content doesn't play smoothly or doesn't work at all

  • First of all make sure you have the latest Flash Player from Adobe, to check what, if any, version of Flash Player you have look at the output of this command rpm -q flash-plugin. Then check the latest version from Adobe. If you don't have the latest version then download the rpm package from that link and double click it to install it.
    • N.B. There's a package in the PLF repos, flash-player-plugin, that installs the Adobe flash plugin, creates the necessary symlinks, and uninstalls the swfdec and gnash free flash plugins (see below); the PLF repos can be added using the Easy Urpmi web site.
  • Uninstall any open source flash players e.g. swfdec-mozilla or gnash-firefox-plugin, either using rpmdrake (aka "Install & remove software") or as root in terminal (to become root use su):
urpme -a swfdec gnash
As stated in the previous point, the PLF flash rpm will uninstall these free flash plugins automatically as they interfere with the Adobe flash player.
  • If you're running 2009.1 or older releases make sure to uninstall libflashsuport, this package doesn't exist in 2010.0 as it was only needed to provide PulseAudio support for Flash Player 9; Flash Player 10 supports PulseAudio natively. This package is obsoleted, so if you do an upgrade from older releases it'll be removed automatically.
  • nspluginwrapper is reported to sometimes cause trouble when playing flash content; it's supposed to run the plugins in a separate process so that if a plugin crashes, Firefox itself would continue to run, this was needed in the past because of frequent crashes in Firefox when playing flash content, but with current Flash Player 10 and Firefox-3.5.x these crashes are rare. So if you're having trouble with Flash content, uninstall nspluginwrapper, again either using rpmdrake (aka "Install & remove software") or as root in terminal (to become root use su):
urpme -a nspluginwrapper.
  • 3D desktop effects sometimes cause flash content playing to be jerky, so disable any 3D desktop effects and see if flash plays better.
If you're running x86_64 Firefox

Adobe pulled their 64bit tarball from the Adobe Labs web site, (with a promise to “bringing native 64-bit Flash Player for the desktop by providing native support for Windows, Macintosh, and Linux 64-bit platforms in an upcoming major release of Flash Player”. This is mostly due to multiple security vulnerabilities found in flash player 10, (which has been corrected, only, in the i586 10.1 flash player). Naturally the PLF x86_64 flash player package has been removed too, see here for more info.

So for x86_64 installs the alternatives are:

  • Using the latest i586 flash player from Adobe (or the i586 PLF flash player package) and installing nspluginwrapper (bear in mind that nspluginwrapper is reported to cause some problems, as stated above)
    • N.B. The Adobe upstream flash player rpm doesn't create /usr/lib/mozilla/plugins if it doesn't already exist, this prevents it from creating the symlink /usr/lib/mozilla/plugins/libflashplayer.so -> /usr/lib/flash-plugin/libflashplayer.so which in turn prevents nspluginwrapper from working correctly with flash player plugin. For more info see: https://bugs.adobe.com/jira/browse/FP-5039 . For now you should ensure /usr/lib/mozilla/plugins exists before installing the upstream rpm by using this command in terminal:
mkdir -p /usr/lib/mozilla/plugins
  • Using the i586 Firefox package, or any other i586 web browser package, on an x86_64 installation with the i586 Adobe flash player, this is possible after first uninstalling the x86_64 Firefox package, in this case you won't need to install nspluginwrapper.

Firefox doesn't change the colour of visited links

This option is disabled, in Mandriva, by default in Firefox-3.6.x due to a privacy invading vulnerability where a web page can easily obtain info about users' browsing habits using a simple css or a javascript using the "colour" status of ":visited" links. Note that this option wasn't available in Firefox versions older than 3.5.

Links: https://bugzilla.mozilla.org/show_bug.cgi?id=147777 http://support.mozilla.com/tiki-view_forum_thread.php?locale=hu&comments_parentId=438422&forumId=1 http://davidwalsh.name/jquery-spyjax

If you don't care about this vulnerability, you can revert this change by typing about:config in Firefox address bar then pressing Enter, search for layout.css.visited_links_enabled and double click it to change it to true.

Under KDE4, the buttons in message dialogues in Firefox-3.6.x are laid out differently

The Firefox-3.6.x update brings with it KDE4 integration patches, so now under KDE4, Firefox-3.6.x will use the KDE4 buttons layout specification, i.e. the Apply/Yes buttons will be on the left and the Cancel buttons on the right... etc.

Opening hyperlinks from some GTK-based applications doesn't work after updating Firefox to a new version

Using make firefox the default web browser functionality in Firefox modifies some gconf configuration files in the user's /home (in .gconf), and makes it set /usr/lib(64)/firefox-<firefox version>/firefox as the default web browser. After Firefox is updated /usr/lib(64)/firefox-<firefox version>/firefox is changed to reflect the new version, this breaks opening hyperlinks in some GTK-based applications, e.g. Thunderbird. This issue has been fixed to make Firefox always use /usr/bin/firefox when that functionality is used.

If you ever used any application that modified those gconf settings then you may need to fix this issue manually by using one of the following methods:

  • If you're running GNOME, use System -> Preferences -> Preferred Applications
  • Running these two commands as user in terminal (should work for all DE's including GNOME):
gconftool-2 --set --type string /desktop/gnome/url-handlers/http/command 'www-browser "%s"'
gconftool-2 --set --type string /desktop/gnome/url-handlers/https/command 'www-browser "%s"'
  • Install gconf-editor and launch it as user from terminal, then navigate to /desktop/gnome/url-handlers/ and change the command values for both http and https to:
www-browser "%s"

www-browser will make it use the browser you set as the default in the DE you're running.

You can replace www-browser with whatever web browser you want, e.g. /usr/bin/firefox, /usr/bin/opera or /usr/bin/chromium-browser ...etc. Also note that both Firefox and Chromium browsers have built in options to modify those settings.

N.B. Due to the Firefox/KDE4 integration using the make firefox the default web browser functionality in Firefox won't modify gconf settings any more if you're running KDE4, you can easily use one of the methods listed above to fix this issue.


Functionalities which do not work in One edition

Mandriva Linux 2010.0 One edition does not include a Java environment due to the lack of space. OpenOffice.org relies on several Java features and that will not work on One edition when running live. Bellow is a list of such functionalities:

  • Creating databases, forms and user controls using Base app;
  • Accessing any type of database in Base which requires a JDBC connector;
  • Saving and 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 using Writer app;
  • Saving and exporting to Pocket Excel (.pxl), Microsoft XML 2003 Excel format (.xml) , OpenDocument SpreadSheet(Flat XML)(.fods) and Unified Office Format spreadsheet (.uos) using Calc
  • Saving and exporting to OpenDocument Presentation (Flat XML) (.fodp) and Unified Office Format presentation (.uop) in Impress
  • Saving and exporting to Saving file as to: OpenDocument Drawing (Flat XML) (.fodg) using Draw app;
  • Letter, Fax, Agenda and Web Page wizards using all OpenOffice.org apps;
  • Exporting to XHTML (.xhtml, .html) using all OpenOffice.org apps;
  • Saving documents containing macros written in JavaScript or Beanshell using all OpenOffice.org apps;
  • Known problems: Image:bug_small.png Bug #44644 and Image:bug_small.png Bug #45269.

To recover such features just install the openoffice.org-java-common package since you had installed the One edition on some writable device as your hard disk.

No icons on toolbar, only text

This is a known bug. As a workaround you can apply one of two solutions, You can install openoffice.org-style-galaxy package and remove other openoffice.org-style-* packages or
Follow below steps that user MikhailZ has suggested:

1. delete .ooo3 in home (on LXDE ~/.config/.ooo3)
rm -fr ~/.ooo3 
rm -fr ~/.config/.ooo3
2. create file /usr/lib/ooo/share/registry/data/org/openoffice/Office/Common.xcu

contains this

<?xml version="1.0" encoding="UTF-8"?>
<oor:component-data xmlns:oor="http://openoffice.org/2001/registry"
xmlns:xs="http://www.w3.org/2001/XMLSchema" oor:name="Common"
 <node oor:name="Misc">
  <prop oor:name="SymbolStyle" oor:type="xs:string">
  <prop oor:name="SymbolSet" oor:type="xs:short">

Image:bug_small.png Bug #53284

3D accelerated desktop

Video playback glitches

See also Image:bug_small.png Bug #25572. If you use the 3D accelerated desktop technologies included in Mandriva Linux , 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. You should use the x11 / xshm output driver.

  • 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 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.
Personal tools