** Description changed:
[Summary]
Please promote bin:libnet-snmp-perl to main. It's the only binary
package built by src:libnet-snmp-perl. The package is a "new" dependency
of bin:amavisd-new which is in main. I say "new" in quotes because is
was already a dependency, but d/control mi
** Description changed:
[Summary]
Please promote bin:libnet-snmp-perl to main. It's the only binary
package built by src:libnet-snmp-perl. The package is a "new" dependency
of bin:amavisd-new which is in main. I say "new" in quotes because is
was already a dependency, but d/control mi
** Description changed:
[Summary]
+ =
Please promote bin:libnet-snmp-perl to main. It's the only binary
package built by src:libnet-snmp-perl. The package is a "new" dependency
- of bin:amavisd-new which is in main. I say "new" in quotes because is
+ of bin:amavisd-new, which is i
** Description changed:
[Summary]
=
Please promote bin:libnet-snmp-perl to main. It's the only binary
package built by src:libnet-snmp-perl. The package is a "new" dependency
of bin:amavisd-new, which is in main. I say "new" in quotes because is
was already a dependency, but
** Description changed:
[Summary]
=
Please promote bin:libnet-snmp-perl to main. It's the only binary
package built by src:libnet-snmp-perl. The package is a "new" dependency
of bin:amavisd-new, which is in main. I say "new" in quotes because is
was already a dependency, but
Hi Roland, you are right, I mixed up the two upstreams, I updated the
MIR bug description.
One thing I got right for sure is the part about the package being
actively and well maintained. Thanks for chiming in!
** Description changed:
[Summary]
=
Please promote bin:libnet-snmp-p
Per server-triage-discussion: this *may( be a case where a "new upstream
microrelease" is acceptable, but the requirements are to be verified:
https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
** Tags removed: server-triage-discuss
--
You received this bug notification bec
The good news is that the test passes when building nss in a Groovy lxd
container, but fails when copying that container (lxc copy), upgrading
the copy to Hirsute and rebuilding there, so I have good pair of
containers to do the "bisect" on.
--
You received this bug notification because you are a
Hi Zcien and thanks for this bug report. I can't reproduce the crash. I
tried to setup a Focal arm64 chroot on both Focal and Impish host
systems, always amd64. I tried to:
git clone https://github.com/canonical/cloud-init # just a random one
and it always worked. I setup the chroots with (qem
I tracked the problem down to the LTO optimizations that were enabled by
default in dpkg 1.20.9ubuntu1.
** Changed in: nss (Ubuntu)
Status: New => Triaged
** Tags added: lto
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Bug watch added: Mozilla Bugzilla #1721995
https://bugzilla.mozilla.org/show_bug.cgi?id=1721995
** Also affects: nss via
https://bugzilla.mozilla.org/show_bug.cgi?id=1721995
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of U
According to the pmdk upstream git repository the two commits identified
as fixing this bug have been released in version 1.11.0:
https://github.com/pmem/pmdk/commit/652659830
https://github.com/pmem/pmdk/commit/e672c09d9
which is now in Impish, so I'm going to mark the Impish task as Fix
Release
All of the above still applies to nss 3.68-1, for which I'm preparing a
merge right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931104
Title:
Test of dogtag-pki is failing on s390x vs the ns
MP for a merge from Debian which also disabled LTO via
DEB_BUILD_MAINT_OPTIONS=optimize=-lto:
https://code.launchpad.net/~paride/ubuntu/+source/nss/+git/nss/+merge/406163
** Summary changed:
- Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
+ Test of dogtag-pki is fail
** Changed in: pmdk (Ubuntu Hirsute)
Status: New => In Progress
** Summary changed:
- Include powerpc port upstream fixes to librpmem 1.10 on pmdk package
+ [SRU] Include powerpc port upstream fixes to librpmem 1.10 on pmdk package
--
You received this bug notification because you are a
I am setting up a PPA for preliminary testing before the actual upload.
Unfortunately the package build queue for ppc64el is very long at the
moment; I'll share a link to the PPA as soon as the package is ready.
** Description changed:
+ [Impact]
+
+ On ppc64el the librpmem checks for RPMEM_RAW_
Fix Released in version 0.32-17-g8f3d478f-0ubuntu1.
** Changed in: cloud-utils (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898534
Title:
Packaging
An update on this. Now that at is in universe we can safely make it a
sync from Debian. There are currently three changes in the Ubuntu delta:
(1) Suggest an MTA rather than Recommending one.
This can be dropped, and dropping it will fix this very bug.
(2) d/patches: add 03-do-not-drop-seconds
Fix Released upstream by commit [1] and in Ubuntu in version
21.2-43-g184c836a-0ubuntu1. Not auto-marked Fix Released as the [1]
commit message didn't mention the LP bug, so our tooling couldn't add it
to the generated d/changelog.
[1] https://github.com/canonical/cloud-
init/commit/e753141fc7844e
Hi, so here is the PPA with amd64 and s390x packages including the fix:
https://launchpad.net/~paride/+archive/ubuntu/pmdk-lp1931063
I'll work towards uploading it to -proposed for the formal
SRU/verification process, however early feedback on the packages will
help and speed things up. @lamm or
** Bug watch added: Debian Bug tracker #991562
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991562
** Also affects: nss via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991562
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
Hi Robie, thanks for opening this bug!
We discussed covering the "cloud-init installed but disabled" case
yesterday at standup, and it would be indeed good to cover it. The
question we also discussed how the failure mode we hit compares to any
of the other commands/tools called during postinst (or
Hello Chris and sorry for not replying to this bug report back when it
was filed. As of today it's an "old bug": none of the releases which
were supported in 2015 is supported today. Should anybody be hitting an
issue that fits with the description of this bug, my suggestion is to
file a new bug re
Thanks @lamm for testing. Just to be sure: is log excerpt you just
pasted a new issue which is not present in the version currently in
Hirsute? In other words, does it look like a regression introduced by
the patches which are included in the PPA package?
--
You received this bug notification bec
I tried reproducing the issue by recompiling the source package from my
PPA and from the current tip of pmdk git on an up-to-date Hirsute
container running on:
$ arch
ppc64le
$ uname -a
Linux paride-h 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:17:52 UTC 2021
ppc64le ppc64le ppc64le GNU/Lin
Hi, now as [1] landed if I don't go wrong we'll have to:
- Wait for livecd-rootfs 2.664.25 to be accepted and installed
in the Focal archive.
- Wait for new ISOs to be built and check from the cd-build-log [2]
which livecd build was used.
- Check that livecd build log at [3] actually uses live
Thanks, I'll follow the steps you provided and see if I can reproduce
the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931063
Title:
[SRU] Include powerpc port upstream fixes to librpmem 1.
Hello and thanks for the additional information.
I tried to reproduce the issue but with no success. I could observe the
"window size dance" you described by doing a detach/resize/resize-
back/attach, but I can't tell if it could be related to tmux dropping
out from copy mode.
An interesting data
Hello Luke,
Did you perhaps try the same setup on Ubuntu Xenial or Focal? If the
behavior of Dovecot changed between releases then we'd have a action to
take on the Ubuntu side: look for the change that introduced (or fixed)
the problem in the past versions of the dovecot package and evaluate the
This is causing LXD VMs (Focal, possibly others) to boot in "degraded"
state, see [1]. The underlying cause is:
root@paride-f-delme:~# systemctl status systemd-sysctl.service
● systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static;
Public bug reported:
snapd can't be purged when there are snaps installed, it fails with with
error:
rm: cannot remove '/snap': Device or resource busy
Steps to reproduce on Hirsute (but also affects Focal, Groovy):
lxc launch ubuntu-daily:hirsute purgefail ; \
sleep 5 ; \
lxc exec
** Changed in: smartmontools (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878264
Title:
nvme smart error count email after upgrading to 20.04
To manage no
** Bug watch added: OpenSSH Portable Bugzilla #3229
https://bugzilla.mindrot.org/show_bug.cgi?id=3229
** Also affects: openssh via
https://bugzilla.mindrot.org/show_bug.cgi?id=3229
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Hello Bert and thanks for this bug report. I could easily reproduce the
issue you described, but I think it would best be fixed upstream rather
than with an Ubuntu specific patch. I filed an upstream bug report [1]
and linked it to this one.
Given that triggering this bug requires a very odd setti
Hello Nissan and thanks for this bug report. Mysql is failing to start
because with error:
[ERROR] [MY-77] [Server] /usr/sbin/mysqld: Error while setting value
'ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
to 'sql_mode'.
which is caused by this (non-default) setting
Public bug reported:
The multipathd daemon is not started in containers, as multipath-
tools.service sets:
ConditionVirtualization=!container
but this doesn't prevent it from running on VMs, including those started
by using cloud images. I don't think enabling multipathd in VMs makes
much sens
Hi and thanks for chiming in.
I probably underestimated how often multipath is used in VMs, but I
still think that the vast majority of the cloud instances out there have
no use for it. However I see your point, what we need is to enable
socket based activation for multipathd, as Rafael proposed.
Hi Klaus,
I think the culprit is the misconfigured `search .` domain in
/etc/resolv.conf. However that's not a Docker (image) default: it's just
inherited by the host system. Can you please verify this is the case,
try fixing it in the host system and try the postfix install in docker
once again?
** Changed in: at (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1464051
Title:
at does not respect the [.ss] portion of the
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906970
Title:
dpkg hook hostname error
To man
Hi Florian, I set the Importance of this bug report to Low, as the issue
is cosmetic.
Ideally this should be fixed upstream: this way the fix will be picked
up by Debian/Ubuntu and other distributions without the added
maintenance need of carrying an Ubuntu-specific delta.
Would you consider forw
Public bug reported:
dh_strip in debhelper 13.3ubuntu3 (currently in hirsute-proposed) fails
with error:
sh: 1: Syntax error: "(" unexpected
dh_strip: error: lto-no-text-in-archive:
debian/libfoo3-dev/usr/lib/s390x-linux-gnu/libfoo.a
dh_strip: error: Aborting due to earlier error
The diff [1] w
Random build log showing the failure:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-hirsute/hirsute/s390x/d/dh-ada-
library/20201218_035409_93407@/log.gz
** Tags added: update-excuse
--
You received this bug notification because you are a
It seems that we're hitting this issue again with the subiquity
installer. The installer fails at the "installing kernel" stage, when
zipl is called. These are the last lines of the installer log
(retrieving the full log is not trivial because of LP: #1823797):
Setting up linux-image-5.0.0-8-gene
Hello Stefan,
So you replaced the check_nrpe binary *only*, without downgrading the
whole package and (what I'm mostly interested in) without downgrading
openssl?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Thanks for your report. We will have to ensure php-pear >=1.4.2 is in
before php8, and this will likely happen in Ubuntu 19.10.
For existing Ubuntu releases the deprecation warning is correct but we
think it is not a problem for now, as it has been there since php 7.2.0
(i.e. since Ubuntu 18.04).
Thanks Andrew for taking the time to file this bug report. The answer
here is that `cloud-init clean` is not meant to clean /etc/machine-id,
as it only cleans files that cloud-init itself generated or more in
general files that cloud-init fully owns. The machine-id is generated by
systemd as part o
This is causing the ubuntu-focal-live-server-amd64-smoke-snap ISO
testing job to fail: it timeouts as snapd is never seeded.
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
This is happening on: arm64, ppc64el, arm64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864191
Title:
focal-server d-i image doesn't detect network hardware
To manage notifications about this b
** Attachment added:
"Screenshot_utah-93017-focal-server-amd64_2020-02-26_16:22:31.png"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1864191/+attachment/5331256/+files/Screenshot_utah-93017-focal-server-amd64_2020-02-26_16%3A22%3A31.png
--
You received this bug notificatio
Hi,
I tried the described scenario a few times from both Eoan and Focal
hosts and always ended up with a working keyboard. FWIW, while doing ISO
testing I often ran installations of Ubuntu *server* on Eoan and now I
do on Focal, and never experienced the issue.
I do not doubt the report is valid,
Hello and thank you for taking the time to file this bug report.
According to the bug description you are running Ubuntu 14.04 on your
samba server machine. This release reached its end of life on April 30,
2019 and it is not supported anymore. Is it possible for you to check if
the same problem ha
Hello Kalle,
Thanks for filing this bug report. The version of gpsd shipped with
Focal has an informative comment in /lib/systemd/system/gpsd.socket:
[Socket]
ListenStream=/var/run/gpsd.sock
ListenStream=[::1]:2947
ListenStream=127.0.0.1:2947
# To allow gpsd remote access, start gpsd with the -G
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864992
Title:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file()
After some digging with Ryan and after trying with different kernel
versions the problem seems due to a change in the kernel package. We
didn't figure out which change in particular is causing the error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331658/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18649
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331660/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331655/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864992
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331654/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
apport information
** Tags added: apport-collected focal uec-images
** Description changed:
During a Focal install from the ISO image several errors like:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not
open builtin file '/lib/modules/5.4.0-14-generic/modules.bui
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331657/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864992
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331656/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864992
Title:
depm
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331659/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864992
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331664/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864992
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331663/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864992
Title:
de
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331661/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/186
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1864992/+attachment/5331662/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864992
** 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/1864992
Title:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819977
Title:
razor2 had unknown error during get_server_info
To manage notifications about this bug go to:
htt
Thank you for your report.
This looks like a local configuration problem, rather than a bug in Ubuntu.
You can find pointers to get help for this sort of prob
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
If indeed this is a local configuration problem,
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
If indeed this is a local configuration problem,
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821935
Title:
Samba panic or segfault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821927
Title:
Systemd do not respawn sssd on failure
To manage notifications about this bug go to:
https://bugs.l
Hey Ralph and others, thanks for following-up and getting to the bottom
of this.
It is quite clear that razor2's diagnostic messages could and should be
improved: the effort you put into this do show this pretty well. However we
believe that this request belongs to the upstream project, and not
Thanks Christian for looking into it. The next time it happens I'll try
to gather some more context and follow up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822096
Title:
libvirt hangs after ut
Sure, I'll try and report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822096
Title:
libvirt hangs after utah workload is aborted
To manage notifications about this bug go to:
https://bugs.
I've been able to reproduce the hang with libvirt-* installed from the
stein-staging PPA. Once again it seems that having an open console to
the VM when UTAH is interrupted is a relevant factor to reproduce the
problem.
I'll now try to take everything from the PPA and try again.
--
You received
It is reproducible even with all the packages grabbed from the stein
PPA.
Another thing I observe is that if UTAH is killed very early in the
installation process (e.g. during the network configuration stage) it
doesn't hang. Killing it later in the process, when block devices are
already involved
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821927
Title:
Systemd do not respawn sssd on failure
To manage notifications about this bug go to:
https://bugs
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821935
Title:
Samba panic or segfault
To manage notifications about this bug go to:
https://bugs.launchpad.net/
The analysis in the Debian bug fully applies to the Ubuntu package too.
The bug makes the package unusable in disco.
** Changed in: ublock-origin (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
When I file bugs sometimes my cat barks.
** Affects: paride-test-project
Importance: Low
Status: New
** Affects: paride-test-project/trunk
Importance: Low
Status: New
** Tags: domestic-animals
** Changed in: paride-test-project
Importance: U
After adding some debugging messages to vm.py I can confirm the hang
happens exactly when vm.undefine() is called at vm.py:445 [1]. But
there's more: adding a debugging printout right before vm.undefine()
prevents the hang from happening, confirming the idea you had since the
beginning that the und
Hello Claudio,
Is your system otherwise stable, or did you notice anything else
crashing in a similar way? You could try to search your system logs for
segmentation faults or other unexpected crashes. This is useful
information to understand if the problem is actually with apache2 or
with some oth
FTR: I couldn't find an upstream bug for this.
** Changed in: haproxy (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: haproxy (Ubuntu Disco)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Hello Malte,
I tried to reproduce the behavior you describe using the haproxy.cfg you
provided, but without success. I have some questions that may help us
getting in sync with what are observing.
1. Your haproxy.cfg doesn't work in Bionic and Eoan because haproxy complains
that the following t
Hello Henning, thanks for your report. I can't reproduce the issue using
Eoan, the same version of tmux and the same architecture. Is this
something that happened one-off, or does it happen often/always on your
system?
Since there isn't enough information in your report to differentiate
between a
The patch looks good for upstream inclusion, but if this has to be fixed
in the packaging branch wouldn't skipping pep8's newly introduced E117
be more appropriate? Skip to be kept until the proper fix lands
upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Just as another data point, I couldn't reproduce either.
Eoan host and Eoan guest, on an amd64 laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846782
Title:
Frequent crashes in multipass VMs
** Changed in: curtin (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845611
Title:
Install fails on ppc64el (unrecognized partition table: 'mac')
The released fix does not appear to fully address the problem:
https://github.com/lxc/lxd/issues/4656#issuecomment-542630903
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779156
Title:
lxc 'delete
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861316
Title:
ubuntu 20.04: libnss-winbind:386 should remain
To manage notifications about this bug go to:
https:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate between a
local configuration problem and a bug in Ubuntu, I'm marking this bug as
Incomplete. We'd be grateful if you would then provide a mor
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861316
Title:
ubuntu 20.04: libnss-winbind:386 should remain
To manage notifications about this bug go to:
http
nut 2.7.4-11ubuntu3 is currently in focal-proposed, so this is *almost*
Fix Released. I'm setting this bug status to Triaged, to be changed to
Fix Released once nut migrates.
** Changed in: nut (Ubuntu)
Status: Expired => Triaged
--
You received this bug notification because you are a mem
Thanks Andreas for this report. Apparently the same problem happens in
Eoan too. The minimal steps to reproduce are:
1. start a fresh LXD container
2. apt update
3. apt install apache2 libaprutil1-dbd-mysql
4. a2enmod authn_dbd (also enables the dbd module)
5. systemctl restart apache2
6. curl loc
Public bug reported:
re2c 1.3-1, currently in focal-proposed, fails the autopkgtests on i386.
Failed test run log:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/i386/r/re2c/20200115_041336_7e788@/log.gz
** Affects: re2c (Ubuntu
What I imagine is that the bug submitter did want to configure a public
MTA, so he chose the "Internet site" debconf answer (the "right" answer
for his use case), and not "Local only". This led to a nonfunctional
setup, e.g. because he has ldap users, and the debconf setup of Postfix
supports only
** Bug watch added: github.com/intel/ipmctl/issues #123
https://github.com/intel/ipmctl/issues/123
** Also affects: libsafec via
https://github.com/intel/ipmctl/issues/123
Importance: Unknown
Status: Unknown
** No longer affects: libsafec
--
You received this bug notification be
101 - 200 of 1596 matches
Mail list logo
