Bug 342442 - Mime type of remote folders is not recognized
Summary: Mime type of remote folders is not recognized
Status: RESOLVED FIXED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-03 14:08 UTC by Sean Chu
Modified: 2015-05-16 20:12 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Chu 2015-01-03 14:08:09 UTC
use the network folder with sftp, the sftp folders are not recognised. Folders are just shown as unknown icons with unknown type

Reproducible: Always

Steps to Reproduce:
1. create a nerwork folder sftp://...
2. the sub-directories are just shown as unknown icons with unknown type
Comment 1 Frank Reininghaus 2015-01-03 17:59:50 UTC
Thanks for the bug report. I can confirm this issue also with folders on ftp servers. It's also reproducible in the "Open File" dialog of, e.g., KWrite though, so it's not a Dolphin-specific issue.
Comment 2 Mark 2015-05-16 18:32:04 UTC
This should have been fixed a couple months ago if i remember correctly.
Can any of you that had this issue verify that is has indeed been fixed?
Comment 3 Sean Chu 2015-05-16 19:36:35 UTC
yes it is fixed, awesome!

On 16/05/15 19:32, Mark wrote:
> https://bugs.kde.org/show_bug.cgi?id=342442
>
> Mark <markg85@gmail.com> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |markg85@gmail.com
>
> --- Comment #2 from Mark <markg85@gmail.com> ---
> This should have been fixed a couple months ago if i remember correctly.
> Can any of you that had this issue verify that is has indeed been fixed?
>
Comment 4 Mark 2015-05-16 20:12:01 UTC
Great, marking it as fixed then.

I "think" this review fixed it: https://git.reviewboard.kde.org/r/121447/