Bug 442482

Summary: Dolphin location bar doesn't take folder names with capital letters if they also exist with small letters
Product: [Applications] dolphin Reporter: David <david.cortes.rivera>
Component: bars: locationAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: dolphin-bugs-null, john.kizer, kdedev, p.r.worrall
Priority: NOR Keywords: triaged
Version First Reported In: 21.08.0   
Target Milestone: ---   
Platform: Debian unstable   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description David 2021-09-15 15:58:07 UTC 
SUMMARY
If in my home folder I have folders '.a' and '.A', dolphin will not let me type '.A' in the address bar as it will always automatically change it to '.a', making it difficult to move to folder '.A'.

STEPS TO REPRODUCE
1. Create folders '.a' and '.A' in your home folder.
2. Launch Dolphin, go to home folder, click the address bar.
3. Put the writing focus at the end of the address bar, write ".", and then "Shift + a" so as to make a capital "A".

OBSERVED RESULT
Automatically changes it to small "a", thus blocking me from moving to folder ".A".

EXPECTED RESULT
Should take a capital "A" just like I inputted.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Paul Worrall 2021-09-15 18:48:40 UTC 
Can reproduce

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.22.80
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-27-generic (64-bit)
Graphics Platform: Wayland
Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics
Memory: 7.7 GiB of RAM
Graphics Processor: AMD CEDAR
Comment 2 TraceyC 2024-05-15 22:28:33 UTC 
This is still an issue in Plasma 6
Possibly related to #42662

Operating System: Solus 4.5
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.6.3
Comment 3 TraceyC 2024-06-12 18:13:04 UTC 
That related bug should be 426622
Comment 4 John Kizer 2025-05-14 19:39:56 UTC 
Merging in with what I believe is the underlying issue, thanks!

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