Bug 356830 - Invalid location in location bar (button mode) when browsing FTP
Summary: Invalid location in location bar (button mode) when browsing FTP
Status: RESOLVED FIXED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-17 12:59 UTC by Max
Modified: 2015-12-23 16:22 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.18
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Max 2015-12-17 12:59:58 UTC
When I descend into directory tree of FTP server, all entries in location bar after server name become the same and display the name of current folder, so if I'm in myproject/images, location bar displays images / images. Pressing any of those entries does nothing. This only happens in "button" mode of the bar. If I click aside of location buttons to switch to string mode, than the location is displayed properly.

Reproducible: Always

Steps to Reproduce:
1. Logon to any FTP server
2. Descend at least 2 directories down the tree
3.

Actual Results:  
All buttons on location bar display same names, clicking on them does nothing.

Expected Results:  
Buttons should properly display names of all folders in current tree branch, clicking on the button should change directory.
Comment 1 Alexey Stukalov 2015-12-20 18:30:19 UTC
I too have a very similar problem since the upgrade to 15.12 and Plasma 5.5 on Archlinux.
Both sftp:// and webdavs:// triplicate the last subfolder 3 times, i.e. instead of "webdav/a/b/c/d" it shows "c/d/d/d".
Comment 2 Julio J. 2015-12-22 16:09:05 UTC
Same behaviour here, since upgrading to 15.12 on Arch it started happening, both sftp:// and fish:// folders. I'm guessing it's present on all network protocols.
Comment 3 Emmanuel Pescosta 2015-12-23 16:22:37 UTC
Thanks for the bug report!

This bug will be fixed with the next framework (5.18) release.