Hi Ioanna,
please elaborate a bit more as soon as you can :)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/1835818
Title:
snmpd causes autofs mount points to be mounted on system star
Same thing on bionic now.
a) SSL with incorrect name fails as expected:
ubuntu@bionic-ldap-start-tls-1835181:~$ sudo truncate -s 0 /var/log/syslog
ubuntu@bionic-ldap-start-tls-1835181:~$ ldapwhoami -x -H
ldaps://bionic-ldap-start-tls-1835181.lxd
ldap_sasl_bind(SIMPLE): Can't contact LDAP serve
I didn't have TLS_REQCERT set in /etc/ldap/ldap.conf during these tests,
but the manpage says the value "demand" (equal to "hard") is the default
in eoan at least.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to openldap in Ubuntu.
https://b
It seems to be working fine in eoan. I setup a CA and issued a server
certificate, and setup openldap with ssl/start_tls.
The hostname of the container:
ubuntu@eoan-ldap-start-tls-1835181:~$ hostname -f
eoan-ldap-start-tls-1835181.lxd
ubuntu@eoan-ldap-start-tls-1835181:~$ ping -c 1 $(hostname -f)
@mcandre, I think your issue, even though it's also a segfault, is a
different one than this bug from 2014, which was about armhf and was
verified in comment #4 as no longer happening.
Could you please open a separate bug about what you experienced,
including detailed steps to reproduce it? Attach
There are other failures after the ones I pasted. I updated the upstream
bug report with them.
** Summary changed:
- FTBFS: gcc9 stringop-truncation
+ FTBFS: gcc9 stringop-truncation and others
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we c
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.40~cloud0
---
qemu (1:2.5+dfsg-5ubuntu10.40~cloud0) trusty-mitaka; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.5+dfsg-5ubuntu10.40) xenial; urgency=medium
.
* Restore patches that cause
** Bug watch added: Squid Bugzilla #4969
http://bugs.squid-cache.org/show_bug.cgi?id=4969
** Also affects: squid via
http://bugs.squid-cache.org/show_bug.cgi?id=4969
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Serve