[Bug 1923237] Re: FTBFS in multiple Ubuntu series

** Also affects: nomad (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: Groovy = nomad/0.10.5+dfsg1-1ubuntu2 currently FTBFS in Groovy. The following test has been failing: === CONT TestServer_Reload_Vault testing.go:129: timed out

[Bug 1923238] [NEW] FTBFS in multiple Ubuntu series

Public bug reported: Focal = cadvisor/0.27.1+dfsg2-4 currently FTBFS in Focal. A build dependency seems to be missing: src/github.com/google/cadvisor/container/common/inotify_watcher.go:20:2: cannot find package "golang.org/x/exp/inotify" in any of:

[Bug 1923239] [NEW] FTBFS in Bionic

Public bug reported: golang-github-docker-libnetwork/0.8.0-dev.2+git20170202.599.45b4086-3 currently FTBFS in Bionic. The following error is reported during build time: github.com/docker/libnetwork # github.com/docker/libnetwork src/github.com/docker/libnetwork/controller.go:1096:69: undefined:

[Bug 1923237] Re: FTBFS in multiple Ubuntu series

** Summary changed: - FTBFS + FTBFS in multiple Ubuntu series ** Also affects: nomad (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: + Groovy + = + nomad/0.10.5+dfsg1-1ubuntu2 currently FTBFS in Groovy. The following test has been failing: ===

[Bug 1923237] [NEW] FTBFS

Public bug reported: nomad/0.10.5+dfsg1-1ubuntu2 currently FTBFS in Groovy. The following test has been failing: === CONT TestServer_Reload_Vault testing.go:129: timed out while shutting down server --- FAIL: TestServer_Reload_Vault (60.08s) FAIL FAILgithub.com/hashicorp/nomad/nomad

[Bug 1921011] Re: Fix build against new runc version

The test plan indicates that the build time tests and DEP-8 tests should pass. - Both packages built fine on LP. - libpod DEP-8 test is passing but the golang-github-containers-buildah DEP-8 test is failing for a while so I'd ask to ignore it. golang-github-containers-buildah autopkgtest

[Bug 1919322] Re: Backport the container stack in Hirsute

I have checked the reverse build dependencies and I noticed the following FTBFS due to the new docker.io version: - golang-github-fsouza-go-dockerclient (bionic) Other reverse build dependencies are failing to build but it is not because of the container stack update, they were failing already

[Bug 1923108] Re: FTBFS against docker 20.10

Package uploaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923108 Title: FTBFS against docker 20.10 To manage notifications about this bug go to:

[Bug 1923108] Re: FTBFS against docker 20.10

Thanks for the review Sergio! I indeed forgot the add references to the LP bug, it is done now. Regarding the DEP-8 tests you are right, there is no definition for them. I'll update the bug description to add the upstream tests executed during build time instead of DEP-8 tests, I think we do not

[Bug 1923108] Re: FTBFS against docker 20.10

** Description changed: [Impact] The version in Bionic FTBFS against docker 20.10 currently in bionic- - proposed. This would be consider a regression. + proposed. This would be considered a regression. [Test Plan] DEP-8 tests passing. [Where problems could occur] There

[Bug 1923108] Re: FTBFS against docker 20.10

The attached patch fixes the FTBFS in bionic (with bionic-proposed enabled). I uploaded this packages to this PPA to confirm that: https://launchpad.net/~lucaskanashiro/+archive/ubuntu/buildah-and-libpod ** Attachment added: "debdiff"

[Bug 1923108] [NEW] FTBFS against docker 20.10

Public bug reported: [Impact] The version in Bionic FTBFS against docker 20.10 currently in bionic- proposed. This would be considered a regression. [Test Plan] DEP-8 tests passing. [Where problems could occur] There could be any breakage related to the move from Go 1.10 to 1.13. Moreover,

[Bug 1916485] Re: test -x fails inside shell scripts in containers

Sorry, I forgot to update the tags. Nothing is missing in the runc verification, we can release it. ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu

[Bug 1889070] Re: [SRU] Add LPAR fence agent to Pacemaker (fence-agents)

Hi "bw...@de.ibm.com", could you perform the same tests you did previously but now using the fence-agents package from focal-proposed instead of my PPA? You can check the "Test plan" section in the bug description but it is basically what you already did. This is part of the SRU process and we

[Bug 1921011] Re: Fix build against new runc version

Packages uploaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921011 Title: Fix build against new runc version To manage notifications about this bug go to:

[Bug 1921011] Re: Fix build against new runc version

Both packages built fine in this PPA: https://launchpad.net/~lucaskanashiro/+archive/ubuntu/buildah-and- libpod/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921011 Title: Fix build

[Bug 1921011] Re: Fix build against new runc version

The libpod package FTBFS because of the new version of the docker.io package in groovy-proposed. The attached debdiff fixes this issue. ** Patch added: "libpod.debdiff" https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/1921011/+attachment/5485291/+files/libpod.debdiff -- You received

[Bug 1921011] Re: Fix build against new runc version

The golang-github-containers-buildah package FTBFS because of the new version of the docker.io package in groovy-proposed. The attached debdiff fixes this issue. ** Patch added: "golang-github-containers-buildah.debdiff"

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

The test plan says the upstream test suite should be executed to catch any regression. This was done during the package build process and it succeeded. Therefore, I am considering the validation as done for this SRU. ** Tags removed: verification-needed verification-needed-bionic

[Bug 1890491] Re: A pacemaker node fails monitor (probe) and stop /start operations on a resource because it returns "rc=189

Sorry for taking too long to get to this bug. I have some comments about the proposed debdiff: 1- The version needs to be updated to 1.1.18-0ubuntu1.4. The .3 version was already released to bionic-updates. 2- The patches need some DEP-3 headers. I see you are just backporting the upstream

[Bug 1889070] Re: [20.10 FEAT] Add LPAR fence agent to Pacemaker (fence-agents)

** Description changed: + [Impact] + + fence-agents does not support fencing IBMz LPAR. This is a key feature + to support Corosync/Pacemaker clusters in IBM Cloud. We can consider + this as hardware enablement. + + [Test Plan] + + Install the fence-agents package (in Bionic do not forget to

[Bug 1889070] Re: [20.10 FEAT] Add LPAR fence agent to Pacemaker (fence-agents)

Thanks for testing the packages "bw...@de.ibm.com", appreciated! We will need to double-check them when the SRU team accepts them into the proposed pocket. For now, we have enough testing :) Regarding the python-requests package: it is already a suggested dependency in Bionic. In Focal you did

[Bug 1916485] Re: test -x fails inside shell scripts in containers

To verify runc I am launching a docker container and calling "test -x" like was done for systemd. Groovy == ubuntu@docker-groovy:~$ cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10"

[Bug 1919322] Re: Backport the container stack in Hirsute

Verification - Bionic With all the components accepted in bionic-proposed I was able to run the tests needed with them which is basically autopkgtest. All of the DEP-8 tests are successfully passing (I am installing the 3 packages from bionic-proposed in the testbed): [runc] autopkgtest

[Bug 1919322] Re: Backport the container stack in Hirsute

Verification - Focal With all the components accepted in focal-proposed I was able to run the tests needed with them which is basically autopkgtest. All of the DEP-8 tests are successfully passing (I am installing the 3 packages from focal-proposed in the testbed): [runc] autopkgtest

[Bug 1874954] Re: [SRU] settings manager window will not shrink horizontally after expanding

** Tags removed: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874954 Title: [SRU] settings manager window will not shrink horizontally after expanding To manage notifications about this

[Bug 1874954] Re: [SRU] settings manager window will not shrink horizontally after expanding

I confirm that the fix worked well on my Xubuntu 20.04 installation and I can resize the settings manager window as expected. ** Tags removed: apport-collected verification-done-groovy verification- needed verification-needed-groovy -- You received this bug notification because you are a member

[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range

I just noticed you asked about this on #ubuntu-release IRC channel and you got the following answer: cjwatson> Rebuilds would be SRUs like any other cjwatson> It's just that the proposed diff would just be the changelog With that in mind, I believe you can proceed with the upload of

[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range

Thanks for the patches Sergio, the changelog entry looks good. However, I am not sure what is the SRU team policy about no-changes rebuild. Can we try to confirm with the SRU team before uploading the proposed patches? Maybe there is no manual upload involved. -- You received this bug

[Bug 1919322] Re: Backport the container stack in Hirsute

Verification - Groovy Now that all the components were accepted in groovy-proposed I was able to run the tests needed with them which is basically autopkgtest. All of the DEP-8 tests are successfully passing (I am installing the 3 packages from groovy-proposed in the testbed): [runc]

[Bug 1921011] Re: Fix build against new runc version

Thanks for helping with the investigation and the review Sergio! The packages were already uploaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921011 Title: Fix build against new runc version

[Bug 1921011] Re: Fix build against new runc version

** Attachment added: "libpod_debdiff" https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+attachment/5480328/+files/libpod_debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1921011] Re: Fix build against new runc version

** Attachment added: "golang-github-containers-buildah_debdiff" https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+attachment/5480327/+files/golang-github-containers-buildah_debdiff -- You received this bug notification because you are a member of Ubuntu

[Bug 1919322] Re: Backport the container stack in Hirsute

libpod and golang-github-containers-buildah also need a SRU targeting Groovy to work fine with the new runc version. The status can be tracked here: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers- buildah/+bug/1921011 -- You received this bug notification because you are a

[Bug 1921011] [NEW] Fix build against new runc version

Public bug reported: [Impact] runc/1.0.0~rc93-0ubuntu1 in Hirsute is going to be backported to Groovy (already in groovy- proposed) but libpod and golang-github-containers-buildah FTBFS with it (autopkgtest fails as well). Those packages are blocking runc's migration. Both packages, libpod

[Bug 1919322] Re: Backport the container stack in Hirsute

** Description changed: [Impact] In order to follow our policy on keeping the container stack (docker.io, containerd, and runc) up-to-date in our supported releases, let's backport the stack in Hirsute to Groovy, Focal, and Bionic. docker.io version 20.10.2 was introduced in mid

[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net

Thank you for taking the time to file a bug report. None of the mentioned packages create a link to the certificates directory (/etc/ssl/certs), so I believe you made some kind of manual intervention. And IMO this "symlink sensitivity" is an upstream design decision and not a bug, if you believe

[Bug 1919322] Re: Backport the container stack in Hirsute

Filed a bug against upstream golang-github-docker-go-connections: https://github.com/docker/go-connections/issues/83 ** Bug watch added: github.com/docker/go-connections/issues #83 https://github.com/docker/go-connections/issues/83 -- You received this bug notification because you are a

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

Thanks for the review Sergio! I am going to fix my email address in the groovy package and upload all of them. Also fix/improve the bug description. ** Description changed: [Impact] Due to our current policy we keep updating the container stack in all supported releases with new

[Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial

Hi Robie, I just realized that I forgot to change the tag when I posted my test process :( This is the reason why this package is not on the -updates pocket yet, right ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1919322] Re: Backport the container stack in Hirsute

The SRU team brought up to my attention that a couple of changes were made to the containerd service file which worth a mention here. The following lines were added by upstream: +RestartSec=5 +OOMScoreAdjust=-999 They were considered fine by the SRU team. -- You received this bug notification

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

** Attachment added: "debdiff-bionic" https://bugs.launchpad.net/ubuntu/+source/opengcs/+bug/1912691/+attachment/5479208/+files/debdiff-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912691

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

** Attachment added: "debdiff-focal" https://bugs.launchpad.net/ubuntu/+source/opengcs/+bug/1912691/+attachment/5479207/+files/debdiff-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912691

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

** Attachment added: "debdiff-groovy" https://bugs.launchpad.net/ubuntu/+source/opengcs/+bug/1912691/+attachment/5479206/+files/debdiff-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912691

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

I prepared packages for Bionic, Focal and Groovy here in this PPA: https://launchpad.net/~lucaskanashiro/+archive/ubuntu/opengcs autopkgtest is passing in all of them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial

** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915547 Title: Users are prompted by ucf on upgrade from Trusty to

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

** Description changed: + [Impact] + + Due to our current policy we keep updating the container stack in all + supported releases with new upstream versions. runc is part of this + stack, and currently versions of opengcs in Bionic, Focal and Groovy do + not support runc / 1.0.0 ~ rc93-0ubuntu1.

[Bug 1912691] Re: autopkgtest failure blocking runc migration

During the runc/1.0.0~rc93-0ubuntu1 backport to Bionic, Focal and Groovy (LP #1919322), this very same issue showed up. Due to that I am marking all those releases as affected as well. Fortunately, opengcs has the same upstream version in all those releases, so the patch applied to Hirsute should

[Bug 1919322] Re: Backport the container stack in Hirsute

golang-github-docker-go-connections FTBFS at the moment in Focal and Groovy because of an issue with one certificate used in the tests. Likely this certificate needs to be regenerated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1919322] Re: Backport the container stack in Hirsute

With the new runc version opengcs needs to be patched in Bionic, Focal and Groovy in the same way it was done in Hirsute, more info on LP #1912691 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop

@seb128 I'm not sure it's upstream. has been around forever and was marked as duplicate of the still open where it appears Mozilla doesn't want to do anything about it. The earliest ancestor

[Bug 1919322] Re: Backport the container stack in Hirsute

** Changed in: runc (Ubuntu Groovy) Status: New => In Progress ** Changed in: runc (Ubuntu Groovy) Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro) ** Changed in: runc (Ubuntu Focal) Status: New => In Progress ** Changed in: runc (Ubuntu Focal)

[Bug 1919322] [NEW] Backport the container stack in Hirsute

Public bug reported: [Impact] In order to follow our policy on keeping the container stack (docker.io, containerd, and runc) up-to-date in our supported releases, let's backport the stack in Hirsute to Groovy, Focal, and Bionic. docker.io version 20.10.2 was introduced in mid January in Hirsute

[Bug 1919249] Re: package libsmbclient:amd64 2:4.11.6+dfsg-0ubuntu1.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

Thank you for taking the time to file a bug report. The logs are not very helpful in this case, the only thing I saw was: dpkg: error processing package libsmbclient:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting

[Bug 1919119] Re: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

Thank you for taking the time to file a bug report. After reading the logs I believe you tried to abort the package installation in the middle of the process, I can't spot anything besides that. You also need to be careful when upgrading to MySQL 8, please take some time to read the upstream

[Bug 1919182] [NEW] [FFe] Import version 1.0-rc93

Public bug reported: This new upstream release contains an important fix to address LP #1916485. runc now has special handling for seccomp profiles to avoid making new syscalls unusable for glibc. Backporting this single fix would be painful because upstream also updated some of the vendorized

[Bug 1917718] Re: Can't auto login after upgrading to 2.3.1-3ubuntu4 on 20.10

Thanks for taking the time to file this bug. While checking the logs I noticed this: Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: Loaded settings from: /usr/lib/realmd/realmd-defaults.conf /usr/lib/realmd/realmd-distro.conf Mar 4 01:49:13 precision-3551-c3x-202002-27718

[Bug 1851232] Re: Laptop does not suspend when using open-iscsi

Thank you for taking the time to file a bug report. I just tried to connect to an iscsi target from my Ubuntu Focal workstation and I was not able to suspend and then wake up my system, as both of you described. Your analyses seems right, the iscsi target might be delaying the whole process. I

[Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

Thank you for taking the time to file a bug report. >From what you described it seems that Network Manager is the one responsible for adding the unexpected routing rule, so this might not affect OpenVPN itself. I quickly tried to reproduce your setup but did not notice the bug there. Could you

[Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial

Thanks for the review Robie, I have tested the package on the proposed pocket by using this script: #!/bin/sh set -x series=trusty name=$series-upgrade multipass delete $name multipass purge multipass launch $series --name $name multipass exec $name -- sudo sh -c "cat

[Bug 1917971] Re: package samba-common (not installed) failed to install/upgrade: installed samba-common package post-installation script subprocess returned error exit status 10

Thank you for taking the time to file a bug report. The attached logs do not help too much, the only info I could extract was dpkg returning the exit code 10. It seems that something is in an inconsistent state in your system but I was not able to spot anything with the provided information.

[Bug 1573192] Re: apparmor prevents using SCSI hostdevs

Thanks for taking the time to file this bug. I am not able to reproduce this bug since I do not have an scsi device to test it. I am subscribing Christian, he might have a better idea on how to address this issue. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial

Thank you for this review Robie, we have now updated the package to only ship two md5sum. The latest version of 50unattended-upgrades of Trusty and Xenial. I have already updated the MR with those changes and I Bryce is reviewing that changes before uploading the new package. -- You received

[Bug 1917766] [NEW] [RM] Do not ship ruby-omniauth-remote-user in Hirsute

Public bug reported: ruby-omniauth-remote-user is blocking ruby-defaults/1:2.7+2 migration because it FTBFS. Related Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959557 I am one of the upstream maintainers and I can confirm this project is quite dead, unmaintained for many

[Bug 1917036] Re: Some of the modules of cloud-init are not working properly (in this case: runcmd)

Also, please provide the userdata that you are using to configure cloud- init too. I forgot to mention that on my last comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917036 Title: Some of

[Bug 1917036] Re: Some of the modules of cloud-init are not working properly (in this case: runcmd)

Hi Kalpesh, thank you for reporting this issue. Can you please provide the cloud-init logs for the instance that is failing ? Those logs would be cloud-init.log and cloud-init-output.log After providing that, you can change the status of this bug to new again. ** Changed in: cloud-init (Ubuntu)

[Bug 1917336] Re: Mailman does not honour MAILMAN_USER on startup

Thank you for taking the time to file a bug report. Checking the mailman package in Ubuntu Focal I see the logrotate file installed by this package contains some postrotate scripts that might be setting back the ownership to list:list. Take a look at /etc/logrotate.d/mailman and try to make the

[Bug 1917280] Re: package libsss-nss-idmap0 2.2.3-3ubuntu0.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

Thank you for taking the time to file a bug report. I set up a Focal LXD container and installed libsss-nss-idmap0 without problems in it. I see you tried to install version 2.2.3-3ubuntu0.2, and now in focal-updates we have 2.2.3-3ubuntu0.4, please try to install this newer version and check if

[Bug 1906307] Re: flaky autopkgtest on arm64

I forwarded this bug to the upstream maintainers: https://github.com/puma/puma/issues/2562 ** Bug watch added: github.com/puma/puma/issues #2562 https://github.com/puma/puma/issues/2562 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1916954] Re: autopkgtest regression on s390x and arm64

I tested the attached debdiff in Canonistack VMs (s390x and arm64) and I got no autopkgtest failure. ** Attachment added: "debdiff" https://bugs.launchpad.net/ubuntu/+source/puma/+bug/1916954/+attachment/5467252/+files/debdiff -- You received this bug notification because you are a member

[Bug 1916954] [NEW] autopkgtest regression on s390x and arm64

Public bug reported: The test is hanging on s390x and arm64 architectures only, blocking its migration and also rails. Below my findings so far. On s390x the TestPlugin#test_plugin is hanging, not sure why that is happening exactly but this test is new (not present in the puma version in

[Bug 1915547] Re: sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial

I will further increase this SRU bug with information that is lacking on from the original bug proposal: [Impact] During an upgrade from trusty to xenial, users will be prompted to make a decision regarding the diff on unattended-upgrades. This is not a good user experience, specially because

[Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

So sad, Asus doesn't care about linux users, that's the reality ... Our only hope is a community developed driver for this feature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title:

[Bug 1916659] [NEW] The default config in Bionic does not work on Azure

Public bug reported: By default the "transport" field is not set in /etc/corosync/corosync.conf which means "udp" is used. However, it does not work in Ubuntu Bionic on Azure for some reason, I thought it could be some issue regarding multicast but I was told it is supported. In order to make it

[Bug 1889070] Re: [20.10 FEAT] Add LPAR fence agent to Pacemaker (fence-agents)

I backported the needed code to support the fence agent to Bionic and Focal here in this PPA: https://launchpad.net/~lucaskanashiro/+archive/ubuntu/ha-stack-ibm The idea would be to SRU those patches and release them to Bionic and Focal, instead of relying only on the PPA with Groovy's full HA

[Bug 1916541] Re: smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade

Thank you for taking the time to file a bug report. I tried to reproduce your bug in a Ubuntu Hirsute container without success. Moreover, I looked for an upstream bug report about any incompatibility with glibc 2.33 but found nothing. Could you please share your postfix config file to help us

[Bug 1915670] Re: iotop 0.6-24-g733f3f8-1 fails with 'UnboundLocalError' on newly installed 20.04 release

Thank you for taking the time to file a bug report. I tried to reproduce the crash you mentioned and I was not able to do it. In a brand new Focal environment I was able to install iotop and call it without any problem. Since there is not enough information in your report to begin triage or to

[Bug 1915747] [NEW] notebook lid open wont awake linux

Public bug reported: If I leave the notebook closed for too much time and open it, it will not wake up and I have to force reboot by pressing power. However if I simply close and open at the same minute it works. This kernel fixes the athk11 wifi, it works now but I think it might be the cause

[Bug 1915547] [NEW] sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial

Public bug reported: == Begin SRU Template == [Impact] When upgrading from trusty to xenial, we are prompted about config changes on 50unattended-upgrades with the following diff: --- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08 19:21:39 +++

[Bug 1915203] Re: Backport AWS agent with IMDSv2 support

PPA with proposed packages: https://launchpad.net/~lucaskanashiro/+archive/ubuntu/ha-stack-aws ** Description changed: + [Impact] + + This update is considered as a hardware enablement feature which will + allow AWS users to make use of the IMDSv2 support recently added to + resource-agents.

[Bug 1915190] Re: Backport the fence_aws support for IMDSv2

Status: New => In Progress ** Changed in: fence-agents (Ubuntu Focal) Status: New => In Progress ** Changed in: fence-agents (Ubuntu Groovy) Status: New => In Progress ** Changed in: fence-agents (Ubuntu Bionic) Assignee: (unassigned) => Lucas Kanashiro (lucas

[Bug 1915203] [NEW] Backport AWS agent with IMDSv2 support

onal layer of defense against network abuses, customers utilizing it may choose to disable IMDSv1. Disabling IMDSv2 today causes fence_aws to fail. ** Affects: resource-agents (Ubuntu) Importance: Undecided Assignee: Lucas Kanashiro (lucaskanashiro) Status: Fix Released

[Bug 1915190] [NEW] Backport the fence_aws support for IMDSv2

Public bug reported: Last year, AWS released "IMDSv2" in an effort to protect customers against some potentially severe information leaks related to accidentally proxying this local data to the network. Details at

[Bug 1914980] Re: package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

Thank you for taking the time to file a bug report. >From the attached logs I can see this: package:mysql-server-8.0:8.0.23-0ubuntu0.20.04.1 Setting up mysql-server-8.0 (8.0.23-0ubuntu0.20.04.1) ... mysqld will log errors to /var/log/mysql/error.log mysqld is running as pid 4837 Error: Unable to

[Bug 1896223] Re: no-quorum-policy=demote and on-fail=demote features for MSSQL servers

FWIW here you can find the proposed package targeting Focal for testing: https://launchpad.net/~lucaskanashiro/+archive/ubuntu/pacemaker-sql- server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1914052] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build

*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 I have the same issue as Alexandre, proceeded with autoupdate and sudednly my PC stopped recognizing my wifi adapter. -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1914101] Re: package clamav-freshclam 0.102.4+dfsg-0ubuntu0.20.04.1 failed to install/upgrade: installed clamav-freshclam package post-removal script subprocess returned error exit status 1

Thanks for taking the time to file a bug and trying to make Ubuntu better. This is what I found in your logs: Removing clamav (0.102.4+dfsg-0ubuntu0.20.04.1) ... Removing clamav-daemon (0.102.4+dfsg-0ubuntu0.20.04.1) ... Removing clamdscan (0.102.4+dfsg-0ubuntu0.20.04.1) ... Removing

[Bug 1914288] Re: Xorg freeze

** Information type changed from Private Security to Private ** Information type changed from Private to Public Security ** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1914288] [NEW] Xorg freeze

Public bug reported: Freezes randomly during usage and always after recovering from suspend mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion:

[Bug 1914280] [NEW] Remove bundler from Hirsute

Public bug reported: Now the binary packages (bundler and ruby-bundler) previously provided by src:bundler are now provided by src:rubygems. Please remove src:bundler and its binary package from Hirsute to allow src:rubygems migration. ** Affects: bundler (Ubuntu) Importance: Undecided

[Bug 1913596] Re: [RM] autopkgtest failure is blocking ruby-faraday{, -middleware} in hirsute-proposed

Right, ruby-puppet-forge migrated to Debian testing yesterday :) hopefully version 3.0.0-1 will work this out. I believe we should also remove vagrant-librarian-puppet since it is reverse dependency of the removed librarian-puppet. -- You received this bug notification because you are a member

[Bug 1913596] Re: autopkgtest failure is blocking ruby-faraday{, -middleware} in hirsute-proposed

r10k has no reverse dependencies in hirsute: $ reverse-depends -b -r hirsute r10k No reverse dependencies found $ reverse-depends -r hirsute r10k No reverse dependencies found librarian-puppet has the following reverse dependency: $ reverse-depends -b -r hirsute librarian-puppet

[Bug 1913596] Re: autopkgtest failure is blocking ruby-faraday{, -middleware} in hirsute-proposed

Please remove the following source packages and associated binary packages from hirsute: * ruby-puppet-forge * r10k * librarian-puppet * vagrant-librarian-puppet ** Summary changed: - autopkgtest failure is blocking ruby-faraday{,-middleware} in hirsute-proposed + [RM] autopkgtest failure is

[Bug 1913596] Re: autopkgtest failure is blocking ruby-faraday{, -middleware} in hirsute-proposed

ruby-puppet-forge has the following reverse dependencies: $ reverse-depends -b -r hirsute ruby-puppet-forge Reverse-Build-Depends * librarian-puppet * r10k $ reverse-depends -r hirsute ruby-puppet-forge Reverse-Depends * librarian-puppet * r10k Packages without architectures listed are

[Bug 1913598] Re: autopkgtest failure is blocking ruby-faraday{, -middleware} in hirsute-proposed

Please remove ruby-diaspora-federation source and binary packages from hirsute. ** Summary changed: - autopkgtest failure is blocking ruby-faraday{,-middleware} in hirsute-proposed + [RM] autopkgtest failure is blocking ruby-faraday{,-middleware} in hirsute-proposed -- You received this bug

[Bug 1913598] Re: autopkgtest failure is blocking ruby-faraday{, -middleware} in hirsute-proposed

Since ruby-diaspora-federation has no reverse dependencies we could follow Debian to unblock other packages: $ reverse-depends -r hirsute ruby-diaspora-federation $ reverse-depends -b -r hirsute ruby-diaspora-federation No reverse dependencies found -- You received this bug notification because

[Bug 1913596] Re: autopkgtest failure is blocking ruby-faraday{, -middleware} in hirsute-proposed

FWIW ruby-puppet-forge was removed from Debian testing to allow migration of ruby-faraday{,-middleware}: https://tracker.debian.org/news/1224756/ruby-puppet-forge-removed-from- testing/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1913598] Re: autopkgtest failure is blocking ruby-faraday{, -middleware} in hirsute-proposed

FWIW ruby-diaspora-federation was removed from Debian testing to allow the migration of ruby-faraday{,-middleware}: https://tracker.debian.org/news/1198071/ruby-diaspora-federation- removed-from-testing/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1913586] Re: autopkgtest failure in Hirsute

Thanks Sergio! I forgot to run update-maintainer indeed :) I was planning to commit this change in the salsa git repo but the maintainer is in the middle of an upstream release bump and I did not want to mix things up until it is done. But I am going to do that once the package in git is in a

[Bug 1913598] [NEW] autopkgtest failure is blocking ruby-faraday{, -middleware} in hirsute-proposed

Public bug reported: The test is failing because upstream does not support yet the newer versions of faraday and faraday_middleware gems. Test log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-hirsute/hirsute/amd64/r/ruby-diaspora-

<    4   5   6   7   8   9   10   11   12   13   >