By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1502

Summary: Konsole does not correctly display forward slash now supported in konqueror
Product: TDE Reporter: Darrell <darrella>
Component: tdebaseAssignee: Timothy Pearson <kb9vqf>
Status: RESOLVED INVALID    
Severity: minor CC: bugwatch, darrella, michele.calgaro, slavek.banko
Priority: P5    
Version: R14.0.x [Trinity]   
Hardware: Other   
OS: Linux   
Compiler Version: TDE Version String:
Application Version: Application Name:

Description Darrell 2013-05-09 10:34:27 CDT
As discussed in bug report 269, konsole does not correctly display a forward slash used in a file name created in konqueror.

To replicate:

1. Ensure Trinity is updated to the latest GIT sources.
2. Ensure the appropriate UTF-8 language environment variable (LANG) is exported/set before starting Trinity.
3. From within konqueror, create or rename a file to include a forward slash.
4. Press F4 to open konsole to the same directory.
5. Perform an ls to view the directory files.
6. Verify the forward slash is not displayed correctly.
Comment 1 Slávek Banko 2013-05-15 13:41:40 CDT
I tested in 3.5.13.2 and I did not notice any problem. Tested file name and also folder name - both fine.
Comment 2 Darrell 2013-05-15 15:01:52 CDT
I'm using GIT.

Did you backport the patch to 3.5.13.2?
Comment 3 Slávek Banko 2013-05-15 15:09:15 CDT
Yes, commit b4a23465 is already backported into v3.5.13-sru branch. That was why I tested your reported bug also in 3.5.13.2.
Comment 4 Darrell 2013-05-15 16:01:37 CDT
At the moment then we'll have to presume something different about GIT or the underlying distro.
Comment 5 Michele Calgaro 2014-03-06 23:19:34 CST
I tested this today. No problem on my system, file names containing / are correctly displayed in Konsole.
locale gives:
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Darrell, is it still a valid bug?
Comment 6 Darrell 2014-03-07 13:41:02 CST
Still valid.

In konqueror the files appear as expected:

test/folder
test/file

In konsole the text appears like this:

test%2ffolder/
test%2ffile

Changing LANG to en_US.UTF-8 does not fix the problem and causes konqueror to display the slash with the same %2f.
Comment 7 Michele Calgaro 2014-03-08 00:18:15 CST
(In reply to Darrell from comment #6)
Darrell, just curious. Did you create the name with / before or after changing the locale?
Could you also post your locale settings?
Comment 8 Darrell 2014-03-08 13:05:32 CST
>Did you create the name with / before or after changing the locale?
What difference does that make. That slash doesn't work. Period.

>Could you also post your locale settings?
Defaults:
LANG=en_US
LC_COLLATE=C
Comment 9 Michele Calgaro 2014-03-08 21:03:20 CST
(In reply to Darrell from comment #8)
>>Did you create the name with / before or after changing the locale?
>What difference does that make. That slash doesn't work. Period.
Perhaps the / is coded in different way if using different locale (even though it is part of the ASCII table, so it should not). 
Anyhow I was just curious
Comment 10 Michele Calgaro 2018-07-30 10:19:13 CDT
This depends on the encoding used for Konsole and the system.
I am able to replicate a similar behaviour if I create a file in Konqueror with / and change the encoding settings in Konsole.
This is not a bug, the system is actually doing things as instructed. It is no different from opening a document with a different encoding from what it was created with.