Bug 317691

Summary: local collection empty and stays empty after rescan
Product: [Applications] amarok Reporter: Ulf Dellbrügge <ulf.dellbruegge>
Component: Collections/LocalAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED DUPLICATE    
Severity: major CC: matej, ralf-engels
Priority: NOR Keywords: investigated
Version: 2.7.0   
Target Milestone: 2.8   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ulf Dellbrügge 2013-04-01 18:31:49 UTC 
I opened amarok a few days ago and my local collection was empty. I went into the settings and checked, if amarol lost the path for the data files and clicked on full rescan. Nothing happens, i click okay and it would not check for new files like it does normally if i try to scan my music for the first time.

Reproducible: Always

Steps to Reproduce:
1. Open Amarok
1. Rescan Collection

1. Deinstall Amarok
2. Install Amarok (and open it)
3. Scan for Collection

1. Deinstall Amarok
2. Delete .kde4/share/apps/amarok
3. Install Amarok (and open it)
4 Rescan Collection
Actual Results:  
Always the same: empty collection

Expected Results:  
show my music 

I remember to have more informations in dolphin. There were some items like Documents, Music, Videos, which are no more.
I went into system settings and typed in my typical paths to Documents, Music and Videos. That might all be related.
Comment 1 Ulf Dellbrügge 2013-04-01 18:35:55 UTC 
This may also be related to the switch to MariaDB as i found in that other bug report 
317633 (https://bugs.kde.org/show_bug.cgi?id=317633)
which is marked as a duplicate of 
317370 (https://bugs.kde.org/show_bug.cgi?id=317370)

Sorry for bug-spamming, if that is the case. I will check on that asap.
Comment 2 Ulf Dellbrügge 2013-04-01 18:44:33 UTC 
Yes. This can be closed. I installed mariadb and followed the procedure as announced on archlinux.org. I restarted amarok and did a rescan. It is scanning now, which it did not before using mariadb.
Comment 3 Ulf Dellbrügge 2013-04-01 18:46:14 UTC 

*** This bug has been marked as a duplicate of bug 317370 ***