After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 329688 - Won't let me open an MP3 file
Won't let me open an MP3 file
Status: RESOLVED DUPLICATE of bug 138033
Product: nautilus
Classification: Core
Component: general
2.12.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-03 00:08 UTC by Sam Morris
Modified: 2006-02-03 09:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Sam Morris 2006-02-03 00:08:40 UTC 
Please describe the problem:
When trying to open an MP3 file, Nautilus gives me the following error:

'The filename "Executive Mix 1.mp3" indicates that this file is of type "MP3
audio". The contents of the file indicate that the file is of type "WAV audio".
If you open this file, the file might present a security risk to your system.

Do not open the file unless you created the file yourself, or received the file
from a trusted source. To open the file, rename the file to the correct
extension for "WAV audio", then open the file normally. Alternatively, use the
Open With menu to choose a specific application for the file.'

file(1) says:

'Executive Mix 1.mp3: RIFF (little-endian) data, WAVE audio, MPEG Layer 3,
stereo 22050 Hz'

Having to rename it to .wav is annoying since I have Totem associated with
audio/x-wav. I guess this is really a bug with Nautilus' MIME type detection.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Fabio Bonelli 2006-02-03 09:57:01 UTC 
Thanks for the bug report!

This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

There are useful links to the root of the problem in bug 138033 's comments.

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