Bug 390146 - Krusader can't jump to files in folders beginning with "#"
Summary: Krusader can't jump to files in folders beginning with "#"
Status: RESOLVED FIXED
Alias: None
Product: krusader
Classification: Applications
Component: search (show other bugs)
Version: 2.6.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Krusader Bugs Distribution List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-09 12:45 UTC by Rafael Linux User
Modified: 2018-08-16 22:48 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Results of a search (107.25 KB, image/png)
2018-06-09 20:51 UTC, Rafael Linux User
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael Linux User 2018-02-09 12:45:39 UTC
While using Krusader to search files, I realized that, in the list of found files, when I click on some files, Krusader doesn't not bring me to the folder in which the file were in. Now, I discovered that Dolphin does the same, and it's related only with files that are inside folders that begin with the "#" symbol.

It happens in any of my OpenSUSE with KDE installations.

Any fix for this?

Thank you
Comment 1 Julian Steinmann 2018-02-14 14:46:45 UTC
Hmm. I am not able to reproduce this with Dolphin 17.12.2. If I create a folder named "#Test" and put a file in it, I am able to search for that file and right click to "Open path". The path is then correctly opened. Did I misunderstand your problem? And could you test this again with Dolphin 17.12.2, if possible?
Comment 2 Christoph Feck 2018-03-01 00:47:59 UTC
If you can provide the information requested in comment #1, please add it.
Comment 3 Christoph Feck 2018-03-29 14:03:26 UTC
To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.
Comment 4 Julian Steinmann 2018-04-12 09:12:07 UTC
This bug has been inactive for quite a while... If no new comments are added, I'll close this bug in two weeks from now. If you can add the information requested in comment 1, please do so.
Comment 5 Julian Steinmann 2018-04-28 11:47:48 UTC
There have been multiple attempts to notify the original reporter, but none of them were fruitful. I am going to close this bug for now, please reopen the report if you can still reproduce this issue. Thanks!
Comment 6 Rafael Linux User 2018-06-09 20:51:56 UTC
Created attachment 113179 [details]
Results of a search

This is a search result. All files are in the same root path, but Krusader can't change to real folder of them that contains "#".
Comment 7 Rafael Linux User 2018-06-09 20:54:21 UTC
I discovered when attaching the capture that if a file contains "#" in her name, it can't be attached (from Firefox, in this case)!!!. I begin to think that this bug could be more general than for Krusader/Dolphin.
Comment 8 Rafael Linux User 2018-08-15 21:52:32 UTC
Nowadays, this bug only affect Krusader, so I changed product. This bug is still in Versión 2.6.0 "Stiff Challenges" version. I was doubting about it was happening in NFS mounted folders, but it's not the problem. Locally it happens too  :(

I have the same file in two folders named:
/home/Music/Pendientes/#NewAge/NewFolder
/home/Music/Pendientes/NewAge/NewFolder
If I look for the file, Krusader show both folders but if I click on the first one, Krusader show me only /home/Music/Pendientes/ , ignoring the rest of the folders. Is in a XFS filesystem with locale LANG=es_ES.UTF-8 , if it can help.
Comment 9 Toni Asensi Esteve 2018-08-16 19:33:36 UTC
Hi, Rafael. The problem doesn't happen to me using the git version of Krusader under Kubuntu 18.04, with ext4 and locale "LANG=es_ES.UTF-8". Can you try it using Krusader 2.7.0 or Krusader 2.7.1?

You can also use use the git version of Krusader, there are instructions in https://commits.kde.org/krusader?path=INSTALL
Comment 10 Rafael Linux User 2018-08-16 22:46:48 UTC
(In reply to Toni Asensi Esteve from comment #9)
> Hi, Rafael. The problem doesn't happen to me using the git version of
> Krusader under Kubuntu 18.04, with ext4 and locale "LANG=es_ES.UTF-8". Can
> you try it using Krusader 2.7.0 or Krusader 2.7.1?
> 
> You can also use use the git version of Krusader, there are instructions in
> https://commits.kde.org/krusader?path=INSTALL

Eureka!! You solved problem in Version 2.7.1 "Peace of Mind". I installed it from "KDE Extras: Experimental", cause was easier for me than compile or try from GIT. And it worked just as expected.

Moreover, the link you included let me know exactly what I should install from console with a "zypper" command before the first time I launch Krusader!!

THANK YOU