@jamesps this applies to Ubuntu Focal 20.04 as described in the manpage.
This seems to me a local configuration issue and not a bug in the
package. Due to that I am marking this bug as Invalid.
** Changed in: openssh (Ubuntu)
Status: New => Invalid
--
You received this bug notification
@family-gan are you saying this is an issue in Ubuntu Impish (21.10)? It
seems to be already fixed in supported releases. Could you share any
steps to reproduce it? If you consider the issue you are facing
different than the one discussed in this bug please consider filing a
separate bug.
--
You
)
Status: Fix Released => In Progress
** Changed in: sbd (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968226
Title:
DEP-
According to the latest changes in the docker.io group SRU exception
approved here:
https://lists.ubuntu.com/archives/ubuntu-release/2022-April/005371.html
now, .0 releases of runc and containerd are eligible for backporting.
Considering that, could we now accept runc into
Public bug reported:
sbd/1.5.1-1build1 is currently blocking pacemaker/2.1.2-1ubuntu3
migration in jammy because the fence-external DEP-8 test is missing a
dependency on fence-agents-base, which contains the stonith:external/sbd
agent.
** Affects: sbd (Ubuntu)
Importance: Undecided
** Also affects: pcs (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- booth/1.0-237-gdd88847-4ubuntu1 is currently blocking
- pacemaker/2.1.2-1ubuntu3 migration in jammy because the pacemaker DEP-8
- test is missing a dependency on resource-agents-extra, which
Public bug reported:
crmsh/4.3.1-1ubuntu1 is currently blocking pacemaker/2.1.2-1ubuntu3
migration in jammy because the pacemaker-basic-resource.sh DEP-8 test is
missing a dependency on resource-agents-extra, which contains the
ocf:heartbeat:IPv6addr resource.
** Affects: crmsh (Ubuntu)
Public bug reported:
booth/1.0-237-gdd88847-4ubuntu1 is currently blocking
pacemaker/2.1.2-1ubuntu3 migration in jammy because the pacemaker DEP-8
test is missing a dependency on resource-agents-extra, which contains
the ocf:heartbeat:Dummy resource.
** Affects: booth (Ubuntu)
Importance:
** Changed in: containerd (Ubuntu)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960449
Title:
Backport container stack in Ja
ang-github-openshift-imagebuilder (Ubuntu Focal)
Status: New => In Progress
** Changed in: golang-github-openshift-imagebuilder (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: golang-github-openshift-imagebuilder (Ubuntu Impish)
St
Build with Golang 1.16
** Patch added: "golang-github-openshift-imagebuilder.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/runc/+bug/1960449/+attachment/5577728/+files/golang-github-openshift-imagebuilder.debdiff
--
You received this bug notification because you are a member of
** Patch added: "Build with Golang 1.16"
https://bugs.launchpad.net/ubuntu/bionic/+source/runc/+bug/1960449/+attachment/5577727/+files/golang-github-fsouza-go-dockerclient.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: block-proposed-focal
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: pacemaker (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
In order to fix the golang-github-fsouza-go-dockerclient/1.6.0-2 and
golang-github-openshift-imagebuilder/1.1.0-2 regressions, we need to
make them build with Golang 1.16 instead of the default in Focal. This
is needed because the DEP-8 test tries to build the code and it uses the
docker.io
We have a PR up fixing this issue:
https://github.com/canonical/ubuntu-advantage-client/pull/2028
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968067
Title:
upgrade_lts_contract.py exception on
*** This bug is a duplicate of bug 1967901 ***
https://bugs.launchpad.net/bugs/1967901
** This bug has been marked a duplicate of bug 1967901
[qxl] Xorg fails to start with "Screen(s) found, but none have a usable
configuration."
--
You received this bug notification because you are a
adding Xorg crash dump
** Attachment added: "Xorg crash dump"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968063/+attachment/5577702/+files/_usr_lib_xorg_Xorg.126.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg-
Server will not start. Either directly via lightdm or via gdm/wayland
selecting Xubuntu session.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu
Backporting the default config change to Focal breaks pacemaker DEP-8
test. The fix for this can be tracked here:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1968039
I created a separate bug to block this update in focal-proposed and
avoid users updating the package because of a
Public bug reported:
[Impact]
After updating corosync to the version proposed here in Focal:
https://bugs.launchpad.net/charm-hacluster/+bug/1874719
pacemaker DEP-8 test fails because it relies in the hardcoded 'node1'
default node name.
[Test Plan]
Run pacemaker DEP-8 test against the
** Description changed:
[Impact]
Users upgrading from Bionic to Focal are getting a different default
- node name, previously it was the hostname and now it is using a
- hardcoded "node1". This issue was already fixed on Impish onward, so now
- only Focal is using the hardcoded "node1"
** Changed in: corosync (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
[SRU] Use the hostname as the node name instead of
** Description changed:
+ [Impact]
+
+ Users upgrading from Bionic to Focal are getting a different default
+ node name, previously it was the hostname and now it is using a
+ hardcoded "node1". This issue was already fixed on Impish onward, so now
+ only Focal is using the hardcoded "node1"
golang-1.16 is waiting in the Bionic NEW queue, and
runc/containerd/docker.io were uploaded targeting Bionic already (runc
and docker.io depend on golang-1.16). So now everything is on SRU team's
hands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: golang-1.16 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: golang-1.16 (Ubuntu Bionic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for the review Bryce. I added some more bits to the changelog to
make it more clear about the needed changes. I also updated the bug
description with your suggestions. The package was already uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
[Impact]
To enable packages that are backported wholesale to all releases of
Ubuntu (i.e. runc and docker.io) to stop depending on what is now a
fairly ancient version of Go (some of them require at least Go 1.16), we
are going to upload 1.16 to bionic (this
ang-1.16 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: golang-1.16 (Ubuntu Focal)
Status: New => Invalid
** Changed in: golang-1.16 (Ubuntu Impish)
Status: New => Invalid
** Changed in: golang-1.16 (Ubuntu Bionic)
Assignee: (unassigned) =>
The attached debdiff backport golang-1.16/1.16.2-0ubuntu1~20.04 from
Focal to Bionic.
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/golang-1.16/+bug/1967425/+attachment/5575870/+files/debdiff
--
You received this bug notification because you are a member of Ubuntu
golang-1.16-go from Focal has Breaks: dh-golang (<< 1.43~) which is
unsatisfiable in Bionic, where we have dh-golang/1.34.2. This made runc
version 1.1.0-0ubuntu1 FTBFS with golang 1.16.
According to the discussion on the commit message
(https://salsa.debian.org/go-
** Also affects: golang-1.16 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: golang-1.16 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
To enable packages that are backported wholesale to all releases of
Ubuntu (i.e. runc and docker.io) to stop depending on what is now a
fairly ancient version of Go (some of them require at least Go 1.16), we
are going to upload 1.16 to bionic (this version is in
ruby-ferret/0.11.8.7-2 in Jammy is behaving well on arm64:
https://autopkgtest.ubuntu.com/packages/ruby-ferret/jammy/arm64
** Changed in: ruby-ferret (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We have performed the test for release 27.7 using the package that is
proposed
** Attachment added: "ua-test-results-27.7.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1964028/+attachment/5573894/+files/ua-test-results-27.7.tar.xz
** Tags removed:
Since version 2018091102 dns-root-data has a DEP-8 test called baseline.
** Changed in: dns-root-data (Ubuntu)
Status: New => 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/1677829
Thanks for confirming that William. I already uploaded the fix.
** Changed in: containerd (Ubuntu)
Status: Triaged => 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/1965157
Public bug reported:
1) Description: Ubuntu 20.04.3 LTS
Release: 20.04
2) N: Unable to locate package pkgname
3) My current issue is the external display not being detected, but I
don't know how it will behave, given the different issues, at different
boots, being that the
This bug was fixed in 3.0.2-7ubuntu1 which landed together with
3.0.2-7ubuntu2 (security update) 2 days ago. AFAICS the build failures
were triggered 4 days ago. FWIW I built ruby-kramdown (mentioned in the
bug) locally and it worked just fine.
** Changed in: ruby3.0 (Ubuntu)
Status: New
Yep, the structure of go.mod and some other files need to be changed to
support Go 1.17. I updated the needed files running the following
commands:
$ go mod tidy -go=1.17
$ go mod vendor
With that, I created the attached debdiff which fixes the FTBFS. Could
you confirm if everything is fine with
Still no updates in the upstream bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930393
Title:
any local user can shut clamd down via control socket
To manage notifications about this bug go
The agents in fence-agents-base did not require any change. And I was
not able to find any occurrence of this type of issue with a simple grep
command in the other agents inside the extra package. If someone find
any issue please file another bug describing that.
** Changed in: fence-agents
Hi William,
Thanks for working on it. I took a look at what upstream is doing
regarding that and I believe it is OK to remove the empty module, but
I'll suggest an extra change based on the upstream discussions. We
should replace "go 1.16" in go.mod to "go 1.17" to have this feature
which should
This is the upstream issue:
https://github.com/ClusterLabs/resource-agents/issues/699
** Bug watch added: github.com/ClusterLabs/resource-agents/issues #699
https://github.com/ClusterLabs/resource-agents/issues/699
--
You received this bug notification because you are a member of Ubuntu
The testing and bisecting (suggested by Rafael) still need to be done.
This is in our backlog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900374
Title:
fence_aws in Focal and Bionic (LP:
Those are the proposed changes:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/fence-
agents/+git/fence-agents/+merge/417044
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965312
Title:
** Changed in: corosync (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874719
Title:
[SRU] Use the hostname as the node name instead of hardcoded
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965312
Title:
[FFe] Add some agents to the -base binary package
To manage notifications about this bug go to:
Just approved the PR robert-ancell
Also, I understand the need to use status.json directly. In the future
we can better discuss on how we can extend `ua status --format json` to
the Desktop needs to simplify that process.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I'd like to move the following agent from the fence-agents-extra binary
package to the fence-agents-base package:
- fence_sbd
- fence_ipmilan
+ fence_idrac
+ fence_ilo3
+ fence_ilo4
+ fence_ilo5
+ fence_imm
+ fence_ipmilanplus
In practice, fence_ipmilan and all
Filed a bug upstream: https://github.com/nov/json-jwt/issues/100
** Bug watch added: github.com/nov/json-jwt/issues #100
https://github.com/nov/json-jwt/issues/100
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually, this is an issue with ruby-json-jwt, and not ruby-openid-
connect itself which only depends on it.
** Also affects: ruby-json-jwt (Ubuntu)
Importance: Undecided
Status: New
** Tags added: transition-openssl3-jj update-excuse
--
You received this bug notification because you
Public bug reported:
ruby-openid-connect/1.2.0-2 do not support OpenSSL 3 which lead us to
the following test failures during build/autopkgtest time:
Failures:
1) OpenIDConnect::Discovery::Provider::Config::Response#public_keys
Failure/Error: instance.public_keys
ntu Groovy)
Status: Triaged => Won't Fix
** Changed in: corosync (Ubuntu Hirsute)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
** Changed in: corosync (Ubuntu Groovy)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
--
You received this bug notif
Public bug reported:
Currently, it seems that software-properties is incorrectly assuming
that both ESM and Livepatch services can be enabled in a Jammy machine.
Those services are not yet available in Jammy and we are attaching an
image showing that the Desktop message is that we had an error
** Changed in: ruby3.0 (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/1964813
Title:
Script to generate Provides is broken
To manage
With the version in archive this is the summary of the execution of the
test suite during the build:
1494 runs, 3679 assertions, 28 failures, 395 errors, 0 skips
Applying the WIP patch (attached) the summary is:
1494 runs, 3964 assertions, 16 failures, 332 errors, 0 skips
** Patch added: "WIP
Thanks for the review Athos. I fixed the indentation and uploaded the
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964813
Title:
Script to generate Provides is broken
To manage
The attached debdiff fixes this issue. The changes are in
ruby3.0/3.0.3-1 in Debian:
https://salsa.debian.org/ruby-
team/ruby/-/commit/e6d192830071320905729c8560dbcb7fc5a99746
** Attachment added: "debdiff"
Public bug reported:
The script to generate the content of the Provides field of libruby3.0
(debian/genprovides) is not finding all the gems shipped in ruby3.0.
** Affects: ruby3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
ruby2.7 was removed from Jammy and ruby-defaults does not pull it in
anymore.
** Changed in: ruby3.0 (Ubuntu)
Status: New => 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/1960185
I also filed this issue which involves some ruby-net-ssh test failures:
https://github.com/ruby/openssl/issues/500
** Bug watch added: github.com/ruby/openssl/issues #500
https://github.com/ruby/openssl/issues/500
** Changed in: vagrant (Ubuntu)
Status: New => Triaged
--
You
** Also affects: ruby-bcrypt-pbkdf (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/1964025
Title:
Do not support OpenSSL 3
To manage
The solution for this issue reported in ruby/openssl will fix part of
the net-ssh issue:
https://github.com/ruby/openssl/issues/498
** Bug watch added: github.com/ruby/openssl/issues #498
https://github.com/ruby/openssl/issues/498
--
You received this bug notification because you are a
It is also impacting vagrant already in Jammy (the release pocket). The
following does not work because of this issue:
$ vagrant init debian/buster64
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in
This issue is currently blocking ruby2.7 removal from Jammy. The removal
requires the migration of ruby-bcrypt-pbkdf in jammy-proposed:
$ reverse-depends src:ruby2.7
Reverse-Depends
* ruby-bcrypt-pbkdf (for libruby2.7)
Packages without architectures listed are reverse-dependencies
Thanks for reporting this bug and trying to make Ubuntu better.
Looking at the logs, I noticed you tried to install mariadb on top of
mysql, that's not a supported use case and you should try to pick one of
them. Once you tried to install mariadb, mysql was supposed to be
removed and for some
Hi Norbert,
All the unmet dependencies you got are already available in the PPA. To
be in the safe side, you might want to specify all of them, one by one,
specifying the version in the PPA. This likely happened because you need
all the dependencies locked to the same version, since you did not
Thanks for describing your findings Norbert, and good to hear you have a
functional environment now. This might be helpful for others. In this
case, I do not think there is much we can do here, since this is a very
specific case in Oracle Cloud.
--
You received this bug notification because you
I upgraded openssh-server in a Impish VM locally and I was not able to
reproduce the issue you described. Are you able to provide some detailed
steps on how to reproduce this bug? Could you check if you face the same
issue with Jammy (22.04)?
--
You received this bug notification because you are
Thanks for letting us know Thomas, since this is already fixed in Jammy
I am marking this task as Fix Released. I am adding tasks for Focal and
Impish to check if this bug is still present there.
** Also affects: samba (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects:
Thanks for letting us know John. I am subscribing ubuntu-server so we
can take a look at this update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963831
Title:
Open-vm-tools 12.0.0 has been
Thanks for taking the time to file this bug and try to make Ubuntu
better.
After taking a look at the mentioned file
(debian/etc/conf.d/20-policy_banks in the source package), it seems that
you are right, this config has no effect since there is no definition of
`$policy_bank{'WHITELIST'}`. In
*** This bug is a duplicate of bug 1960454 ***
https://bugs.launchpad.net/bugs/1960454
Thank you for reporting this bug and trying to make Ubuntu better.
From the logs:
MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of
symbolic links: '/etc/mysql/my.cnf'
Since it seems
Public bug reported:
Upstream still does not support OpenSSL 3, and due to that a bunch of
tests are failing. Fedora has been seeing the same problem and they
filed a bug upstream:
https://github.com/net-ssh/net-ssh/issues/843
** Affects: ruby-net-ssh (Ubuntu)
Importance: High
The agents in resource-agents-base did not require any change. And I was
not able to find any occurrence of this type of issue with a simple grep
command in the other agents inside the extra package. If someone find
any issue please file another bug describing that.
** Changed in: resource-agents
The scope of this bug is only the agents present in
{resource,fence}-agents-base which are in main. The other agents in
{resource,fence}-agents-extra should work just fine but they are not
curated by the Ubuntu Server team.
--
You received this bug notification because you are a member of Ubuntu
The scope of this bug is only the agents present in
{resource,fence}-agents-base which are in main. The other agents in
{resource,fence}-agents-extra should work just fine but they are not
curated by the Ubuntu Server team.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: vsftpd (Ubuntu)
Assignee: Lucas Kanashiro (lucaskanashiro) => (unassigned)
** Changed in: vsftpd (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
** Tags removed: server-todo
** Tags added: server-next
--
You received this bug notification b
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
In this case, what you described is exactly what is expected. The
/etc/cron.d/php file is expected to trigger the execution of the
/usr/lib/php/sessionclean script only in systems not running systemd.
That's why we have
Thanks for reporting this bug and trying to make Ubuntu better.
This is indeed something we can cherry-pick from upstream. I talked to
Athos (who did the last upload) and he will be working on it.
** Changed in: bind9 (Ubuntu)
Status: New => Triaged
** Changed in: bind9 (Ubuntu)
You can find the binaries of samba/2:4.7.6+dfsg~ubuntu-0ubuntu2.23 here
(clicking on the architecture you are using):
https://launchpad.net/ubuntu/+source/samba/2:4.7.6+dfsg~ubuntu-0ubuntu2.23
And you could download and install them if you want.
@Andreas do you think this is something
Thanks Michael, it indeed seems flaky. I'll be adding this bug to our
backlog to be tackled when we have some time to do it.
** Changed in: cluster-glue (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I did not find any Oracle specific doc on how to upgrade a Ubuntu system
to Impish, which is kind of expected since they do not support this use
case. I'd recommend you to try to use `do-release-upgrade` to do that.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Groovy and Hirsute reached the end of regular support, so I am marking
those tasks as Won't Fix.
** Changed in: apache2 (Ubuntu Groovy)
Status: Triaged => Won't Fix
** Changed in: apache2 (Ubuntu Hirsute)
Status: Confirmed => Won't Fix
--
You received this bug notification
The fix is available in freeradius v3.0.x, and since we have this
version in all currently supported Ubuntu releases I am marking this bug
as Fix Released.
** Changed in: freeradius (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member
** Changed in: multipath-tools (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961633
Title:
Consider dropping d/p/kpartx-Improve-finding-loopback-device-by-
Hi arnoldthebat,
Just to double check, were you attached to an UA subscription before performing
apt upgrade ?
Also, does the problem persist if you run:
apt-get install ubuntu-advantage-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi Gene Sun,
This is a really odd issue and I have never experienced it before. I think the
best path forward is to contact the snapd team and ask for help there, as this
could be a bug on the package:
https://bugs.launchpad.net/ubuntu/+source/snapd
Since this is issue is snapd related, I am
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960036
Title:
[SRU] Doesn't regain quorum when tracked
** Changed in: vsftpd (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960837
Title:
New upstream version supports modern
After talking to the Security team, we agreed that once the packages
land in -updates they will upload a no-change rebuild to the security
pocket. I'll let them know when the packages land in -updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the investigation Liam. This is in our backlog for further
investigation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954306
Title:
Action `remove-instance` works but appears to fail
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
This is indeed something that we should ship in the next LTS release. We
do not carry any delta compared to the version in Debian, I'll ping the
Debian maintainer to try to get this new version there and then sync it
Norbert,
Could you also provide which open-iscsi version you are using? I was
checking the difference between open-iscsi in bionic and focal and the
upstream version is the same but some patches were applied. For
instance, this is one bug reported by one Orable Cloud user which was
fixed in
Hello Gene Sun,
It seems there is something wrong if your snapd service.
What is the output of running:
$ systemctl status snapd
And if the service is not running, can you run:
$ systemctl start snapd.service
And double check if snap services is now running as expected ?
--
You received
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960712
Title:
package ubuntu-advantage-tools 27.6~20.04.1 failed to
** Changed in: containerd (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: containerd (Ubuntu Impish)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(Ubuntu Impish)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: containerd (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: docker.io (Ubuntu Bionic)
Status: New => Triaged
** Changed in: docker.io (Ubuntu F
I am tracking the backport of the entire container stack (docker.io,
containerd and runc) in this bug:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1960449
Please refer to that when checking the status of the backport.
** Tags removed: server-todo
--
You received this bug notification
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960449
Title:
Backport container stack in Jammy
To manage notifications about this bug go to:
201 - 300 of 3389 matches
Mail list logo
