Bug 134930

Summary:	Amarok won't start after downgrading version
Product:	[Applications] amarok	Reporter:	Marshalleq <atoms>
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Marshalleq 2006-09-30 23:58:46 UTC

Version:           1.4.3-15 (using KDE KDE 3.5.4)
Installed from:    SuSE RPMs
OS:                Linux

I'm running SLED 10 and I use the packman repositories with SMART.  Yesterday I found that amarok was having some faily major performance problems so I changed from SQLite to MYSQL as I have a large collection on an NFS share.  Unfortunately it did not resolve the issue though curiously enough if I right clicked on the visualisation window and left that window open it would all run fine until I clicked elsewhere.  Anyway, that is another bug, so I figured I'd downgrade it from 1.4.3-15 to 1.4.3-13 (as I believe the problem did not exist until I upgraded) but the few times I have downgraded it seems as though amarokapp decides to not run (all I get is a splash screen) and then it exits.  I've deleted the .kde/share/apps/amarok directory which I've found I've had to do when the SQLite database stuffs up in the past but it hasn't worked this time.  

Unless I have configured debug wrong (and this was my first time) all I am getting is a 'No Stack' which I've read elsewhere is completely unhelpful ;}

Incidentally I noticed that it is possible for me to have a different version of the libvisual package than that of amarok so it could have been the cause so I will test that, but I need amarok to actually go first ;}  And besides this is such an awesome app and I couldn't possibly live without it ;} !

Comment 1 Marshalleq 2006-10-01 00:07:21 UTC

OK, I've found the problem.  Firstly I had to delete not only the amarok directory mentioned above but also all files starting with amarok in /home/user/.kde/share/config.  Then I could see clearly that it's a database issue again.  I seem to always have to fix or delete the database when something goes wrong, could someone please explain why that is?  I would have thought the database tables would not have changed with such a small version difference as mentioned above and if I then put the versions back it would run again anyway, but perhaps I am wrong! ;}  So now I must again rescan my entire collection (takes about 1 hour) so you can see, this is not very nice for me!

Comment 2 Alexandre Oliveira 2006-10-01 00:10:38 UTC

We only released 1.4.3. "-13" and "-15" are probaly changes your distro has done.
Report this to your distro, as we have no idea about what they could have changed between these versions

Comment 3 Marshalleq 2006-10-01 02:10:57 UTC

Actually these are just from Packman (http://packman.links2linux.org/) and are taken straight from your cvs or equivalent.  Besides that, where they came from I believe has no relevance to my problem.  

The problem being that I have had a number of cases whereby my database needs to be fixed up, deleted etc.....  quite a number over the past year.   These problems have not been caused by version upgrades or downgrades and I'm not sure exacly what is causing them or I probably wouldn't need to log this ;}

I am suspicious it is related to having a large collection stored on a remote share, which used to be SMB but is now NFS because I believe it to be easier and better.  So pretty much I want to log the fact that I need to delete my database (be it MySQL or other) occasionally to get amarok working.  If someone wants to point out what to do to help resolve this I'm all ears ;}

Comment 4 Mark Kretschmann 2006-10-01 02:47:56 UTC

So yeah, if you're not sure of anything, that's a bad bug report. Sorry. Better use our forums and IRC.