Errata do Mandriva Linux 2009

De Wiki da Comunidade Mandriva

Mandriva Linux 2009 Errata - Em Construção, traduzindo


Tradução sendo retirada de http://wiki.mandriva.com/en/2009.0_Errata

Errata do Mandriva Linux 2009


Tabela de conteúdo

Introdução

Esta página contém a Errata para o Mandriva Linux 2009. Isto quer dizer que esta página contem informações sobre problemas conhecidos no Mandriva Linux 2009 e, onde está disponível, como resolver, prevenir ou trabalhar em torno deles. Vocẽ deve ver também o Notas de Lançamento, que contém mais informações gerais sobre o Lançamento do Mandriva Linux 2009.

Errata para versões anteriores do Mandriva Linux

Outras páginas de errata estão disponíveis para versões mais antigas do Mandriva Linux:

Testando Futuras Atualizações

Quando algum problema é identificado no Mandriva Linux, o mantenedor do pacote se encarrega de construir um novo pacote com uma potencial correção, envia o pacote para o repositório de testes /main/testing 

que é exclusivo para pacotes em testes. Estes pacotes são então testados pelos usuários que detectaram e reportaram o problema e pelo time de QA - Quality assurance da Mandriva. Se os testes confirmam a correção do problema e que a correção não gera regressões(perda de funcionalidade), o pacote é lançado como atualização oficial, e fica disponível para todos os usuários do Mandriva Linux através do MandrivaUpdate

.

Se você encontrou um problema em algum pacote e sabe que há uma versão corrigida para testes no /main/testing 

e gostaria de ajudar testando, você deve configurar a ferramenta de gerenciamento de pacotes do Mandriva Linux para que ele busque pacotes nesse repositório de testes. Para instruções de como fazer isso leia Instalando e Removendo Software (uso avançado: Backports e Candidatos a  Atualização)

Existe também o repositório /contrib/testing 

que faz a mesma coisa que pacotes da sessão /main/testing
o diferencial é que o /contrib/testing
contém somente atualizações feitas pela comunidade (note que a Mandriva suporta pacotes da/contrib
e que serão ou imediatamente atualizados após testes, pois estes são pacotes mantidos pela comunidade e não pelo time de desenvolvedores oficial da Mandriva). Como configurar estes repositórios também é abordado na página citada acima.

Instalando Atualizações

As atualizações oficiais do Mandriva Linux são instaladas pelo MandrivaUpdate e opcionalmente pelo Instalar & Remover Software do menu principal. Você inicia o "MandrivaUpdate" através do "Centro de Controle Mandriva", navegando até a aba "Gerenciamento de Software" depois clica no link "Atualizar seu sistema", você também é notificado sobre atualizações disponíveis através de um ícone que fica na barra de ferramentas, ao lado do relógio.

Problemas já Resolvidos

Esta seção lista os problemas que já foram corrigidos por atualizações Oficiais.

== Driver Proprietário NVIDIA não Funciona com kernel-server 

==

O Driver proprietário NVIDIA não funcionava com o Mandriva Linux 2009 usando o kernel kernel-server . Este problema foi mais notado em máquinas recentes, poderosas máquinas de Desktop que tinham 4 ou mais GB de memória RAM; kernel-server 

por padrão, é instalado em todas as máquinas com 4GB de RAM ou mais assegurando o uso de toda a memória RAM. O pacote atualizado do nvidia-current, nvidia-current-177.70-2.3mdv2009.0

, foi lançado e está disponível como atualização oficial do Mandriva 2009. Use o MandrivaUpdate para baixar e instalar esta atualização, você será notificiado pelo sistema sobre esta e todas as outras atualizações automaticamente.

Problemas de Instalação

Problemas depois de ter feito uma atualização online do Mandriva 2008 Spring para o 2009

