Using 1.3 official, Guru\'s SUSE RPMs (including all engine/visual RPMs).


I noticed a couple things on a fresh install (backed up my old db and all amaroK-related .kde hidden files):


1) In the initial Wizard, I selected \"MySQL\" as the database, including correct user/pass for it. I didn\'t mark any directories to scan at this point.

However, once the Wizard was done and I popped open \"Configure\", it was showing me \"SQLite\" was selected.

I switched it to MySQL and saw the user/pass were there from the Wizard though.

2) I marked my music collection dirs, and had it set for MySQL. I noticed that the Apply button never woke up when I changed the collection dirs, or when I changed the db.

I figured clicking OK would accept these, though.

So I did that, and then \"Rescan collection\". The dirs were fine.

However, it still saved everything in an SQLite db.


3) I\'m thinking that #2 may be an \"Apply\" issue because after noting this, I went back into the Configure panel and switched it again to MySQL. But this time I turned off OSD.That caused the Apply button to appear. As soon as I clicked that, I saw my collection disappear.

I could then rebuild using MySQL.



I guess I\'m saying there\'s some kinda Saving issue here when it comes to database options, in the Wizard, and on manual Configure change.

Post edited by: HairMetalAddict, at: 2005/08/16 12:06

Yea, I can confirm this is a problem. I\'ll look into it.

Thanks,
ian