Bug 1301133 - Incorrect mime type detection for file
Incorrect mime type detection for file
Product: Fedora
Classification: Fedora
Component: glib2 (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-01-22 12:10 EST by Jonathan Underwood
Modified: 2016-12-20 13:05 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 13:05:03 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Example mime type definition (398 bytes, application/xml)
2016-01-22 12:10 EST, Jonathan Underwood
no flags Details

  None (edit)
Description Jonathan Underwood 2016-01-22 12:10:55 EST
Created attachment 1117307 [details]
Example mime type definition

Description of problem:

1. Install the attached mime type xml file under /usr/share/mime/packages

2. Change the mathematica section of /usr/share/mime/packages/freedesktop.org.xml to have a lower weight and priority ie.:

<glob weight="30" pattern="*.nb"/>


<magic priority="30">

3. Run update-mime-database /usr/share/mime

4. At this point, the definition in application-vnd.wolfram.nb.xml should be having priority over the one in freedesktop.org.xml for files with the extension .nb, and so the mimetype should be detected as application/vnd.wolfram.nb rather than application/mathematica

5. However:

$ xdg-mime query filetype junk.nb 

$ gvfs-info junk.nb
display name: junk.nb
edit name: junk.nb
name: junk.nb
type: regular
size:  4
uri: file:///home/jgu/tmp/junk.nb
  standard::type: 1
  standard::name: junk.nb
  standard::display-name: junk.nb
  standard::edit-name: junk.nb
  standard::copy-name: junk.nb
  standard::icon: application-mathematica, x-office-document
  standard::content-type: application/mathematica
  standard::fast-content-type: application/vnd.wolfram.nb

$ mimetype junk.nb
junk.nb: application/vnd.wolfram.nb

$ kmimetypefinder junk.nb
(accuracy 100)

So, gvfs is getting it wrong. mimetype and kmimetypefinder are getting it right.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 1 Jonathan Underwood 2016-01-22 12:12:03 EST
Meant to mention, this is with gvfs-1.26.2-1.fc23.x86_64
Comment 2 Jonathan Underwood 2016-01-22 14:27:25 EST
Reassigning to glib, as I think this must be a bug in the weight handling in xdgmimecache.c
Comment 3 Fedora End Of Life 2016-11-24 10:07:14 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2016-12-20 13:05:03 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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