I'm running amarok-svn as of today, and this may just be an svn problem.  If that's the case then I'll just wait until it's resolved.  The last build I had was working fine though so I don't think there are any other issues going on here.

I'm using the gentoo svn ebuild for amarok.

I don't have debugging but I did run an strace on the app.  I don't understand strace output too well though so I am not sure how helpful it will be.  I can tell where it's getting stuck but I don't really understand what it means to resolve it.
Hmm, I found out something interesting, it will start in root so this has to be an issue with some part of my kde configuration on my user... I'm just not sure.. what.. because previous versions were fine.

Code: Select all

read(3, "\1\1\217\207\0\0\0\0T\0 \2\206\2\35\2\300\26h\0\0\0\0\000"..., 32) = 32
gettimeofday({1156618790, 932779}, NULL) = 0
gettimeofday({1156618790, 932910}, NULL) = 0
gettimeofday({1156618790, 933049}, NULL) = 0
gettimeofday({1156618790, 933171}, NULL) = 0
gettimeofday({1156618790, 933294}, NULL) = 0
gettimeofday({1156618790, 933420}, NULL) = 0
gettimeofday({1156618790, 933544}, NULL) = 0
gettimeofday({1156618790, 933680}, NULL) = 0
gettimeofday({1156618790, 933803}, NULL) = 0
gettimeofday({1156618790, 933929}, NULL) = 0
gettimeofday({1156618790, 934053}, NULL) = 0
gettimeofday({1156618790, 934176}, NULL) = 0
gettimeofday({1156618790, 934311}, NULL) = 0
gettimeofday({1156618790, 934457}, NULL) = 0
ioctl(9, FIONREAD, [0])                 = 0
write(11, "\0", 1)                      = 1
write(3, "\n\0\2\0O\0 \2\31\0\v\0R\0\0\0\0\0\30\0\22\0\0\0R\0\0\0"..., 52) = 52
gettimeofday({1156618790, 935442}, NULL) = 0
write(14, "\1\2\1\0?\0\0\0\331\2\0\0", 12) = 12
write(14, "\0\0\0\7amarok\0\0\0\0\vDCOPServer\0\0\0\0\1\0\0"..., 62) = 62
write(14, "\1", 1)                      = 1
read(14, "\2\3\0\2\'\0\0\0", 8)         = 8
read(14, "\331\2\0\0", 4)               = 4
read(14, "\0\0\0\vDCOPServer\0\0\0\0\7amarok\0\0\0\0\5vo"..., 39) = 39
write(14, "\1\2\1\0\300\0\0\0\331\2\0\0", 12) = 12
write(14, "\0\0\0\7amarok\0\0\0\0\vDCOPServer\0\0\0\0\0\0\0"..., 103) = 103
write(14, "\0\0\0\5kded\0\0\0\0\rmediamanager\0\0\0\0\25me"..., 89) = 89
read(14, "\2\3\0\2(\0\0\0", 8)          = 8
read(14, "\331\2\0\0", 4)               = 4
read(14, "\0\0\0\vDCOPServer\0\0\0\0\7amarok\0\0\0\0\5bo"..., 40) = 40
write(14, "\1\2\1\0\304\0\0\0\331\2\0\0", 12) = 12
write(14, "\0\0\0\7amarok\0\0\0\0\vDCOPServer\0\0\0\0\0\0\0"..., 103) = 103
write(14, "\0\0\0\5kded\0\0\0\0\rmediamanager\0\0\0\0\27me"..., 93) = 93
read(14, "\2\3\0\2(\0\0\0", 8)          = 8
read(14, "\331\2\0\0", 4)               = 4
read(14, "\0\0\0\vDCOPServer\0\0\0\0\7amarok\0\0\0\0\5bo"..., 40) = 40
write(14, "\1\2\1\0\304\0\0\0\331\2\0\0", 12) = 12
write(14, "\0\0\0\7amarok\0\0\0\0\vDCOPServer\0\0\0\0\0\0\0"..., 103) = 103
write(14, "\0\0\0\5kded\0\0\0\0\rmediamanager\0\0\0\0\27me"..., 93) = 93
read(14, "\2\3\0\2(\0\0\0", 8)          = 8
read(14, "\331\2\0\0", 4)               = 4
read(14, "\0\0\0\vDCOPServer\0\0\0\0\7amarok\0\0\0\0\5bo"..., 40) = 40
write(14, "\1\2\1\0<\0\0\0\331\2\0\0", 12) = 12
write(14, "\0\0\0\7amarok\0\0\0\0\5kded\0\0\0\0\rmediaman"..., 56) = 56
write(14, "\0\0\0\5", 4)                = 4
read(14,                         


I decided to go ahead and just backup/remove my previous kde configuration since that was the only difference from root.  I noticed with root that I could have the same exact configuration files with no problems, so it was apparently something else in the .kde directory messing it up.

Sure enough just mv .kde3.5 .kdebk & copying in my previous collection files made it work again.

But I have absolutely no idea what went wrong with it.

strange - some people have reported similar problems (as KDE users) with amarok not starting as their main user after a kde upgrade, and as you discovered, when they either created a new user, or tried wiping their .kde directory and restarting, it worked.

Noone's managed to figure out yet exactly WHAT setting is causing the problem, but congrats on working out a solution

don't know if it helps, but i had this same problem after upgrading from 1.4.1 to 1.4.2b1, but strangely, after i deleted collection.db it worked all right. i did loose all my scores/ratings but hey, it worked