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 711716 - Arcane mime-type instead of human readable description
Arcane mime-type instead of human readable description
Status: RESOLVED OBSOLETE
Product: gnome-boxes
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-11-09 02:49 UTC by Bastien Nocera
Modified: 2018-01-11 10:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screenshot (56.18 KB, image/png)
2013-11-09 02:49 UTC, Bastien Nocera
Details

Description Bastien Nocera 2013-11-09 02:49:28 UTC
Created attachment 259308 [details]
screenshot

As gnome-boxes is the one "benefiting" from this. The bar here says "Detected as x-content/bootable-media-type".

x-content/bootable-media-type isn't a registered mime-type. So either file a bug against shared-mime-info with a git formatted patch (following its HACKING file, including a test tree), or install your own translated mime-type file which will give a real name to this mime-type.
Comment 1 Zeeshan Ali 2013-11-09 18:36:54 UTC
(In reply to comment #0)
> Created an attachment (id=259308) [details]
> screenshot
> 
> As gnome-boxes is the one "benefiting" from this. The bar here says "Detected
> as x-content/bootable-media-type".
> 
> x-content/bootable-media-type isn't a registered mime-type. So either file a
> bug against shared-mime-info with a git formatted patch (following its HACKING
> file, including a test tree),

Well I was going to do that 2 years ago when I came-up with this mime-type but IIRC you said you only want it in shared-mime-info if detection can be done using first few Ks of the files and that is not possible.

> or install your own translated mime-type file
> which will give a real name to this mime-type.

Unless I misunderstood you then, I guess we'll have to do this but the file will need to come from libosinfo.
Comment 2 Bastien Nocera 2013-11-12 07:54:46 UTC
(In reply to comment #1)
> (In reply to comment #0)
> > Created an attachment (id=259308) [details] [details]
> > screenshot
> > 
> > As gnome-boxes is the one "benefiting" from this. The bar here says "Detected
> > as x-content/bootable-media-type".
> > 
> > x-content/bootable-media-type isn't a registered mime-type. So either file a
> > bug against shared-mime-info with a git formatted patch (following its HACKING
> > file, including a test tree),
> 
> Well I was going to do that 2 years ago when I came-up with this mime-type but
> IIRC you said you only want it in shared-mime-info if detection can be done
> using first few Ks of the files and that is not possible.

It's obviously guessing the mime-type already, somehow. The problem is that you don't have a description for the mime-type. That has nothing to do with that (undefined) mime-type having magic or not.

> > or install your own translated mime-type file
> > which will give a real name to this mime-type.
> 
> Unless I misunderstood you then, I guess we'll have to do this but the file
> will need to come from libosinfo.

It still needs a mime-type definition to have a nice and translated name in the UI. It shouldn't have magic that requires huge amounts of data.
Comment 3 GNOME Infrastructure Team 2018-01-11 10:07:02 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-boxes/issues/20.