Amarok/Manual/Various/TroubleshootingAndCommonProblems/da: Difference between revisions
(Importing a new version from external source) |
(Importing a new version from external source) |
||
Line 25: | Line 25: | ||
Den aktuelle spilleliste kan undertiden blive ødelagt, hvilket vil forhindre '''Amarok''' i at starte op. Dette kan løses ved simpelt hen at fjerne den aktuelle spilleliste i '''Amaroks''' mappe: <tt>$HOME/.kde/share/apps/amarok/current.xspf</tt>. Bemærk, at du på nogle systemer skal skrive <tt>.kde4</tt> i stedet for <tt>.kde</tt>. | Den aktuelle spilleliste kan undertiden blive ødelagt, hvilket vil forhindre '''Amarok''' i at starte op. Dette kan løses ved simpelt hen at fjerne den aktuelle spilleliste i '''Amaroks''' mappe: <tt>$HOME/.kde/share/apps/amarok/current.xspf</tt>. Bemærk, at du på nogle systemer skal skrive <tt>.kde4</tt> i stedet for <tt>.kde</tt>. | ||
==== | ==== Problemer med databasen ==== | ||
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'''. | 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'''. |
Revision as of 10:28, 19 December 2011
Fejlsøgning og almindelige problemer
Hvis du arbejder dig igennem procedurerne på denne side uden held, så kontakt os på IRC (irc://irc.freenode.org/amarok), i KDE-forumets sektion for Amarok eller skriv til Amaroks postlist.
Problemer med installation
Dårkige pakker
Det sker undertiden, at brugere kommer ud for dårlige pakker fra deres distribution; enten fordi den inkluderer en forkert version af en komponent eller fordi den mangler en vigtig del. Af en eller anden grund sker det ofte med MySQL-komponenter. Fejlrapporter om disse problemer skal rettes til din distribution, ikke til bugs.kde.org.
Problemer med at bygge fra kildekoden
For de, der ønsker at hjælpe med at teste den nyeste version af Amarok er det tilrådeligt at bygge en lokal udgave. Brug denne glimrende guide: Compiling Amarok from GIT Locally; a Full Summary. Detaljeret information om git kan findes her: Techbase GIT Tutorial.
Hvis du tidligere har bygget med held og nu støder på fejl, så prøv at fjerne CMakeCache.txt og prøv igen. Hvis der stadig opstår fejl, så slet hele bygge-mappen og start helt forfra.
URL'en til at pull'e fra git er blevet ændret for nylig. Kør
git remote set-url origin git://anongit.kde.org/amarok
hvis du stadigbruger den gamle URL. Kontakt os venligst, hvis du finder det gamle link i vore dokumenter, sådan at vi kan opdatere alting.
Problemer med opstart
Fejl i spillelisten
Den aktuelle spilleliste kan undertiden blive ødelagt, hvilket vil forhindre Amarok i at starte op. Dette kan løses ved simpelt hen at fjerne den aktuelle spilleliste i Amaroks mappe: $HOME/.kde/share/apps/amarok/current.xspf. Bemærk, at du på nogle systemer skal skrive .kde4 i stedet for .kde.
Problemer med databasen
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
.If you don't want Amarok scanning for changes, uncheck that, and use
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
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 , 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
. 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.
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