The current trigger for x-content/image-picturecd is too general - having a non empty folder named PICTURES. There is no device type check, so internal disks, portable usb devices etc are all labelled incongruously as begin a picture cd (eg by nautilus). See downstream bug - https://bugs.launchpad.net/nautilus/+bug/258936.
Especially on case-insensitive filesystems, its not uncommon to have a directory named Pictures, and this still triggers the match.
The current trigger for x-content/ image-picturecd is too general - having a non empty folder named PICTURES. There is no device type check, so internal disks, portable usb devices etc are all labelled incongruously as begin a picture cd (eg by nautilus). See downstream bug - https:/ /bugs.launchpad .net/nautilus/ +bug/258936.
Especially on case-insensitive filesystems, its not uncommon to have a directory named Pictures, and this still triggers the match.
The offending line in the mime files:
$ grep -A 39 x-content/ image-picturecd /usr/share/ mime/packages/ freedesktop. org.xml | grep -v xml:lang content/ image-picturecd "> Picture CD</comment>
<mime-type type="x-
<comment>
<treemagic>
<treematch type="directory" path="PICTURES" non-empty="true" match-case="true"/>
</treemagic>
</mime-type>
Ideally this should be enhanced to also include a device type check, or alternatively just removed.
See resulting effect on gvfs ([drive-hardisk] considered a x-content/ image-picturecd ):
$ gvfs-mount -li | grep -A 15 'Volume(1)' nitorGdu) 3edc-4dd5- b0d8-7134845d31 d1' harddisk- ata] [drive-harddisk] [drive] automount= 0 nitorGdu) location= file:// /media/ Files harddisk- ata] [drive-harddisk] [drive] content_ types: x-content/ image-picturecd
Volume(1): Files
Type: GProxyVolume (GProxyVolumeMo
ids:
uuid: '62b4128d-
unix-device: '/dev/sda6'
label: 'Files'
themed icons: [drive-
can_mount=1
can_eject=0
should_
Mount(0): Files -> file:///media/Files
Type: GProxyMount (GProxyVolumeMo
default_
themed icons: [drive-
x_
can_unmount=1