Amarok/Manual/Various/TroubleshootingAndCommonProblems/pt-br

Solução de problemas e Problemas comuns

Se você seguir os procedimento aqui descritos, mas se não tiver sucesso, entre no IRC (irc://irc.freenode.org/amarok), cadastre a sua dúvida no Fórum do KDE, na seção do Amarok ou escreva na lista de discussão do Amarok.

Problemas na instalação

Pacotes inválidos

Ocasionalmente, os usuários irão encontrar pacotes com problemas nas distribuições; ou têm uma versão errada de um componente incluído ou ficou a faltar algo de importante. Por alguma razão, isto normalmente ocorre com as dependências do MySQL. Os relatórios de erros nestes casos deverão ser feitos com a sua distribuição, não com o bugs.kde.org.

Dificuldades na compilação a partir do código-fonte

Para as pessoas que desejam ajudar a testar as versões mais recentes do Amarok, existe uma versão para compilação local. Use este excelente guia: Compilando o Amarok localmente a partir do GIT - um resumo completo (em inglês). Informações detalhadas sobre o git podem ser encontradas aqui: Tutorial da Techbase sobre o GIT.

Se você já conseguiu compilar com sucesso anteriormente e agora está encontrando erros, tente remover o arquivo CMakeCache.txt e tente novamente. Se os erros persistirem, remova totalmente a pasta de compilação (Build) e faça uma nova compilação.

A URL para obter o código do Git foi alterada recentemente. Execute o comando

git remote set-url origin git://anongit.kde.org/amarok

se você ainda estiver usando a URL antiga. Por favor, contacte-nos se você ainda encontrar o link antigo na documentação, para que ele possa ser atualizado em todos os locais.

Problems starting up

Playlist errors

The current playlist can occasionally get corrupt, which will prevent Amarok from starting. This can be fixed by simply removing the current playlist file in the Amarok directory, $HOME/.kde/share/apps/amarok/current.xspf . Note that on some systems, this may be .kde4 rather than .kde.

Database issues

If the database is corrupt and this is preventing Amarok from starting, you can move the database to a backup location (or simply delete it). This will cause Amarok to rebuild the database from scratch. Move the $HOME/.kde/share/apps/amarok/mysqle folder to a backup location (such as $HOME/.kde/share/apps/amarok/mysqle~) and restart Amarok.

Other issues and backing up settings

If the above two items do not help, or you otherwise need to restore Amarok to a clean configuration, you can move to a backup location (or delete) the Amarok directory at $HOME/.kde/share/apps/amarok and the Amarok config files at $HOME/.kde/share/config/amarok* (there may be two or three files matching this pattern). Again, the directory may be .kde4 rather than .kde.

Problems Scanning, Sorting files

Amarok scans your music files on first startup, and will keep your collection up-to-date automatically, if you chose Settings -> Configure Amarok -> Collection -> Watch folders for changes.

If you don't want Amarok scanning for changes, uncheck that, and use Tools -> Update Collection whenever you make changes to your collection.

More about Amarok collection scanning here.

Corrupt tags

Some folks notice that Amarok seems to be missing some files. One of the causes can be corrupt tags, which you can check using the tagging application kid3. More about tagging here.

To find the bad file(s), run amarokcollectionscanner from the console. Details here.

Inability to write tags

If Amarok is not saving changes to tags, you may have permissions problems. Ensure that your user has write permissions to your music. For example,

chown -R youruser Music/

to change ownership to your user, or

chmod -R +w Music/

to add write permissions to the owner.

Incorrect Sorting (Various Artists)

Sometimes people report that tracks are in Various Artists when they should not be, or are sorted into "Unknown Album." What separates Various Artists albums and tracks and albums sorted under their artists is the Album Artist tag. When you click Show under Various Artists in the context (right-click) menu, that tag will be emptied if it is filled. The opposite happens to a file in Various Artists when you choose Do not show under Various Artists, but the Album Artist tag will be auto-filled from the Artist tag.

If there is no Album tag, and no Album Artist tag, Amarok will put the track into Unknown Album in Various Artists. If you want them sorted otherwise, tag them the way you want them sorted. If you don't know some of the information, try out the new MusicBrainz function in the tag editor, or use a tagging application.

Problems playing files

Amarok skips over tracks, or appears to play them without sound

If the files you are attempting to play are in mp3 format, please see instructions for enabling mp3 support on your distro, here. Note that one piece of software being able to play mp3s on your system does not necessarily mean Amarok has had the required codecs installed.

No sound, or bad sound

For more general sound issues, first check what Phonon backend you are using in Settings -> Configure Amarok -> Playback -> Configure Phonon -> Backend. Consider switching to a different backend; VLC, GStreamer and Xine backends should be available from your distribution, although Xine is deprecated. Gstreamer or VLC is usually recommended.

Also check whether the backend standalone software can play the files correctly; if not this is an issue with that software and you may find information in their help files. In other words, can Gstreamer or VLC play the same file? Will it play in Dragon, which also uses phonon?

If it seems to be a PulseAudio problem, and you want to provide a log to the PulseAudio developers, the troubleshooting page is here.

Problems with collections on iPod etc.

Amarok show no cover-images or images are lost when transferring to device

Most likely the wrong version of libgpod4 is installed. On Debian and it's derivatives like Kubuntu the default is libgpod4-nogtk, which comes without support for covers. Simply install the variant libgpod4:

sudo apt-get install libgpod4

The package libgpod4-nogtk can then be removed without problem. This is currently under review for Kubuntu Quantal (to be released as 12.10) and will likely be changed to the default libgpod4 in the future.

Crashes and bugs

• How to run Amarok from the command line:

  amarok --debug --nofork

• Amarok crashes, but Dr. Konqi doesn't pop up — run in gdb with the following command:

  gdb --args amarok --debug --nofork

  In gdb's console, type run to start Amarok, reproduce the crash, and then in gdb type thread apply all bt to generate the backtrace.

• Filing bugs: If triggered, Dr. Konqi will provide an option to report a bug and do most of the work for you. If not, you will need to submit the bug manually at bugs.kde.org. For crash bugs, paste the backtrace from gdb as a comment.

• How to get personal support with problems: IRC (#amarok on Freenode IRC), Forum, Mailing list

• ← Amarok on OS X
• ↑ Back to Menu ↑
• FAQ →