[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-04-01 Thread Robie Basak
Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292548 Title: smb.conf contains valid users = %S in [global] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-04-01 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: samba (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292548 Title: smb.

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-04-01 Thread Raoul Bhatia
Hi Robie, Yes, there is a "valid users = %S" line present in the smb.conf file. When I comment it out, smbclient -L works as expected. What i did: 1) Comment out "valid users = %S", see the diff: > root@ubuntu:/etc/samba# diff -u ~/smb.conf.old smb.conf > --- /root/smb.conf.old 2014-04-01 18:19:

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-04-01 Thread Sebastien Bacher
** Also affects: samba (Ubuntu Trusty) Importance: High Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292548 Title: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (s

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-04-01 Thread Robie Basak
Please can you see if this is bug 1296289, and if the fix there (the "valid users" line) works? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292548 Title: Standalone Server: Update from Samba 2:3.

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-04-01 Thread Sebastien Bacher
** Tags added: rls-s-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292548 Title: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-03-31 Thread Raoul Bhatia
> #!/bin/sh > > VER=4.1.6+dfsg-1 > ARCH=amd64 > > for p in samba samba-common-bin samba-dsdb-modules samba-vfs-modules > samba-libs libwbclient0 python-samba smbclient libsmbclient; do > wget > "http://ftp.at.debian.org/debian/pool/main/s/samba/${p}_${VER}_${ARCH}.deb"; > done > > wget > "

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-03-31 Thread Raoul Bhatia
If anyone wants to quickly update to the packages from Debian until this issue is fixed, here some wget lines for retrieving them: wget "http://ftp.at.debian.org/debian/pool/main/s/samba/samba_4.1.5+dfsg-1_amd64.deb"; wget "http://ftp.at.debian.org/debian/pool/main/s/samba/samba-common_4.1.5+dfs

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-03-22 Thread Raoul Bhatia
Dear Robie, actually, it is quite easy to reproduce during an update from saucy to trusty and i suspect that this bug will even strike when you do a clean trusty install. Nevertheless, i reproduced this issue with a fresh saucy install: 1. install saucy using http://at.mirror.archive.ubuntu.com

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-03-17 Thread Robie Basak
Thanks. So 2:4.1.3+dfsg-2ubuntu3 from Trusty has this issue, but 2:4.1.5+dfsg-1 from Debian does not? Sounds like we need to either merge it, or figure out the fix and apply it. ** Changed in: samba (Ubuntu) Status: Incomplete => New ** Changed in: samba (Ubuntu) Importance: Undecided =

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-03-17 Thread Robie Basak
I don't see exact reproduction steps though. Please can you supply this, so that developers can focus on the bug, rather than having to second guess what you did first? These should be steps to reproduce the problem including starting on a fresh Saucy instance, configuring samba as you had done, an

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-03-17 Thread Raoul Bhatia
Thank you for your fast reply. Updating Samba 3 to Samba 4 *is* possible, please see https://wiki.samba.org/index.php/Updating_Samba . There might be some configuration changes but all in all it is no big deal to manually merge them - at least not for a basic setup without any active directory (A

[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

2014-03-17 Thread Robie Basak
Thank you for taking the time to report this bug and helping to make Ubuntu better. The upgrade from samba 3 to samba 4 is a major change, and I wouldn't expect automatic upgrades to be possible in all cases. Please can you check upstream release notes and confirm that this is even possible, and t