amarok cannot play files that containt '#' (hash) in the path

Bug #437968 reported by Stilor
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
New
Undecided
Unassigned
Nominated for Karmic by Peter M

Bug Description

Binary package hint: amarok

Amarok cannot play files if they contain '#' (hash) in the path name. How to reproduce:

1. Create a directory. Put a sample 1.mp3 file into the directory.
2. Check that the file can be played by Amarok.
3. Rename "1.mp3" to "1#1.mp3"
4. Try to play the file in Amarok. File is loaded, tags are displayed correctly, but the file cannot be played.

The problem looks similar to bug #317526. However, the response in bug #317526 was that the problem is likely to be caused by GStreamer backend; I am not using GStreamer, I am using Xine backend.

ProblemType: Bug
Architecture: i386
Date: Sun Sep 27 22:41:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/amarok
NonfreeKernelModules: nvidia
Package: amarok 2:2.1.90-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: amarok
Uname: Linux 2.6.31-11-generic i686

Revision history for this message
Stilor (stilor) wrote :
Revision history for this message
Sean (mrnowls) wrote :

I'm having the same problem, except with .m4a files. A file that included the "#" (pound sign) in its filename wouldn't play, though its tags displayed correctly. Acting on a hunch, I removed the "#" symbol and the file played correctly.

This behavior didn't happen for me with Kubuntu 9.04 using Amarok 2.2.1.

PackageArchitecture: amd64
Date: Mon Nov 2 15:02:46 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/amarok
NonfreeKernelModules: nvidia
Package: amarok 2:2.2.0-0ubuntu2
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: amarok
Uname: Linux 2.6.31-11-generic i686

Revision history for this message
Sean (mrnowls) wrote :

Sorry, the Uname line in the comment above should read:

Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
Peter M (peter-bolkhuis) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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