It appears this was fixed with the patch
https://attachments.samba.org/attachment.cgi?id=9882 in Samba bug 10524
(https://bugzilla.samba.org/show_bug.cgi?id=10524) against their 4.1
code base. Is there any chance in getting this applied to the 14.04 LTS
Samba release or the Utopic release
In case it assists when this bug gets triaged, I've repeated my build
today with Samba 2:4.1.6+dfsg-1 from Jessie and this bug is also not
present in the 4.1.6 release, which includes security fixes over 4.1.5.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
As this bug stops an other application using the Kerberos details stored
in the Samba directory, it is quite a show-stopper for the Trusty
release. Is there anything I can tag this bug with or anyone I should
notify in an attempt to get 4.1.5 pulled from Jessie for the Trusty
release?
--
You
Public bug reported:
To reproduce this bug, carry out the following:
Install a fresh Trust Tahr 14.04 AMD64 development build in a (KVM)
virtual machine as a basic server.
Install the samba (2:4.1.3+dfsg-2ubuntu3) and bind9 packages.
Provision an Active Directory Domain with the following
I've just upgraded Samba to 2:4.1.5+dfsg-1 from the Debian Jessie
repository. This also forced the following updates:
2014-03-10 17:13:00 upgrade python-samba:amd64 2:4.1.3+dfsg-2ubuntu3
2:4.1.5+dfsg-1
2014-03-10 17:13:00 upgrade samba-dsdb-modules:amd64 2:4.1.3+dfsg-2ubuntu3
2:4.1.5+dfsg-1
A year has passed since this packaging issue was solved in the Debian
repositories. How can we go about getting it included in the 10.04 LTS?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
** Attachment added: cupsd.conf
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/494141/+attachment/1764561/+files/cupsd.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Sorry for the two posts, I couldn't work out how to attach more than one
file to a comment! cupsd.conf and smb.conf as requested. IP addresses
and domain names have been changed as per RFC1166 and RFC2606
respectively to protect privacy.
** Attachment added: smb.conf
Confirmed as still being an issue on a fresh installation of Maverick
(10.10) RC AM64 server.
--
dhcp3-server launches before upstart brings all interface, thus failing to start
https://bugs.launchpad.net/bugs/580319
You received this bug notification because you are a member of Ubuntu
Server
As another proposed workaround, I have found that editing /etc/init/rc-
sysinit.conf to change the line:
start on filesystem and net-device-up IFACE=lo
to:
start on filesystem and net-device-up IFACE=br0
also appears to produce the desired result by delaying running of legacy
*** This bug is a duplicate of bug 580319 ***
https://bugs.launchpad.net/bugs/580319
** This bug has been marked a duplicate of bug 580319
dhcp3-server launches before upstart brings all interface, thus failing to
start
* You can subscribe to bug 580319 by following this link:
It appears that the bind 9.4 and 9.5 packages have missed out on this
patch. The Jaunty bind 9.6 package has the fix but for those of us that
are still running Intrepid or Hardy LTS. Is there any chance of getting
it applied to all the supported releases?
Thanks in advance,
Ian.
--
named
I've only just noticed this bug report. For the last couple of Ubuntu
releases I've been patching and re-compiling the openldap (previously
openldap2.3) packages in my PPA as I use the smbk5pwd overlay.
If you'd like to make use of my work, add the following to apt's
sources.list for Intrepid:
13 matches
Mail list logo
