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, and then upgrading and the failure case (which you've already kindly presented). 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: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1292548/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