Um novo recurso do Mandriva 2009 é a capacidade de fazer uma atualização online pelo modo gráfico, de 2008 Spring para 2009, através da notificação de atualização do sistema do Mandriva Online. Em 10 de Outubro de 2008, os usuários do Mandriva 2008 Spring foram avisados de uma nova versão, e foi oferecido uma atualização para isto. Os usuários que tentaram usar o sistema nesta vez podem ter achado que a atualização não funcionou corretamente: ao reiniciar o sistema dentro do "processo de atualização do sistema", talvez, ao iniciar, você esteja impossibilitado de entrar nele pelo modo gráfico, ou vários coisas podem estar quebradas ou faltando. Isto ocorre porque o processo nao foi feito da maneira correta o suficiente para o prevenir de diversos problemas potenciais que podem ocorrer durante a atualização, incluindo espelhos (mirrors) ocupados causando falha nos downloads (e, consequentemente, atualizações) dos pacotes, ou nao existe espaço em disco suficiente no sistema para que a atualização se complete com sucesso.

Se você está passando por um problema de atualização, os seguintes procedimentos podem resolver isto. Aperte ctrl-alt-F1 para ir ao console. Autentique-se como root, e execute este comando: 

urpmi --auto-update -v

e prossiga assim até terminar de atualizar. Isto deve então atualizar os pacotes que não foram atualizados durante a atualização inicial. Se o processo indicar que alguns pacotes não foram habilitados ainda para serem atualizados devido a problemas nos mirrors (espelhos), execute o comando até todas as atualizações possíveis tiverem sido instaladas corretamente. Uma vez que esteja completo, execute reboot 

para reiniciar o sistema. A atualização deverá agora ser finalizada corretamente.

A partir do dia 13 de outubro de 2008, a atualização online via modo gráfico foi temporariamente desabilitada: Os usuários do Mandriva Linux 2008 Spring não serão informados da atualização disponível para o 2009. Isto acontece para que possamos implementar e testar aprimoramentos neste processo afim de evitar estes problemas. Uma vez que, para nossa satisfação, estes aprimoramentos tiverem sido implementados, a atualização via modo gráfico será reabilitada, e futuras atualizações nao deverão sofrer estes problemas.

Problemas de Kernel

Congelamento periódico do ambiente gráfico

Veja também Image:bug_small.png Bug #42833 . Alguns usuários do Mandriva Linux 2009 tem experimentado um bug onde periodicamente ocorre um congelamento do sistema quando este está sendo executado no modo gráfico. Quando isto ocorre, é possível ainda usar o atalho ctrl-alt-F1 para acessar o modo texto. Este problema é causado por um bug nos modulos DRM do kernel fazendo com que o servidor gráfico X.org entre num loop infinito. Para diagnosticar este problema, depois do ambiente gráfico congelar, verifique o arquivo de log do X.org /var/log/Xorg.0.log 

num console em modo texto. A constante presença das seguintes linhas é uma indicação deste 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.

Para resolver este problema, no menu de boot do Mandriva Linux 2009, selecione a opção chamada linux-nonfb, ao invés da opção padrão. Você pode ajustá-la permanentemente como a opção padrão na ferramenta de configuração de boot do mandriva, acessível pelo Centro de Controle do Mandriva, na aba Boot, chamada Set up boot system. Fazendo isto você desabilitará o vídeo framebuffer, o que quer dizer que você não verá nem o boot e nem o desligamento gráfico.

Boot pausa indefinidamente em pontos variados até que um tecla seja pressionada

Veja também Image:bug_small.png Bug #44342 . Na maioria dos sistemas, incluindo o Sony Vaio PCG-GRT-815E, o boot processará pausadamente indefinidamente em diversos pontos até você pressionar uma tecla. Quando a tecla é pressionada, continuará o boot. Se você pressionar uma tecla cada vez que pausa, eventualmente o boot será completado sem problemas.

Essa questão está sob investigação, e será solucionada em uma futura atualização oficial do kernel. É possível trabalhar em torno desse problema adicionando as seguintes linhas no arquivo /etc/modprobe.d/blacklist-mdv 

blacklist thermal
blacklist processor

ou usando os seguintes parâmetros de kernel: 

clocksource=jiffies

Os parâmetros de kernel podem ser adicionados usando a ferramenta de configuração de boot do Mandriva, disponível no Centro de Controle do Mandriva.

Missing module dependency information slightly increases boot time

