Bug 165323 - file -i returns wrong mimetype for mpeg1 video
Summary: file -i returns wrong mimetype for mpeg1 video
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: file
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Radek Vokál
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-08-07 21:56 UTC by Sergey Bostandzhyan
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: 4.14-4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-08-09 12:46:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sergey Bostandzhyan 2005-08-07 21:56:03 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc3 Firefox/1.0.6

Description of problem:
I have various mpeg1 video files; on FC3 (file-4.12-1.FC3.1) the file -i command returned the video/mpeg mimetype for those files, that was correct.

On FC4 file -i returns "FFF6    0xFFF0          audio/X-HX-AAC-ADTS" which is not correct. 

The problem appeared with a number of files, not only with one.
Use this video if you can not reproduce it with your data:
http://www.deadlock.dhs.org/~jin/blender/heusl.mpg

Version-Release number of selected component (if applicable):
file-4.13-4

How reproducible:
Always

Steps to Reproduce:
1. get an mpeg 1 video file, assuming "yourfile.mpg"
2. enter "file -i yourfile.mpg" in terminal and look at the output


Actual Results:  mimetype information was: "FFF6    0xFFF0          audio/X-HX-AAC-ADTS"


Expected Results:  mimetype information should be "video/mpeg"

Additional info:

Comment 1 Sergey Bostandzhyan 2005-08-07 22:03:16 UTC
The problem seems to be related to the magic.mime file that has changed from FC3
to FC4. 

Using the magic.mime file from FC3 with the -m option on a FC4 system produces
correct output. (something like: file -i myfile.mpg -m /tmp/fc3_magic.mime)

Comment 2 Radek Vokál 2005-08-09 12:46:00 UTC
Fixed, there was a typo in AAC files recognition. 


Note You need to log in before you can comment on or make changes to this bug.