Bug 263169 - Filename in properties dialog of search result shows encoded filename
Summary: Filename in properties dialog of search result shows encoded filename
Status: RESOLVED DUPLICATE of bug 308085
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: SVN
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-14 20:02 UTC by Elias Probst
Modified: 2012-11-09 20:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshow showing the file properties of a dolphin nepomuk search result (111.34 KB, image/png)
2011-01-14 20:02 UTC, Elias Probst
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elias Probst 2011-01-14 20:02:15 UTC
Created attachment 56021 [details]
Screenshow showing the file properties of a dolphin nepomuk search result

Version:           unspecified (using KDE 4.5.95) 
OS:                Linux

When opening the properties dialog for a file out of the Dolphin search results (Nepomuk based) the filename is messed up/wrong encoded.

Reproducible: Always

Steps to Reproduce:
1. Click on 'Find' in Dolphin
2. Enter a search term which produces some results
3. Rightclick on a file and select 'Properties'
4. Look at the field showing the filename

Actual Results:  
The filename contains the full URL of the file instead of just the filename.
Furthermore this text is URLencoded and each % character (which is usually used in URLencoded strings) is shown as _
See also screenshot in attachment.

Expected Results:  
I'd expect the properties dialog to show the regular file information just like it is shown when opening it for the file regularly when browsing to it's folder and opening the dialog from there.

I don't know whether this is a Dolphin or Nepomuk bug.
Please re-assign if necessary.
Comment 1 Vishesh Handa 2012-11-09 20:18:58 UTC

*** This bug has been marked as a duplicate of bug 308085 ***