A small bug in the kernel package included with Mandriva Linux 2009 slightly increases boot time. You can work around this by running the command depmod , as root. This should reduce boot time by around two to three seconds. This bug will be resolved in all future official kernel updates.

A candidate fix has been uploaded to the /main/testing 

package repository: kernel-2.6.27.4-0.uc1mnb2

. 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.

Installing VMware on Mandriva fails due to wrong GCC version used to compile kernel

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) will refuse to build their kernel modules when you attempt 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. This will be fixed with an official kernel update.

A candidate fix has been uploaded to the /main/testing 

package repository: kernel-2.6.27.4-0.uc1mnb2

. 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.

Hardware issues

Eee systems do not shut down correctly

See also Image:bug_small.png Bug #44752 . Several users have reported that Eee systems including at least the 701 do 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 

rmmod snd-hda-intel

We are working to identify a fix for this issue, and it will be fixed in an official kernel update as soon as possible.

Wireless networking stops working if disabled and then re-enabled with Fn+F2 on Eee models

See also Image:bug_small.png 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 potential fix for this issue has been identified, and it will likely be resolved with an official kernel update.

Marvell 88SE61 series drive controllers do not work

See also Image:bug_small.png 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.

Continuous loud noise from the sound device

See also Image:bug_small.png Bug #44703 . Several users have 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).

No sound on various snd-hda-intel-based sound devices

See also Image:bug_small.png Bug #44855 

and Image:bug_small.png 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. If you have an Intel HDA codec-based sound device and sound does not work for you, please try the candidate update to see if it resolves the issue for you.

A candidate fix has been uploaded to the /main/testing 

package repository: kernel-2.6.27.4-0.uc1mnb2

. 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)

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. 216.105.167.65). 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 Image:bug_small.png 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 

net.ipv4.tcp_window_scaling=0

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.

TCP timestamps

See also Image:bug_small.png Bug #43372 . 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. If your network connection appears to be correctly configured and working, but internet traffic does not appear to work, this may be the problem for you. Try to disable the timestamps, using this command, run as root:

sysctl -w net.ipv4.tcp_timestamps=0


If this fixes the problem, and you own a router, the bug may be in the router: see if a firmware update is available for it, and if there is not (or the update does not fix the problem), notify your router manufacturer. If you do not have a router, or the problem persists if you bypass the router, the bug is likely at your ISP or further upstream. To make the change permanent, add this line to the file /etc/sysctl.conf 

net.ipv4.tcp_timestamps=0

A candidate fix has been uploaded to the /main/testing 

package repository: kernel-2.6.27.4-0.uc1mnb2

. 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 network response with Realtek wireless internet adapters (using the rt2500pci driver)

See also Image:bug_small.png Bug #42180 . It has been reported that Realtek 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: 

rate 54M

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.

Problemas de Software

Ferramenta de configuração da impressora não está instala por padrão na edição One

Veja também Image:bug_small.png Bug #43635 . A nova ferramenta de configuração de impressora, system-config-printer , não está sendo instalada por padrão quando instala o Mandriva Linux 2009 a partir da edição One.Isso significa que não há opção de configurar um impressora. Para resolver este problema, simplesmente use a ferramenta de gerenciamento de software do Mandriva (Instalar & Remover Software) para instalar o pacote system-config-printer . Após fazer isso, a ferramenta de configuração de impressora estará disponível no Centro de Controle do Mandriva, na aba Hardware.

Edição One falha no boot na interface gráfica do desktop (xorg.conf não é criado)

Veja também Image:bug_small.png Bug #43870 . Muitos usuários reportaram que a edição One do Mandriva Linux 2009 falha na criação do arquivo /etc/X11/xorg.conf 

quando a máquina está no boot.

Isso pode resultar em vários cenários. O que pode acontecer é que o X.org tentará detectar automaticamente a placa e o driver apropriado. Se vocẽ tiver sorte, ele conseguirá, e você nunca notará esse probelma.

Se a auto-configuração do X.org falhar inteiramente, isso resultará em uma falha no início da interface gráfica do desktop. Neste caso, One dará o boot em modo texto.

