sorry, I can't help you, because
- I've updated to ubuntu 16.04. xenial
- I did use now network-connect to my (ubuntu)server via nfs insted of
samba (because I havn't a windows pc any more)
So I can't reproduce the errors any more
Christoph Theuring
P.S.
Its a long time ago I reported this bug ...
Am 17.05.2017 um 23:45 schrieb Joshua Powers:
> Steps to reproqduce would be best. For example, can I just apt install
> samba and hit the issue? did you have some sort of special configuration
> or turn on some feature?
>
> It would be even better if you could do it in a LXC container, e.g.:
>
> lxc launch ubuntu-daily:trusty t
> lxc exec t bash
> ...
> (give me the steps you use to setup samba and reproduce the issue)
>
Hello,
sorry, I can't help you, because
- I've updated to ubuntu 16.04. xenial
- I did use now network-connect to my (ubuntu)server via nfs insted of
samba (because I havn't a windows pc any more)
So I can't reproduce the errors any more
Christoph Theuring
P.S.
Its a long time ago I reported this bug ...
Am 17.05.2017 um 23:45 schrieb Joshua Powers:
> Steps to reproqduce would be best. For example, can I just apt install
> samba and hit the issue? did you have some sort of special configuration
> or turn on some feature?
>
> It would be even better if you could do it in a LXC container, e.g.:
>
> lxc launch ubuntu-daily:trusty t
> lxc exec t bash
> ...
> (give me the steps you use to setup samba and reproduce the issue)
>