Up-stream bug filed: https://bugzilla.samba.org/show_bug.cgi?id=12160
** Bug watch added: Samba Bugzilla #12160
https://bugzilla.samba.org/show_bug.cgi?id=12160
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Ok. Where?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612000
Title:
Samba client/server cannot manage special characters
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Thanks James. In this case you should report your bug to the upstream
Samba project.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612000
Title:
Samba client/server cannot manage special characters
I added the latest upstream Samba to my test 16.04 machine using these
instructions:
http://askubuntu.com/questions/813171/latest-upstream-samba-on-
ubuntu-16-04-how
This appears to have had no appreciable effect on the performance of
this machine to read files with question marks in their paths.
Ok, so this is a bit weirder than expected.
I didn't want to mess with an existing machine so I built a new machine
with Ubu 16.04 and updated it. I found I was able to mount the (10.04)
server share through Nautilus without issue and play files containing
question marks. However, when I added t
I suggest that you test on 16.04 with the latest upstream release of
Samba built from source. Sorry, I have many bugs to triage so I am
unable to go through this with you in detail. You may be able to get
further help from http://www.ubuntu.com/support/community
--
You received this bug notificat
I am happy to help. Should I test with a different distribution or (if
you can give me instructions to do so) should I test on Ubuntu with a
different version of Samba?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
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 iden
