Arch Linux

I have the same bug. Same versions, archlinux also up to same date.

I am using arch's internal database.

I used to lose the local collection all the time in previous versions. All that was needed was to reassign the path for the collection, and things would reappear. Now, OK and Apply don't work. My Local Collection is gone. A playlist from my last run remains and continues to work (but the album covers are gone).

The amarok database of playlists is gone. My playlist files on disk remains. Any m3u playlists created with recent versions of amarok (sometime in the last two months) are empty. Old playlists are still there. I only have 9 m3u playlists and had 7 until recent months.

When I downgrade to amarok 2.7.0-3 everything magically reappears (except my two m3u files are still empty). No intervention necessary. My collection directory has a check mark beside it again.

In general, my impression of amarok's internal database over the last 6 months is it has started to go wonky on me, but until now I just rescanned or rechose my collection directory, and it seemed to work.

I have the same bug. Same versions, archlinux also up to same date.

I am using arch's internal database.

I used to lose the local collection all the time in previous versions. All that was needed was to reassign the path for the collection, and things would reappear. Now, OK and Apply don't work. My Local Collection is gone. A playlist from my last run remains and continues to work (but the album covers are gone).

The amarok database of playlists is gone. My playlist files on disk remains. Any m3u playlists created with recent versions of amarok (sometime in the last two months) are empty. Old playlists are still there. I only have 9 m3u playlists and had 7 until recent months.

When I downgrade to amarok 2.7.0-3 everything magically reappears (except my two m3u files are still empty). No intervention necessary. My collection directory has a check mark beside it again.

In general, my impression of amarok's internal database over the last 6 months is it has started to go wonky on me, but until now I just rescanned or rechose my collection directory, and it seemed to work.

Installing (or reintalling, I don't remember) mariadb helped for me.

I had mariadb installed, as per arch news. But I did that after I installed amarok manually. So, I just went back to reinstall amarok, and no luck. Immediately downgrading again solved the problem, no need to play with any settings.

Again, I am using amarok's internal database.

I missed the news about mariadb, I installed it and amarok is working again now. Thanks all, this bug can be closed !

Well, I still have it, and am not interested in running a database of any kind just for amarok (if that will even fix it in my case).

@ David Bourgeois

I use the SQLite database and I had this issue.
Switching to Mariadb had fixed it.
Did you follow the procedure ?
https://www.archlinux.org/news/mariadb-replaces-mysql-in-repositories/

No, I never bothered with that, because I don't run mysql and it is disabled in my systemd. But, I did install the two libraries now, along with mariadb, and that solved the problem for me!

libmariadbclient mariadb-clients

So, I guess the bug can be closed.



(I wonder if I get to turn the mini browser back on, that used to cause crashes.)

I can confirm this bug and that installing mariadb, libmariadbclient, and mariadb-clients fixes it. This is a package dependency problem specific to Arch Linux. See https://bugs.kde.org/show_bug.cgi?id=317370