amarok scans home directory without asking - even if told not to

Bug #1029457 reported by Alan Jenkins
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Amarok
Invalid
Medium
amarok (Ubuntu)
Undecided
Unassigned

Bug Description

On first startup, Amarok scans the entire home directory without asking whether this makes sense. For example, if your home directory contains source code, or a large photo collection, this probably isn't what you want. You probably want it to scan your music folder instead.

I tried to unselect the home directory in the preferences, but without selecting any alternative collection folder. Amarok's response (on hitting "Apply") was to start scanning the home directory, without even updating the treeview to show that it had re-selected the home folder.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: amarok 2:2.5.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Thu Jul 26 14:30:50 2012
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: amarok
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Alan Jenkins (aj504) wrote :
Revision history for this message
Alex Vadkovskiy (pofigoon) wrote :

I can confirm this bug.
Even if the ~/Music folder is unchecked all the media files are still in my library. No matter if I have another folder selected as library or not.
I tried 'Full library rescan" few times and it didn't work.

I have amd64 Kubuntu 12.04 with backports repository attached.
Amarok Version 2.7.0
Using KDE 4.10.2

Revision history for this message
Myriam Schweingruber (myriam) wrote :

I can't reproduce this at all. You might want to erase your $HOME/.kde/share/config/amarokrc file, so it will ask you again to specify the correct folder on the next Amarok start.

Revision history for this message
Alex Vadkovskiy (pofigoon) wrote :

I tried to remove all 3 amarok-related files from configs folder (amarok-appletsrc , amarokrc and amarok-homerc).
After the files are removed. Amarok is still not asking for another folder - it just updates the existing library and the files I removed are created back.
 The weird thing is that now it seems like the library folder is reset again to ~/Music, but all the media files that were added from the other folder (/media/Music) are still avaliable in the lib.
It look like Amarok is only adding files to the library but never removes them

Revision history for this message
Myriam Schweingruber (myriam) wrote :

I currently have no bug upstream reporting this, could you please report this at https://bugs.kde.org/enter_bug.cgi?product=amarok for the component Collections/Local, so we can track this where it belongs, as the Amarok developers don't use Launchpad as a bug tracker.

Revision history for this message
In , Alex Vadkovskiy (pofigoon) wrote :

It seems like Amarok is only able to add files to Collection and never removes them if the source folder is not selected in Local Collection settings anymore. Even after 'Full rescan'

When Amarok was first started it used $HOME/Music folder as Local Collection. But my collection is stored in /media/Music so I unchecked $HOME/Music and checked /media/Music in Settings->Local_Collection. After using 'Full rescan' option I noticed that all the media files from my $HOME folder are still in collection.
I tried to remove amarokrc file in $HOME/.kde/share/config/ and the library folder was switched to my $HOME/Music again, but this time all the files from /media/Music are still stayed in my collection.

I believe it is possible to cleanup the library using the advice from this ticket https://bugs.kde.org/show_bug.cgi?id=191073 - by removing Amarok's database, but anway I think the current behavior of Local Collection is not quite good :)

Revision history for this message
Alex Vadkovskiy (pofigoon) wrote :

Thanks for help.
I reported a bug there https://bugs.kde.org/show_bug.cgi?id=318602

Revision history for this message
In , Myriam Schweingruber (myriam) wrote :

As mentioned on the Launchpad report: I can't reproduce this here, using Amarok from git v2.7.0-234-g541a484 on KDE 4.10.2, Kubuntu 13.04 beta2

Revision history for this message
In , Alex Vadkovskiy (pofigoon) wrote :

Forgot to mention...
I am using Kubuntu 12.04 64bit + kubuntu-backports

Revision history for this message
In , Matěj Laitl (f-matej) wrote :

I think this is a duplicate of bug 316216. Can you please follow the discussion between me and Rudolf there and report whether you have the same behaviour on the bug 316216?

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

Revision history for this message
In , Alex Vadkovskiy (pofigoon) wrote :

I think Rudolf's bug actually consists of two:
 1) root folder is being added to local collection after CD rip is crashed;
 2) unable to remove junk files (even if the collection folder is changed in settings) unless .kde/share/apps/amarok/mysqle is removed (the problem I do have)

Changed in amarok:
importance: Unknown → Medium
status: Unknown → Invalid
Revision history for this message
In , Matěj Laitl (f-matej) wrote :

(In reply to comment #4)
> I think Rudolf's bug actually consists of two:
> 1) root folder is being added to local collection after CD rip is crashed;
> 2) unable to remove junk files (even if the collection folder is changed in
> settings) unless .kde/share/apps/amarok/mysqle is removed (the problem I do
> have)

No need to analyse Rudolf's problem, just please do what instructed to do, on bug 316216. (not here)

Revision history for this message
Rohan Garg (rohangarg) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at: https://bugs.kde.org/show_bug.cgi?id=318602. Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.

Thanks!

Changed in amarok (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.