This bug was first reported against tracker and then glib but it turned out to be a shared-mime-info bug in the end so filing it here. Please read the details at: http://bugzilla.gnome.org/show_bug.cgi?id=531239
Which version of shared-mime-info? Please include all the details about the bug here.
> Which version of shared-mime-info? 0.22 > Please include all the details about the bug here. You mean you need further details then given on the related gnome bug or you want all details to be copy&pasted here?
audio/x-vorbis+ogg is a descendant of application/ogg, so fix your application to check for parent types as well.
(In reply to comment #3) > audio/x-vorbis+ogg is a descendant of application/ogg, so fix your application > to check for parent types as well. > I filed this bug with respect to my UPnP MediaServer, so it doesn't really need any fixing but seems like many control points out there (including mine) do need to do more than simple string comparison on mimetypes. Correcting my controlpoint is doable of course but for supporting many other controlpoints out there, I'll have to replace "audio/x-vorbis+ogg" with "application/ogg" in the DIDLLite produced by my MediaServer.
Whatever piece of code is asking tracker the mime-type should check probably check for the parent mime-type, and see if it's a known one. There's probably other cases where this would happen, as with quicktime/mpeg-4 sub-types.
(In reply to comment #5) > Whatever piece of code is asking tracker the mime-type That is the UPnP server. It doesn't really do anything with the mime-type itself except for reporting it amongst other meta-data for each media item it export on the UPnP network. > should check probably > check for the parent mime-type, and see if it's a known one. And report the parent-type instead if that is so? > There's probably other cases where this would happen, as with quicktime/mpeg-4 > sub-types. > True.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.