Oh, here we go again. Yet another Ubuntu bug report that goes
completely ignored. The requested information (six months ago) is even
provided (same day as requested) and nothing is done with it like so
many other bugs.
Is this yet another problem that is simply too difficult to solve and so
Public bug reported:
I have both libpam-ldap and libpam-krb5 installed because I am using
Kerberos for authentication here. The implication is that I am not
using passwords in ldap.
When I try to change my password I get this in the auth.log:
Apr 1 23:21:30 foo passwd[4927]:
Public bug reported:
I was trying to apt-get install dpkg to work around #944452 and got
the following while trying to upgrade slapd:
Setting up slapd (2.4.28-1.1ubuntu4) ...
Use of uninitialized value $type in ucfirst at
/usr/share/perl5/Debconf/AutoSelect.pm line 35.
Backing up
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/990742
Title:
does not depend on libsasl2-2 (= 2.1.24)
To manage notifications about this bug go to:
On 12-05-04 12:11 AM, Martin Pitt wrote:
Hello Brian, or anyone else affected,
Accepted cyrus-sasl2 into precise-proposed. The package will build now
and be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
Public bug reported:
The php5 update to 5.3.10-1ubuntu3.1 does not have a changelog at
http://changelogs.ubuntu.com/changelogs/pool/main/p/php5/php5_5.3.10-1ubuntu3.1/changelog.
People want to know what changes an update brings before they apply
them.
** Affects: php5 (Ubuntu)
Importance:
Public bug reported:
Squid 3.1.19 is failing with:
assertion failed: AclProxyAuth.cc:229:
authenticateUserAuthenticated(Filled(checklist)-auth_user_request)
This is reported and fixed upstream however the fix only went into 3.2
because it's too invasive for 3.1.
Thus, squid3 on Qunatal AND
OK. So when will this be fixed? This bug has been open for a year and
3 months already. It was reported in the previous LTS and is still
present in the current LTS. That makes this bug over 2 years old.
Is having a crashing proxy server in two LTS releases acceptable? Is it
acceptable
Public bug reported:
While installing sasl2-bin I got the following message:
Setting up sasl2-bin (2.1.25.dfsg1-3ubuntu0.1) ...
update-rc.d: warning: saslauthd stop runlevel arguments (0 1 6) do not match
LSB Default-Stop values (1)
* Starting SASL Authentication Daemon saslauthd
...done.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1059567
Title:
update-rc.d: warning: saslauthd stop runlevel arguments (0 1 6) do not
match LSB Default-Stop values (1)
To
Yes, please. Do a backport to Intrepid. dnsutils is useless (in a
network with only IP6 dns servers) on Intrepid without this fix.
--
[intrepid] IPv6 unusable
https://bugs.launchpad.net/bugs/249824
You received this bug notification because you are a member of Ubuntu
Server Team, which is
On Tue, 2008-12-02 at 23:22 +, Manson Thomas wrote:
Will anybody have the decency to answer ? any ubuntero here ?
I had to disable my secondary DNS server for dozens of .fr. domains
because of this bug.
Some people are becoming upset and I totally agree with that.
Please, give an
On Wed, 2008-12-03 at 15:29 +, Matt LaPlante wrote:
Subscribers, please test the proposed patch as thoroughly as possible to
increase its chances of acceptance.
I only needed the dnsutils package (for dig, host, etc.) but that worked
just great for me.
--
[intrepid] IPv6 unusable
3 months ago this bug was filed and triaged and yet nothing has been
done about it. You do realize that this prevents us from being able to
configure networks in virt-manager, right? You know that this means
that nothing except basic virtual guests can be created right?
Fixing this is simply a
This patch fixes the problem.
** Patch added: the fix
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/668043/+attachment/1822422/+files/9030-Only-attempt-removal-of-the-rule-allowing-tftp-if-it-was-added.patch
--
You received this bug notification because you are a member of Ubuntu
On Thu, 2011-02-03 at 21:04 +, Serge Hallyn wrote:
(If it did in fact fail, then I'll revert the offending patch
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=fd5b15ff1a2ec37e75609c091522ae1e2c74c811
as per http://bugs.gentoo.org/334921.
Please take note that the fix that I
Public bug reported:
If one configures more than one network to use DHCP, multiple dnsmasq
processes are started, one for each network. The problem is that each
process has --dhcp-lease-max configured for the number of leases in it's
own network. But since multiple dnsmasq processes share the
** Bug watch added: Red Hat Bugzilla #674356
https://bugzilla.redhat.com/show_bug.cgi?id=674356
** Also affects: libvirt via
https://bugzilla.redhat.com/show_bug.cgi?id=674356
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
There is a patch to fix this problem in the upstream bug report.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/713071
Title:
dnsmasq option --dhcp-lease-max prevents startup for
On Thu, 2011-02-03 at 13:39 +, Serge Hallyn wrote:
Please test the packages from the attachment in comment #6.
I would if I could but I can't because my libvirt has other patches
(i.e. bug 713071) for bugs which I have run into and filed reports
upstream in my libvirt. Running your above
On Sat, 2009-02-21 at 02:51 +, duanedesign wrote:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently.
No, there hasn't. Unless I am mistaken, it seems the ball is in your
Chuck: your New-Confirmed seems to contradict Steve's assessment, yes?
I can see Steve's point, so I raised the issue on the nssldap list at
PADL but didn't really get anything meaningful back. It would appear
that nobody is listening there or there is no solution to this problem.
I.e. to this
Steve,
Would you agree to adding the broken_shadow option to pam_unix in the
account mode?
The use case here is a laptop that normally authenticates with kerberos
and gets it's NSS from LDAP, including the shadow map, even though it's
not really used in this situation (due to the use of
On Sat, 2009-10-24 at 06:56 +, Steve Langasek wrote:
No, I would not.
~sigh~
It's a configuration error to have a password record
with an x without a corresponding shadow entry, and we shouldn't
ignore such configuration errors by default.
It's not a configuration error when the
Steve,
You can close this. i have figured out how to make my LDAP passwd map
behave.
For anyone following along or who may find this in their travels, you
will want to remove the shadowAccount object class from any ldap entries
which represent users that should be authenticated by Kerberos --
Public bug reported:
While trying to upgrade my hardy machine to lucid today I got the
following failure:
Selecting previously deselected package mysql-server-core-5.1.
Unpacking mysql-server-core-5.1 (from
.../mysql-server-core-5.1_5.1.41-3ubuntu7_i386.deb) ...
dpkg: error processing
26 matches
Mail list logo
