Bug 163749

Summary:	Amarok is hard coded to scan for collection from root directory
Product:	[Applications] amarok	Reporter:	Murray Trainer <mtrainer>
Component:	general	Assignee:	Amarok Bugs <amarok-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version First Reported In:	1.4.7
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Murray Trainer 2008-06-11 05:13:51 UTC

Version:           1.4.7 (using 3.5.8, Kubuntu (gutsy) 4:3.5.8-0ubuntu3.4)
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.22-14-xen

I am trying to configure amarok to run under a secure NFS home directory.  I get an error "Access denied to file:///." as amarok appears to try and scan from "/" downwards to create a new collection which is not permitted in our environment.  There doesn't appear to be any easy way of fixing this issue.  We are using KDE Kiosk Tool restrictions where KDE apps are not allowed to browse outside their home directory.  Amarok's behaviour in trying to access '/' directly conflicts with the KDE kiosk browsing restriction.  A preference to change the default top directory for collection scanning to $HOME or similar instead of / would solve the problem.

Thanks

Murray

Comment 1 Seb Ruiz 2008-06-11 05:31:05 UTC

We don't hard code anything with the scanning. Change the scan directory in the Collection options. Also, please upgrade to Amarok 1.4.9.1

Comment 2 Murray Trainer 2008-06-11 08:43:03 UTC

Install KDE kiosk tool and check the option under Konqueror - "Disable File Browsing outside Home directory".  You will then get the "Access Denied" error.  Amarok tries to read "/" even if I pre-configure the collection folder as their home directory.  The issue is that Amarok assumes access to "/" wherever the collection is specified.

Comment 3 Matt Rogers 2009-08-03 04:09:21 UTC

Thank you for taking the time to report this bug for Amarok. Amarok 1.4 is now unmaintained and will no longer see any improvements. Because of this, and the massive amount of changes Amarok has undergone throughout the 2.x series of releases, we are closing bugs that no longer apply to the 2.x series due to changes in functionality, the underlying architecture, or a conflict for the vision of Amarok 2.

We appreciate the time you took to provide feedback about Amarok 1.4 and will look forward to any feedback you may provided about Amarok 2. Thanks.