![]() Registered Member ![]()
|
Amarok is by far and away the best and easiest to use music player for any system. But now I find myself frustrated - it seems it has shot itself in the foot. After the recent update (to 1.4.6 I believe?) It appeared to run, until I added a new album. It then shut itself down, and refused to reopen.
So far I have tried everything I can think of - I first removed the config files - no success. Then a reinstall of Amarok through Adept. No success. A complete purge of Amarok through Adept then a manual reinstall from the latest binary? No success. There aren't even any old binaries out there that I can find. What gives? Restore my faith in this program, somebody... |
![]() Moderator ![]()
|
have you checked that there's not a stray amarokapp process running? Try 'killall -9 amarokapp' to make sure.
Does the splash screen display?
"There are two theories to arguing with women. Neither one works."
. If men could get pregnant, we'd learn the true meaning of "screaming nancyboy wuss" |
![]() Registered Member ![]()
|
I did not consider the stray process running - a nice angle, and I would have loved it if it worked, but sadly no... Yes, the splash screen does display - and now oddly it can only be undisplayed by killing amarok. Still doesn't run, just to clear up.
|
![]() Registered Member ![]()
|
I have exactly the same problem. I searched through the bug reports and saw at least two dozens of them. Unfortunately, I couldn't find a solution except for upgrading to the latest version. I do have the latest version!!!
![]() |
![]() Registered Member ![]()
|
Hello,
I also have that problem. On my machine I can get amarok running when I start it as root. Well, this is not a final solution but some sort of workaround. Good luck Hiaso |
![]() KDE Developer ![]()
|
It often helps to nuke your Amarok config and data folder. Beware, this will wipe your statistics, ratings, etc. So you might want to back up before nuking.
If that doesn't help, there is probably something wrong with your package or dependencies. Try to start amarok from the shell with "amarokapp" and see if there is any interesting output. One more tip: Never try to downgrade Amarok. Downgrading is not supported and might corrupt your collection, or Amarok might refuse to start. If your collection is corrupted then nuking helps, like described above.
Last edited by Anonymous on Sun Jul 08, 2007 8:08 am, edited 1 time in total.
--
Mark Kretschmann - Amarok Developer |
![]() Registered Member ![]()
|
Thank you Mark,
these two commands brought my amarok back to live ![]() Bye Hiaso |
![]() Registered Member ![]()
|
yes, deleting my database really helped. I saw that there are many similar reports on the bug tracking system for different version. Therefore, I think you should do something to improve the updates.
|
![]() Registered Member ![]()
|
It worked, so thank you. Still - there may well be people out there who will suffer the same issue. Fix it soon!
Thanks again. *edit* - I have booted amarok for the first time after trying the "amarokapp" through terminal approach. It still doesn't work. Is there a way to run the program without having a terminal open? It's very annoying, as it eats toolbar real estate. **edit again** - Fixed after reboot. *phew*
Last edited by alexwadham on Mon Jul 09, 2007 8:17 pm, edited 1 time in total.
|
Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot]