Bug 502012 - Unable to open SMB share with files containing backslash (no name mangling)
Summary: Unable to open SMB share with files containing backslash (no name mangling)
Status: REPORTED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 6.12.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-26 09:39 UTC by Norbert
Modified: 2025-03-26 09:39 UTC (History)
1 user (show)

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

Attachments
Samba server config (459 bytes, text/plain)
2025-03-26 09:39 UTC, Norbert 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Norbert 2025-03-26 09:39:31 UTC 
Created attachment 179747 [details]
Samba server config

SUMMARY
I'm unable to open directory containing for example file 'a\'. This is an unusual filename I agree, but I've created
it by accident in my PC's home directory and I'm unable to even list the files on my Fedora laptop. And all I get is
repeated password prompts. Not at all specific to the issue.

Mounting via cifs works, removing said file makes the share work, so not a mismatched password problem.
This files only get forwarded with mangled names set to no, see attached samba server config: smb.conf.

STEPS TO REPRODUCE
1. Set mangled names to no in samba server config
2. Create 'a\' file in share

OBSERVED RESULT
I'm unable to open share Test in dolphin.
Logs are a combination of:
  kded6[4170]: is_bad_finfo_name: bad finfo->name
  dolphin[4498]: is_bad_finfo_name: bad finfo->name
  smbnotifier[4170]: kf.kio.workers.smb: -- Failed to smbc_opendir: Invalid argument
  smbnotifier[4723]: kf.kio.workers.smb: -- Failed to smbc_opendir: Permission denied

EXPECTED RESULT
Open the share or at least notify what's wrong


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 41
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
I observed the issue for a quite a time, happen to just debug it properly.
So it's not a new issue.