No pior dos casos, a auto-configuração X.org achar um driver válido mas falhar no trabalho devido a um conflito com o sistema de framebuffer, resultando em um aparente falha no boot: uam tela branca com o cursor piscando no canto superior esquerdo. Há duas abordagens de você achar-se nesta situação. Você pode reiniciar o boot e usar o modo texto, antes do gráfico, no boot - essa opção está somente disponível na edição One na tela de boot apertando F3. Isso poderá resultar em boot gráfico com sucesso, embora ótimo o driver para sua máquina é importante não ser usado. Você pode então rodar a ferramenta de configuração de vídeo através do Centro de Controle do Mandriva para gerar o arquivo /etc/X11/xorg.conf , se desejar; poderá fazer isso se destinar a One para instalação permanente. Se fizer isso e então instalar a One em seu disco rígido, a emissão não será recuperada quando estiver no boot com o sistema instalado.

Alternativamente, quando você ver a tela branca, pressione Alt+F2 para entrar na tela de login. Você poderá logar como root (sem senha) e rodar o drakx11 . Aceite todas as configurações padrões na ferramenta, e feche-o. Então rode o comando service -f dm , e desktop gráfico aparecerá corretamente. Se você instalar o One no disco rígido, essa emissão não será recuperada quando estiver no boot com o sistema instalado. Entretanto, ele recuperará cada ver que você der o boot pelo CD do One.

Se você desejar verificar que isso é realmente o problema e sofrerá com ele, simplesmente cheque se o arquivo /etc/X11/xorg.conf 

existe.

Encrypted partitions are not mounted during boot

See also Image:bug_small.png 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 Image:bug_small.png 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:

DISPLAY="" drakconnect

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 Image:bug_small.png 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-4.150.10.5.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).

Mandriva network configuration tools do not correctly handle wireless encryption keys containing some special characters

See also Image:bug_small.png 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: 

WIRELESS_ENC_KEY="s:KEY"

Where KEY is the key. So if the key was FOOBAR!@%=, you would edit the line to read: 

WIRELESS_ENC_KEY="s:FOOBAR!@%="

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: 

WIRELESS_ENC_KEY='s:FOOBAR!"@%='

This issue will be addressed in a future official update.

Mandriva tool for accessing Windows / SMB / CIFS / Samba shares does not work

See also Image:bug_small.png 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.

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 Image:bug_small.png 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 Image:bug_small.png 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.

Extended keys (multimedia keys) not supported in KDE 4

See also Image:bug_small.png 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.

KDE 4 panel displays graphical corruption when running GTK+-based applications

See also Image:bug_small.png 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 Image:bug_small.png 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 Image:bug_small.png 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 Image:bug_small.png 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.

Evolution cannot send messages when using an Exchange server

See also Image:bug_small.png Bug #44908 . A bug in the evolution 

package provided with Mandriva Linux 2009 prevents outgoing mails from being sent when the outgoing mail server is an Exchange server (via the evolution-exchange
plugin). Evolution will appear to be sending the mail, but the operation will never complete.

A candidate fix has been uploaded to the /main/testing 

package repository: evolution-2.24.0-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 evolution packages.

Mandriva interactive firewall configuration tool too large for low-resolution displays

See also Image:bug_small.png 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.

Webcam support in Skype

Several webcams that use the gspca driver included in the new kernel don't work with Skype out of the box. As a workaround, install the 32 bit version of the package libv4l and run Skype using this command: 

LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so skype

Mandriva Linux 2009 fails to boot when installed as a KVM guest system

See also Image:bug_small.png 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 Image:bug_small.png 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
  • Saving documents containing macros written in JavaScript or Beanshell in all modules

Again, to restore these functions, simply install the openoffice.org-java-common 

package.

Smart broken with lzma compressed metadata

See also Image:bug_small.png 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

3D-accelerated desktop and video playback

See also Image:bug_small.png 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):
vo=x11

For OpenGL output, add the following line instead:

vo=gl2
  • 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".
Obtido em "http://wiki.mandriva.com/pt/Errata_do_Mandriva_Linux_2009"
Ferramentas pessoais
Fund the Mandriva Linux project