| Summary: | Incorrect handling of file types in remote file systems | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] kio-extras | Reporter: | Dotan Cohen <kde-2011.08> |
| Component: | FISH | Assignee: | Jörg Walter <trouble> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | faure, oriol |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Dotan Cohen
2008-12-04 23:56:58 UTC
Then kio_fish is not reporting the right mimetype... I'm not sure if, after all this time, the problem is the same, but at least now the issue is definitely not just for the fish protocol. Both in Dolphin and Konqueror the mimetype of all files is properly recognized when they are local. But all remote files (and I have tried with more than one remote host) are not. A bug reported to ownCloud (http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-668) claims that the problem is an extra ';' (semicolon) that is appended to the mimetype by the 'file' command when used to identify the mimetype. The solution suggested there is simply to make ownCloud remove the semicolon. When I do that, then Dolphin and Konqueror are able to correctly identify the mimetype of all files and everything is fine. But, of course, this only helps when I am accessing my ownCloud files through ownCloud's webdav, and all the other files I access in the server continue to have their mimetypes unrecognized. Does KDE not use the 'file' command for local files but it does for remote ones? Or does it find a way to fix the issue for local files but not for remote ones? I really don't know enough about programming to be able to diagnose this properly and know where to report a separate bug, but I find this behavior extremely annoying so any guidance on how to move on to try to get this fixed would be much appreciated. |