Bug 1064521 - iso image identified as model/x.stl-binary or as plain text
Summary: iso image identified as model/x.stl-binary or as plain text
Status: CONFIRMED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: x86-64 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: openSUSE GNOME
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-21 11:23 UTC by David Kerkhof
Modified: 2017-10-21 17:35 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Kerkhof 2017-10-21 11:23:25 UTC 
I have various iso images of which some are correctly identified as application/x-cd-image, but others are identified as either model/x.stl-binary or as plain text file, making it difficult to open those iso images in a file manager.

Booting into Leap 42.3 all images are correctly identified as application/x-cd-image.

Would be nice to get this fixed
Comment 1 Fabian Vogt 2017-10-21 14:42:32 UTC 
What's the output of file *.iso on the "affected" images?
Comment 2 David Kerkhof 2017-10-21 15:45:26 UTC 
devuan_jessie_1.0.0_amd64_desktop-live.iso: DOS/MBR boot sector; partition 1 : ID=0x17, active, start-CHS (0x0,2,1), end-CHS (0x33b,63,32), startsector 64, 1695680 sectors
kali-linux-2016.2-amd64.iso:                DOS/MBR boot sector; partition 1 : ID=0x17, active, start-CHS (0x0,2,1), end-CHS (0x3fe,176,32), startsector 64, 5794208 sectors; partition 2 : ID=0x1, start-CHS (0x3ff,0,1), end-CHS (0x3ff,176,32), startsector 5794272, 215040 sectors
plopkexec.iso:                              DOS/MBR boot sector; partition 1 : ID=0x17, active, start-CHS (0x0,0,1), end-CHS (0x5,63,32), startsector 0, 12288 sectors
Porteus-KDE-v3.2.2-x86_64.iso:              ISO 9660 CD-ROM filesystem data 'Porteus' (bootable)
super_grub2_disk_hybrid_2.02s4.iso:         DOS/MBR boot sector; GRand Unified Bootloader, stage1 version 0x79, boot drive 0xbb, stage2 address 0x8e70, 1st sector stage2 0xb8db31c3, stage2 segment 0x201; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0xd,3,24), startsector 1, 26743 sectors, extended partition table (last)
systemrescuecd-x86-5.1.0.iso:               ISO 9660 CD-ROM filesystem data 'sysrcd-5.1.0' (bootable)
systemrescuecd-x86-5.1.1.iso:               ISO 9660 CD-ROM filesystem data 'sysrcd-5.1.1' (bootable)
trinity-rescue-kit.3.4-build-372.iso:       ISO 9660 CD-ROM filesystem data 'TRK_3.4' (bootable)

devuan, kali and plop are identified as plain text
super_grub2_disk_hybrid_2.02s4.iso as iso image
and the rest as model/x.stl-binary
Comment 3 Fabian Vogt 2017-10-21 17:35:52 UTC 
Same as https://bugs.freedesktop.org/show_bug.cgi?id=80877 as xdg-mime query filetype *.iso does the same.

As a workaround, edit /usr/share/mime/packages/freedesktop.org.xml and change
    <glob weight="80" pattern="*.iso"/>
    <glob pattern="*.iso9660"/>

below <mime-type type="application/x-cd-image"> to

    <glob weight="60" pattern="*.iso"/>
    <glob pattern="*.iso9660"/>

Reassigning to the maintainers of shared-mime-info.