Bug 504789

Summary: Database updater from 3.2.2 to 3.2.81 (version 15 -> 16) results in no Collection nor Metadata
Product: [Applications] amarok Reporter: dkriz
Component: Collection BrowserAssignee: Amarok Bugs <amarok-bugs-null>
Status: REPORTED ---    
Severity: normal CC: tuomas
Priority: NOR    
Version First Reported In: 3.2.81   
Target Milestone: kf5   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: debug log

Description dkriz 2025-05-25 23:44:00 UTC
Created attachment 181748 [details]
debug log

SUMMARY

Database updater from 3.2.2 to 3.2.81 (version 15 -> 16) results in no Collection nor Metadata

I use an external MySQL DB for amarok. When I upgrade Amarok from 3.2.2 to 3.2.81, opening the application results in the Database Updater detecting an old version of the DB, and attempts to update it.

Amarok then has no songs in my Local Collection, and all Metadata for my collection is no longer detected by Amarok

STEPS TO REPRODUCE
1. Restore backup of amarokdb `mysql -u root amarokdb < amarokdb-2025-05-25.sql`
2. Open Amarok 3.2.81
3. Updater runs and above results are detected.

Note that restoring the DB and opening Amarok 3.2.2 results in my collection being detected, and the metadata being displayed.

Attached is an amarok debug output of the database updater doing this.

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 dkriz 2025-05-25 23:46:08 UTC
Operating System: Arch Linux 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.7-arch2-1 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070
Comment 2 Tuomas Nurmi 2025-05-26 05:28:28 UTC
Thank you for the report!
I don't see any obvious errors or explanations in the debug log at first glance, but I'll try to inspect more later and see if I can find any crucial difference between my own external db migrations and your logs.
Comment 3 dkriz 2025-05-26 18:31:04 UTC
If you want I can send you my MySQL db dump?
Comment 4 dkriz 2025-05-26 18:31:53 UTC
My library is quite large, ~43000 songs
Comment 5 Tuomas Nurmi 2025-05-27 18:54:29 UTC
Sure, that could be helpful, please do. You can email it to me directly (or, if it's very large, upload & send link). Thanks!
Comment 6 Tuomas Nurmi 2025-06-09 16:08:24 UTC
I'll also document here that I've been unable to reproduce this myself, even after I tried setting up a database provided by the reporter. All tracks in the database reside on network shares (some of them with duplicate entries in Amarok's device database); that might have some kind of role.
Comment 7 dkriz 2025-06-14 16:40:27 UTC
Update:

I've rebuilt amarok 3.2.81.
Database updater ran as before, leaving me with 0 songs in my collection.
Performed a full rescan of my library, which left no metadata & ratings.
Exiting and reopening Amarok caused the metadata to be present this time.

So there is a workaround in this case.
Comment 8 Tuomas Nurmi 2025-06-20 11:13:43 UTC
Ok, thank you for the status update. Can you verify if the previous statistics are still there for the now-found tracks, or if they are 'new' tracks with no playcount, first played & last played stats?