Nautilus pays attention to file extensions??

[Sam Bull]

From the switch from Gutsy to Hardy, Nautilus seems to have become dumb (not my terminology :P). I created a normal text file in Gutsy and named it 'Backup.bak', now in Hardy, Nautilus says it doesn't recognize what application to open it with, and I have to right click 'Open with Other Application' and select Text Editor, so it seems to have become dumb between Gutsy and Hardy.

[Pedro Villavicencio (pedro)]

Thanks for your report, can you attach the output of : file Backup.bak and the output of gvfs-info Backup.bak to the report? thanks in advance.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[Sam Bull (dreamsorcerer)]

Sorry about that, didn't see the first comment there,

$ file '/media/disk/home/s/Backup.bak'
/media/disk/home/s/Backup.bak: ASCII text

$ gvfs-info '/media/disk/home/s/Backup.bak'
display name: Backup.bak
edit name: Backup.bak
name: Backup.bak
type: regular
size: 1870
attributes:
  standard::name: Backup.bak
  standard::type: 1
  standard::size: 1870
  standard::display-name: Backup.bak
  standard::edit-name: Backup.bak
  standard::copy-name: Backup.bak
  standard::content-type: application/x-trash
  standard::icon: GThemedIcon:0x8056980
  standard::fast-content-type: application/x-trash
  unix::device: 2049
  unix::inode: 205084
  unix::mode: 33216
  unix::nlink: 1
  unix::uid: 1000
  unix::gid: 1000
  unix::rdev: 0
  unix::block-size: 4096
  unix::blocks: 8
  time::modified: 1209575146
  time::modified-usec: 0
  time::access: 1210504867
  time::access-usec: 0
  time::changed: 1209575146
  time::changed-usec: 0
  etag::value: 1209575146:0
  id::file: l2049:205084
  id::filesystem: l2049
  owner::user: s
  owner::user-real: Sam Bull
  owner::group: s
  access::can-read: TRUE
  access::can-write: TRUE
  access::can-execute: TRUE
  access::can-rename: TRUE
  access::can-delete: TRUE
  access::can-trash: FALSE

[Sam Bull (dreamsorcerer)]

Added requested infromation

[Sam Bull (dreamsorcerer)]

It's done it again when I backup up my xorg.conf file, renaming it to xorg.conf.old, it suddenly doesn't recognise it, it has a different icon this time though, maybe because it's on the local partition, or maybe because it uses a different extension.

[Sebastien Bacher (seb128)]

your example is not a nautilus bug, the mimetype is a special one and not claimed by any application, you should rename it differently

[Sam Bull (dreamsorcerer)]

But, that's the point, I shouldn't have to rename it, nautilus should recognize it as a regular text file, I had none of these problems on Gutsy, so if it's not a bug, then why does it work on versions before Hardy? Since when did the xorg.conf file become unrecognizable just because I added '.old' to it?

[Sebastien Bacher (seb128)]

the shared-mime-info define those as a special mimetype and no application is claiming to handle this one, I agree that's not optimal but nautilus has nothing to do in the issue