This again appears to be broken, for both security.ubuntu.com and
us.archive.ubuntu.com, at least.
Exactly as Jens had noted above - this is (also) an issue with
records being provided, but not accessible. Though security.ubuntu.com
appears to be in ever-so-slightly better shape than
Thanks, Chris. Further references for anyone else looking at this:
- https://forums.he.net/index.php?topic=3345.0 (probably the one you saw?)
- https://forums.he.net/index.php?topic=2911.15
- Bug #1412943
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
do you use HE?
Why, yes! Is this a known issue?
(For anyone else's reference, HE being Hurricane Electric Internet
Services http://he.net/ - and in my case, their IPv6 Tunnel Broker
https://tunnelbroker.net/.)
I have had native IPv6 available from my ISP for a while now - but the
last time I
Some interesting comments left in the notes field at
http://www.openldap.org/its/index.cgi/Software%20Bugs?id=6548 :
fixed in master
fixed in RE24
So hopefully this means that a fix is pending - eventually?
** Description changed:
Reported upstream at
-
Some interesting comments left in the notes field at
http://www.openldap.org/its/index.cgi/Software%20Bugs?id=6548 :
fixed in master
fixed in RE24
So hopefully this means that a fix is pending - eventually?
** Description changed:
Reported upstream at
-
** Description changed:
Reported upstream at
http://www.openldap.org/its/index.cgi/Incoming?id=6548 , but it needs to
be re-opened there.
Many connection_read(): no connection! warnings are written to
/var/log/debug and /var/log/syslog by slapd. As stated at
** Description changed:
Reported upstream at
http://www.openldap.org/its/index.cgi/Incoming?id=6548 , but it needs to
be re-opened there.
Many connection_read(): no connection! warnings are written to
/var/log/debug and /var/log/syslog by slapd. As stated at
I also have an LDAP setup on a clean Ubuntu 11.10 install - but with
local homedirs - and am also experiencing this issue.
The gsettings get is also hanging with gdm - so switching to gdm from
lightdm is not a surefire fix for this issue, either.
Disabling the 90qt-ally script immediately fixed
I have ipset working under 10.10, though without the default Ubuntu
packages. I don't understand how the debbugs #485182 upstream report is
closed as Fix Released.
I spent some time on #Netfilter on IRC, and have sqft (Jan
Engelhardt?) to thank for most of this information.
First, to clarify -
In response to comment #1, isn't that contradictory? Is there something
specific within IPv6 that didn't exist in IPv4, as IPv4 also allowed an
interface to be assigned multiple addresses? If aliases aren't
necessary, how can multiple addresses (either IPv4 and IPv6 or multiple
IPv6) be assigned
What are the next steps necessary to have this patch included into a
future release?
--
pam_group does not support NSS groups
https://bugs.launchpad.net/bugs/297408
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Reported upstream at
http://www.openldap.org/its/index.cgi/Incoming?id=6548 , but it needs to
be re-opened there.
Many connection_read(): no connection! warnings are written to
/var/log/debug and /var/log/syslog by slapd. As stated at
** Attachment added: LDAP Tests and Logs.txt
http://launchpadlibrarian.net/50398131/LDAP%20Tests%20and%20Logs.txt
--
Many connection_read(): no connection! warnings from OpenLDAP server when
using ldapi:/// and a bind DN (no external authentication)
https://bugs.launchpad.net/bugs/594840
Public bug reported:
Reported upstream at
http://www.openldap.org/its/index.cgi/Incoming?id=6548 , but it needs to
be re-opened there.
Many connection_read(): no connection! warnings are written to
/var/log/debug and /var/log/syslog by slapd. As stated at
** Attachment added: LDAP Tests and Logs.txt
http://launchpadlibrarian.net/50398131/LDAP%20Tests%20and%20Logs.txt
--
Many connection_read(): no connection! warnings from OpenLDAP server when
using ldapi:/// and a bind DN (no external authentication)
https://bugs.launchpad.net/bugs/594840
Public bug reported:
Binary package hint: libpam-ldap
Many connection_read(): no connection! warnings are written to
/var/log/debug and /var/log/syslog by slapd. However, as stated at
http://www.openldap.org/lists/openldap-software/200811/msg00079.html ,
this is not a problem with slapd, but a
Found that this only happens using ldapi:/// (the configured default),
and not ldap:/// . Need to review and make sure that this isn't
actually an issue with slapd.
--
pam_ldap disconnects from LDAP without unbinding, causing many
connection_read(): no connection! warnings in logs
Issue is reproducible even with ldapsearch -H ldapi:///, but only if a
bind DN is specified and external authentication is not used. Appears
to be an issue with slapd itself, and not pam_ldap.
** Changed in: libpam-ldap (Ubuntu)
Status: New = Invalid
--
pam_ldap disconnects from LDAP
Reported outstanding issue at
http://www.openldap.org/its/index.cgi?findid=6548 .
--
pam_ldap disconnects from LDAP without unbinding, causing many
connection_read(): no connection! warnings in logs
https://bugs.launchpad.net/bugs/578463
You received this bug notification because you are a
Public bug reported:
Binary package hint: libpam-ldap
Many connection_read(): no connection! warnings are written to
/var/log/debug and /var/log/syslog by slapd. However, as stated at
http://www.openldap.org/lists/openldap-software/200811/msg00079.html ,
this is not a problem with slapd, but a
Found that this only happens using ldapi:/// (the configured default),
and not ldap:/// . Need to review and make sure that this isn't
actually an issue with slapd.
--
pam_ldap disconnects from LDAP without unbinding, causing many
connection_read(): no connection! warnings in logs
Issue is reproducible even with ldapsearch -H ldapi:///, but only if a
bind DN is specified and external authentication is not used. Appears
to be an issue with slapd itself, and not pam_ldap.
** Changed in: libpam-ldap (Ubuntu)
Status: New = Invalid
--
pam_ldap disconnects from LDAP
Reported outstanding issue at
http://www.openldap.org/its/index.cgi?findid=6548 .
--
pam_ldap disconnects from LDAP without unbinding, causing many
connection_read(): no connection! warnings in logs
https://bugs.launchpad.net/bugs/578463
You received this bug notification because you are a
Public bug reported:
Binary package hint: php5
On Ubuntu 10.04 (lucid), installed php5-cgi . Observed that the
php5-cgi is copied as both /usr/bin/php5-cgi and /usr/lib/cgi-bin/php5 .
One of these should be a symbolic link instead - probably /usr/lib/cgi-
bin/php5 to /usr/bin/php5-cgi ? This
Public bug reported:
Binary package hint: php5
On Ubuntu 10.04 (lucid), installed php5-cgi . Observed that the
php5-cgi is copied as both /usr/bin/php5-cgi and /usr/lib/cgi-bin/php5 .
One of these should be a symbolic link instead - probably /usr/lib/cgi-
bin/php5 to /usr/bin/php5-cgi ? This
Public bug reported:
As mentioned on https://blueprints.launchpad.net/ubuntu/+spec/lucid-
duplicated-packages , OpenLDAP should be migrated from db4.7 to db4.8 -
especially as libdb4.8 already seems to be installed by default, and
libdb4.7 isn't.
I am willing to help with this, including testing
Public bug reported:
As mentioned on https://blueprints.launchpad.net/ubuntu/+spec/lucid-
duplicated-packages , OpenLDAP should be migrated from db4.7 to db4.8 -
especially as libdb4.8 already seems to be installed by default, and
libdb4.7 isn't.
I am willing to help with this, including testing
This still exists in 10.04 / Lucid.
--
avahi-autoipd script shows RTNETLINK error when run with multiple network
interfaces
https://bugs.launchpad.net/bugs/425854
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
: inetOrgPerson
objectclass: posixAccount
objectclass: top
sn: Ziesemer
uid: mark-test
uidnumber: 10003
Line added to /etc/security/group.conf :
*; *; %testPAMGroup; Al-2400; cdrom, audio, video
Test:
$ sudo su - mark-test
No directory, logging in with HOME=/
$ id
uid=10003(mark-test) gid=2000
Thanks to Edward for a note concerning the use of whitespace. It is now
working for me, as long as there is no space padded around the LDAP
group. I.E., ...;%testPAMGroup;... works, but ...; %testPAMGroup;...
doesn't.
Testing with sudo login then works by default. Usage under sudo su -
Any chance for Edward's patch to be included in a release? Otherwise,
what is the best way for me to apply this patch myself to my own
systems? Or is there a better / alternative solution for the same
requirement? Thanks!
--
pam_group does support NSS groups
After some trial and error, I was able to download the PAM sources,
patch, and compile. However, now I'm a little confused as to the
supported syntax of this patch. I.E., what is the LDAP query used to
determine if a user is a member of an NSS group or not? Does it only
support a user's
Public bug reported:
Binary package hint: ifupdown
This is very similar to Bug #123773, but is specific to IPv6 and should
probably be tracked separately.
I don't have an instance ready to retest on, but this apparently worked
on Jaunty (9.04) and broke on Karmic (9.10). I'm actually re-using
Actually, I believe this can now be closed as invalid.
A dependent contributing factor to this issue was the combination of a
network bridge (using brctl) with the VLANs. This worked slightly
differently under several other networking drivers, including Intel and
Broadcom. The way the Realtek
Public bug reported:
Had been using VLANs successfully under Jaunty and now Karmic on a Mini
ITX system with only one network adapter, for use as a LAN router. That
motherboard since died, but had a Marvell 88E8056 network controller
and was using the sky2 driver. The new, replacement
** Attachment added: uname-a.log
http://launchpadlibrarian.net/37121210/uname-a.log
--
VLAN support broken for RTL8111/8168B PCI Express Gigabit Ethernet controller
on Karmic
https://bugs.launchpad.net/bugs/499766
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: version.log
http://launchpadlibrarian.net/37121218/version.log
--
VLAN support broken for RTL8111/8168B PCI Express Gigabit Ethernet controller
on Karmic
https://bugs.launchpad.net/bugs/499766
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: lspci-vnvn.log
http://launchpadlibrarian.net/37121230/lspci-vnvn.log
--
VLAN support broken for RTL8111/8168B PCI Express Gigabit Ethernet controller
on Karmic
https://bugs.launchpad.net/bugs/499766
You received this bug notification because you are a member of Ubuntu
** Tags added: hw-specific network r8168 r8169 realtek vlan
--
VLAN support broken for RTL8111/8168B PCI Express Gigabit Ethernet controller
on Karmic
https://bugs.launchpad.net/bugs/499766
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same hardware is working with a fresh installation of 32-bit / i386
Karmic, and with the default r8169 driver. Will re-try with the amd64
version, which will determine if it is either a 32/64-bit issue, or if
something is corrupt in my configuration on the original installation.
--
VLAN support
Also works with 64-bit reinstall.
--
VLAN support broken for RTL8111/8168B PCI Express Gigabit Ethernet controller
on Karmic
https://bugs.launchpad.net/bugs/499766
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Summary changed:
- VLAN support broken for RTL8111/8168B PCI Express Gigabit Ethernet controller
on Karmic
+ Bridging breaks VLAN support for RTL8111/8168B PCI Express Gigabit Ethernet
controller on Karmic
--
Bridging breaks VLAN support for RTL8111/8168B PCI Express Gigabit Ethernet
Ran across this bug report looking for the same answer.
Doc Nielsen - all udev does is run /lib/udev/hdparm , so it seems that
this could just be re-run as necessary.
flyinggorillaz - At least under Karmic, the rule seems to be a default
rule in /lib/udev/rules.d instead of under
Public bug reported:
This appears to be related to - if not caused by - bug #84580. Full
details are posted at http://blogger.ziesemer.com/2009/09/network-
restart-dhcp-bind-vlan-ubuntu.html .
It seems that the avahi-autoipd script previously included the network
interface ($IFACE) in the
This fix appears to have caused another issue, as reported in bug
#425854.
--
avahi-autoipd causes failure if multiple networking stanzas exist
https://bugs.launchpad.net/bugs/84580
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
45 matches
Mail list logo
