Affected, too. When can we expect the patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863697
Title:
not compatible with python3.8 on focal
To manage notifications about this bug go to:
https:
Can confirm, rolled back my repository from one week ago, worked fine
back then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867502
Title:
Netboot Loading libc6-udeb failed for unknown reasons (f
I guess every sysadmin installing an agent-based configuration
management system via di will experience this problem, too. Funny how
there was no progress on this in half a year.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Easy workaround which does not require another apt-setup.udeb:
d-i preseed/late_commandstring \
in-target wget -q -O /etc/apt/trusted.gpg.d/bla.asc
http://bla.de/bla.asc ; \
in-target sed -i '/keyword to uncomment specific line in file/s/^# *//'
/etc/apt/sources.list ; \
This also affects salt-ssh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797895
Title:
salt-minion won't start with openssl 1.1.1
To manage notifications about this bug go to:
https://bugs.launch
The 4.4.0-136 from xenial-proposed seem to be working.
When will this make its way to xenial-updates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789653
Title:
regression with EXT4 file systems
Can anyone follow up on this?
I am ready to provide specific logs and try alternative
methods/workarounds on demand.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963
Title:
Sporadic problems w
*** This bug is a duplicate of bug 1759920 ***
https://bugs.launchpad.net/bugs/1759920
Same problem with ubuntu 17.10 and Kernel 4.13.0-37 and 4.13.0-38. On
the latest 4.16.1 mainline-kernel the problem does not exist.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
The current HAProxy 1.8.8 supplied with Ubuntu Bionic and Disco contains
a bug when using the server-template functionality for generating
upstreams in combination with the check-sni setting.
The bug was fixed in upstream 1.8.17:
https://git.haproxy.org/?p=haproxy-1.8.git;a=c
Set up HAProxy with the attached configuration. The server-template
directive will generate 3 upstreams based on the DNS-answers for
letsencrypt.status.io. This is basic HAProxy DNS-service-discovery.
If you now check back with the stats socket or the webinterface, you
will notice that while the f
Public bug reported:
Recently I found that in distributions <=18.04 libcurl is built without
libssh2 and therefore does not support the sftp/scp protocols.
I am not sure if this is a bug, but maybe this should be added per
default as its the case on 19.10 for example.
** Affects: curl (Ubuntu)
Public bug reported:
This bug is already solved upstream
(https://sourceware.org/bugzilla/show_bug.cgi?id=20338) in 2.32 and has
to be backported.
It indirectly causes systemd-sysusers on 20.04/focal to fail
(https://github.com/systemd/systemd/issues/6512).
** Affects: glibc
Importance: Unk
This was created 20 days ago. When can I expect somebody to look into
it?
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919468
Ti
Hello Seth,
unfortunately, this is incorrect.
HTTP/1.1 defines the "close" connection option for the sender to
signal that the connection will be closed after completion of the
response.
https://tools.ietf.org/html/rfc2616#section-14.10
But the server with Ubuntus HAProxy 2.0.13 will n
This was fixed for me by patching the latest firmware on the GBICs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963
Title:
Sporadic problems with X710 (i40e) and bonding where one interface is
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963
Title:
Sporadic problems with X710 (i40e) and bonding where one interface is
shown as "state DOWN" a
I tested and can reproduce the problem with this combination:
Ubuntu 16.04, kernel 5.0.0-05.201903032031, driver 2.7.6-k, firmware
18.8.9
I set the tag accordingly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Attachment added: "lspci -v"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811963/+attachment/5229570/+files/lspci.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963
Title:
** Attachment added: "version_signature"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811963/+attachment/5229569/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963
T
Public bug reported:
After rebooting the physical server there is a 50/50 chance of all connected
interfaces coming up. This affects Dell EMC R740's and R440's equipped with the
X710 network cards.
As far as I noticed (~20 reboots on different machines), this happens only when
using bonding (in
Unable to serve the logs via apport-collect due to policy restrictions.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811963
Titl
I confirmed this bug as it still affects 7.4.4-1ubuntu2.7 from trusty-
updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380976
Title:
Limiting queue disk space does not work, upgrade needed
Test case
Step 1:
Create a rsyslog-config using gtls:
/etc/rsyslog.d/10-tlstest.conf
Step 2:
To generate the needed ca-, key-, cert-files, follow the guide at
http://www.rsyslog.com/doc/v8-stable/tutorials/tls.html#certificates
Step 3:
Setup a client, which relays logs to the server that was
*** This bug is a security vulnerability ***
Public security bug reported:
There is a new minor/security patch for Dovecot, to mitigate the two DoS
vulnerabilities. The fix should be merged into the supported Ubuntu
version packages.
** Affects: dovecot (Ubuntu)
Importance: Undecided
Ok, I gave it a try. In my case, 24.04 with Ceph 19/Squid I found that
"aa-disable MongoDB_Compass" is perfectly sufficient. The regular
cephadm gather-facts will on the next run immediately work perfectly
fine. In my understanding this is an escaping problem on the ceph side
where "MongoDB Compass
At this point I would like to confirm this bug. Updates are currently
impossible after a fresh install of Kubuntu. This does not apply to the
beta, but also the final version.
I had this problem on both a Thinkpad laptop and a couple Virtualbox
installs (to confirm and reconfirm).
Muon will just
I recently installed the i386 Kubuntu cd on a Laptop and on Virtualbox
(to reproduce) and I can confirm that upgrades for Kubuntu are currently
in a "broken" state, because after install it will prompt users for an
upgrade, that will stall without any error message. I guess it depends
if you instal
27 matches
Mail list logo
