I recently updated my Ubuntu system after using amarok for the 6 months prior to Feisty's release. I really love amarok but since updating my system when amarok is started up, it tries to update my collection this update then gets stuck on 90%, the CPU shoots right up, amarok becomes unbearable slow and at times unresponsive, and anything I add to the playlist is doubled.

I'm running Ubuntu 7.04 Feisty Fawn, Amarok 1.4.5

As a note the 'related artists' box under context changes every time the collection tries to update and gets stuck. Don't know if that is relevent.

Just ran amarok from the command line and got these error messages:

Code: Select all

X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  147
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  147
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  147
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  147
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x81357f0 ): KAccel object already contains an action name "play_pause"
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x81357f0 ): KAccel object already contains an action name "play_pause"
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow


Try to remove the settings:

rm -rf ~/.kde/share/apps/amarok
rm ~/.kde/share/config/amarokrc

Thanks for the help but it didn't seem to work. Any other suggestions?

Yeah: When it gets stuck, look at the file ~/.kde/share/apps/amarok/collection_scan.log. The file that's listed in there is probably the culprit. Remove it from your collection.

There was nothing listed in the above file.

Dag nabbit. 

I have quite a few partially downloaded files in my collection folders could this be the cause of the problems? It's never been a problem before though apart from them being added to the collection.

Can I ask is this symbol '~' meant to represent a folder relevant to my machine or is it actually part of the path?

On Ubuntu do I have a .kde folder?

I'm a bit of a n00b so any help is greatly appreciated.

:]

Both, when ~ is used at the start of a path, it is expanded to your home directory. For example, try "cd ~", it'll put you into your home directory. (If you hit tab after it, it might expand right there for you.) You can also use it to specify the home directory of another user, like if there was a user named John, you could use ~john for /home/john, or wherever his home might be.

Thanks thats a help.

I managed to get to the collection scan file and find found a song written there, deleted that song, got stuck again, another song was written there and then the cycle kept repeating. I've just disabled all the collection directories and recursive scanning. Seems okay if a little slow but I think that that's something to do with beryl. 

Try disabling the directories that contain the unfinished songs. See if that'll fix it.

By the way, which database are you using? SQLite, MySQL, or PostgreSQL? (If you don't know, it's probably SQLite.)

Yes I'm not sure. I have disabled amarok from looking in my music folders as said above. It seems to have helped but when I add songs to the playlist they are still doubled. I wish I was more experienced with Linux generally, to be able to tell you in more detail what is going wrong.

Do the terminal error messages not mean anything?

No, those errors don't mean much. The ones starting with "X Error" are caused by entries in /etc/X11/xorg.conf about a wacom touchpad, which are moronically enabled by default. The others are just from Qt, which is the interface thingy for Amarok. No troubles there.

I can't think of what to do. Try purging Amarok ("sudo apt-get remove --purge amarok"), removing configurations and the databases. (Make backups.) Then reinstall Amarok.

I did the purge thing and reinstalled amarok, I also deleted the locally cached installation files but I wasn't sure where to find the database files. After reinstallation I still have the problem amarok is unusable due to the update collection getting stuck on 90% (i thinks it's more a symptom that a cause though).

Think I'll try using an older version of Amarok because before updating to Feisty it was fine.

Actually, I think this is now an accepted bug with Amarok and Feisty.  I have the exact same problem as the last poster.  Since upgrading to Feisty, my Amarok will no longer work.  It is freezing at 90% on the updating bar at the bottom.  I've already tried reinstalling.  I'm going to try purging and reinstalling, but I have a feeling that isn't going to do much besides waste my time.