the reason it behaves differently on local and non-local locations is
that it's using the file content on local drives to know what to use but
it would be expensive to load the file in other cases
** Also affects: nautilus
Importance: Undecided
Status: New
** Summary changed:
- Nautilus reports "could not display..." empty file
+ non local files opening relies on filename
** Summary changed:
- non local files opening relies on filename
+ opening of non local files relies on filename to be correct
--
opening of non local files relies on filename to be correct
https://bugs.launchpad.net/bugs/435780
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs