Samba client/server cannot manage special characters
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba (Ubuntu) |
New
|
Low
|
Unassigned |
Bug Description
A little background... I have a media server running Ubu 10.04 with a media share containing FLAC files in a pretty standard hierarchy. This server (in service since 2010) has been accessed by machines running from 10.04 to 14.04 without any issues.
I have recently built/upgraded two client machines to from 14.04 to 16.04 and these machines are having trouble with that Samba-served share. If a file or folder contains a question mark, that file or folder will not be accessible--though it will appear in Nautilus and in the Terminal.
In the case of a file (say 01 - Who Are You?.flac) if you double-click the file (or otherwise launch it) you will get a file not found error; this is true in the Terminal as well (using, say, ffplay). In the case of a folder it will appear to be empty and if you double-click the folder you will get a folder not found error. In either case, the question mark is clearly shown in both Nautilus and bash.
If I create a share on one of my Ubu 16.04 machines (with similar parameters) those files and folders which contain question marks do not appear on client machines (regardless of version) when that share is mounted. Interestingly, these 16.04 servers are also not able to share files or folders which contain colons.
This is all with mangled file names disabled. If I enable it, I get mangled file names which share as expected.
(Other characters may be effected, but these are the only two I have tested.)
In short, files and folders containing question marks and colons should appear in shares and be launchable. With 16.04 this is not the case.
From the 10.04 machine:
samba:
Installed: 2:3.4.7~
Candidate: 2:3.4.7~
Version table:
*** 2:3.4.7~
500 http://
500 http://
100 /var/lib/
2:
500 http://
From the 16.04 machine:
samba:
Installed: 2:4.3.9+
Candidate: 2:4.3.9+
Version table:
*** 2:4.3.9+
500 http://
500 http://
100 /var/lib/
2:
500 http://
I am happy to provide additional details or tests as requested.
Thank you for taking the time to report this bug and helping to make Ubuntu better.
If this is valid, it sounds like a bug that should be sent upstream to me. It wouldn't be appropriate for Ubuntu to differ from upstream on this issue.
Or if this is a bug specific to Ubuntu, please could you identify that?
For Ubuntu then, I'd say that validity depends on upstream's opinion. Please could you check if you get the same behaviour from samba built from the latest upstream source, and if you do, raise this with upstream?