** Also affects: lxd-installer (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: lxd-installer (Ubuntu Noble)
Status: New => In Progress
** Changed in: lxd-installer (Ubuntu Noble)
Assignee: (unassigned) => Simon Déziel (sdeziel)
--
You received this bug
** Changed in: ruby-defaults (Ubuntu)
Milestone: ubuntu-24.05 => ubuntu-24.07
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064458
Title:
Merge ruby-defaults from Debian unstable for oracular
** Changed in: ruby-ethon (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/2064459
Title:
Merge ruby-ethon from Debian unsta
** Changed in: runc (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/2064461
Title:
Merge runc from Debian unsta
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
I tried to install dnsmasq in a brand new LXD container running Noble
(24.04) and I was not able to reproduce the failure you mentioned:
root@dnsmasq-install:~# apt install dnsmasq
Reading package lists... Done
** Also affects: qemu (Ubuntu Jammy)
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/2064914
Title:
Windows guest hangs after reboot from the guest OS
To
@u-jjohansen,
I had an interesting result today. I powered off my live 24.04 Lubuntu
installation and rebooting into a new live 24.04 Lubuntu installation.
This time, however, I installed Thunderbird stable as a .deb from
Mozilla. And I ran my old script:
```
$ cat thunder.sh
cp -R
I am adding the test results for Mantic. Those tests confirm that the
daemon doesn't run on Mantic, which makes this release unaffected by
this issue.
** Attachment added: "mantic-test-results.tar.xz"
Any workaround for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051574
Title:
gnome-shell-portal-helper crashed with SIGTRAP in
waitUntilSyncedOrDie() from WebKit::XDGDBusProxy::launch()
I also see that you are patching golang-github-containers-common. Does
that mean that no patch in libpod is needed? If the answer is yes, we
need to mark the libpod tasks as Invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Tomáš,
Thanks for investigating this issue and providing the patch (MP) to fix
it in Noble. However, before fixing it in Noble, we need to fix it in
Oracular (development release). Would you like to provide a patch or MP
targeting Oracular?
--
You received this bug notification because you
The src:runc regressions above helped me to identify an error in the
package. I forgot to remove the basic-smoke test which tries to make use
of the runc binary (now provided by src:runc-app). In order to fix this,
I uploaded src:runc again to Focal (1.1.7-0ubuntu1~20.04.4), Jammy
Now that src:runc-app was accepted from NEW in all supported releases,
we are ready to land the other updates in -proposed to verify everything
together.
Please, SRU vanguard, could you check and move the uploads from
-unapproved to -proposed?
--
You received this bug notification because you
It indeed looks like an issue (but it is not :p). After discussion with
the Server team, we will leave it like this in Noble (there is no
regression), and in OO series we will revisit the usage of a build
profile to not build the runc binary package.
--
You received this bug notification because
Thanks for your time reporting this bug and trying to make Ubuntu
better.
I see the mysql-server is installed alongside mysql-workbench-community
(which is not in the Ubuntu archive and is not supported), this
interaction is untested and might pose you some unexpected behavior.
The mysql error
New install of ubuntu 24.04, causes this issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181666
Title:
gnome-shell randomly blocks mouse clicks from working in app windows
To manage
@u-jjohansen,
You ask:
```
what kind of configuration have you done?
```
I just:
```
sudo apt update
sudo apt install thunderbird
cp -R /media/lubuntu/drive/startup/thunderbird
/home/lubuntu/snap/thunderbird/common/.thunderbird
cp /media/lubuntu/drive/startup/lubuntu_thunder/profiles.ini
Issue present on installed today 24.04, during initial boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051574
Title:
gnome-shell-portal-helper crashed with SIGTRAP in
waitUntilSyncedOrDie()
@u-jjohansen
```
$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs
(rw,nosuid,relatime,size=7984072k,nr_inodes=1996018,mode=755,inode64)
devpts on /dev/pts type devpts
Oh also, by using
```
~/.thunderbird/p0dln6zn.default$ ls -A
```
I just noticed there's a .parentlock right now in that directory ... in
case it's relevant
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@u-jjohansen:
```
$ mount | grep overlay
/cow on / type overlay
(rw,relatime,lowerdir=/filesystem.squashfs,upperdir=/cow/upper,workdir=/cow/work,uuid=on,xino=off,nouserxattr)
/cow on /var/snap/firefox/common/host-hunspell type overlay
@u-jjohansen:
```
$ sudo dmesg | grep DENIED
[ 20.729222] audit: type=1400 audit(1714359674.872:42): apparmor="DENIED"
operation="open" class="file" profile="snap-update-ns.firefox"
name="/usr/local/share/" pid=2002 comm="6" requested_mask="r" denied_mask="r"
fsuid=0 ouid=0
[ 20.743227]
@u-jjohansen:
Also, I'm having this Thunderbird problem going on simultaneously --
https://forum.snapcraft.io/t/unexplained-thunderbird-already-running-
but-is-not-responding-message/39990 -- which might be related to the
issues from my Chrome comments?
--
You received this bug notification
@u-jjohansen:
Yes, live environment only. Sorry, I thought I'd included that in my
first comment but now I see that I neglected to do so. I added an EDIT:
to my first comment to make it clear.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@jjohansen:
```
$ sudo aa-status
apparmor module is loaded.
56 profiles are loaded.
54 profiles are in enforce mode.
/snap/snapd/21465/usr/lib/snapd/snap-confine
/snap/snapd/21465/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
/usr/lib/snapd/snap-confine
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060566
Title:
Add
I seem to have the same apparmor problem with Chrome under Lubuntu
24.04. From "$ journalctl | grep apparmor | grep chrome" I got
info="Userns create restricted - failed to find unprivileged_userns
profile" (among other things). And it's been reproduced by another as
the following relates.
Can
This is expected since the library package is arch:all and is not built
in non-amd64 arches. The runc binary package was moved to src:runc-app.
Therefore, no binary package is built in non-amd64 architectures by
src:runc.
--
You received this bug notification because you are a member of Ubuntu
I think I understood this.
I have a udev rule to force the NIC name to eno1, which is not the
driver's default (it is eno1np0). I did not regenerate the initramfs, so
that rule did not propagate there.
What happens is:
- initramfs is executed. The NIC is renamed to eno1np0 (driver's default).
-
It worked fine in Ubuntu 23.10: network-online.target is only reached
after eno1 is configured.
# journalctl -b |grep -e network -e grid5000.mount
Apr 28 00:23:06 localhost kernel: drop_monitor: Initializing network drop
monitor service
Apr 28 00:23:06 localhost systemd[1]: Listening on
Public bug reported:
Hi,
Running Ubuntu 24.04 with netplan.io/netplan-generator 1.0-2ubuntu1.
I use a systemd unit to mount an NFS filesystem. That unit should only
be activated when the network is ready. However, it looks like network-
online.target is reached before netplan-configured
Hi Dirk Su,
I cloned the git repo and for instance the debian/changelog is
confusing, there are many entries which makes me think that this package
is already maintained somewhere else, is this maintained in a PPA and
now you are trying to put it in the Ubuntu archive? When the package is
landing
Apparently, there is nothing to be sponsored here, I am unsubscribing
~ubuntu-sponsors. If I misunderstood the status of this bug and there is
something ready to be sponsored, please subscribe ~ubuntu-sponsors
again.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@Arif are the attached debdiffs ready to be uploaded? I do not know if I
get it right, but the bug you mentioned is not yet fixed:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648
If this is ready for ~ubuntu-sponsors, please state so. If not, please
unsubscribe ~ubuntu-sponsors
Thanks for the patch @Kai-Heng! I took a look and in general it looks
good, but I'd like to ask you to add some DEP-3 headers [1] to your
patch, that will give us (packagers) more context when revisiting this
package for whatever reason.
Now a personal opinion, I like when the patch file name is
@Matthew I took a look at your debdiffs (I hope they are updated) and
they look good in general, I checked the debdiffs for Focal, Jammy,
Mantic and Noble. The Noble debdiff requires a rebase, now in Noble we
have version 1.47.0-2.4~exp1ubuntu4, so we want version
1.47.0-2.4~exp1ubuntu4.1 with
Thanks for providing the workaround Tomáš! I can confirm that it works
in Noble, but for me, even using the profile you provided in comment #4,
the command below takes more or less 10 seconds (against 12 seconds when
the containers are killed with SIGKILL):
root@docker-apparmor:~# time docker
FWIW there is no autopkgtest regression now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051380
Title:
Expired certificate used for tests causes failures
To manage notifications about this bug
FWIW there is no autopkgtest regression now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049197
Title:
ruby_xfree segmentation fault
To manage notifications about this bug go to:
The packages built fine in all supported architectures, satisfying the
Test Plan section.
** Tags removed: verification-needed verification-needed-jammy
verification-needed-mantic
** Tags added: verification-done verification-done-jammy
verification-done-mantic
--
You received this bug
# Verification Mantic
root@ruby31-segfault-fix:~# dpkg -l ruby3.1
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Even though the verification is already done, we intend to only release
this package on April 30
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060566
Title:
Add esm-infra-legacy support for Trusty
I have performed the verification for this proposed changed.
Attached to this comment, are the test results we have obtained when running a
custom script that:
1) Launches a trusty lxd container
2) Install the proposed version of the Pro client
3) Checks that esm-infra-legacy appears on ua
I uploaded the container stack packages to Noble to make them build with
Go 1.22, those are the versions that require approval:
- runc-app/1.1.12-0ubuntu3
- container-app/1.7.12-0ubuntu4
- docker.io-app/24.0.7-0ubuntu4
- docker-buildx/0.12.1-0ubuntu2
- docker-compose-v2/2.24.6+ds1-0ubuntu2
I
All the container stack packages are using golang-1.21 because it is
available in all supported releases (we want to keep the same behavior
everywhere). Unfortunately, golang-1.22 is only in Noble. We could move
to golang-1.22 in Noble if Foundations backport golang-1.22 to the other
releases
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
Could you please share your config files so we can try to reproduce the
bug locally?
** Changed in: autofs (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
As Hugh already mentioned, it seems that you are installing packages not
from the Ubuntu archive and that is not supported. This part of the log
makes me believe on that:
modified.conffile..etc.odbc.ini:
[ODBC
Public bug reported:
Hi,
running the following test case in a current (today/2024-04-11) Noble
install leads to a "buffer overflow detected":
$ rsync -F --delete-after --archive /etc/fstab 127.0.0.1:/tmp/
*** buffer overflow detected ***: terminated
rsync: connection unexpectedly closed (11
** Description changed:
+ [Impact]
+
+ When users create an airgapped environement, they may create APT mirrors
+ for the ESM services that share a common base URL. For example, in this
+ bug here, the user was mirroring their services one:
+
+
** Description changed:
+ [ Impact ]
+
+ Since we want users to relate to the Pro name when using the client,
+ renaming the collect_logs output from ua_logs to pro_logs is a step on
+ that direction.
+
+ [ Test Plan ]
+
+ This is already covered by the integration tests tied to the next Pro
Public bug reported:
[ Impact ]
This release brings both bug-fixes and new features for the Pro Client,
and we would like to make sure all of our supported customers have
access to these improvements on all releases.
The most important changes are:
- d/apparmor:introduce new
** Description changed:
[Impact]
As Trusty is reaching EOL of ESM support, we are now creating a new service
called esm-infra-legacy to extend ESM support for more time.
- Users who are entitled to that service, will need to run both of these
- commands to enable the service in their
** Also affects: ubuntu-advantage-tools (Ubuntu Trusty)
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/2060566
Title:
Add esm-infra-legacy support for
** Description changed:
- As Trusty is reaching EOL of ESM support, we are now creating a new
- service called esm-infra-legacy to extend that support for more time
+ [Impact]
+ As Trusty is reaching EOL of ESM support, we are now creating a new service
called esm-infra-legacy to extend ESM
Public bug reported:
As Trusty is reaching EOL of ESM support, we are now creating a new
service called esm-infra-legacy to extend that support for more time
** Affects: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
I am not sure why ~ubuntu-sponsors is subscribed to this bug. Is someone
actively working on this? Is this still an issue nowadays?
For now, I am unsubscribing ~ubuntu-sponsors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As you can see here:
https://launchpad.net/ubuntu/+source/dune-uggrid
The version 2.9.0-2build2 was already uploaded with a no changes
rebuild:
dune-uggrid (2.9.0-2build2) noble; urgency=medium
* No-change rebuild for CVE-2024-3094
-- Steve Langasek Sun, 31 Mar 2024
18:05:33 +
This
Unsubscribing ~ubuntu-sponsors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058692
Title:
black autopkgtest fails because python3-typed-ast no longer in archive
To manage notifications about
Thanks Chris! I added just a reference to this bug in the changelog,
with that this bug will be closed once the package migrates. Keep an eye
on that next time. Package uploaded:
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading pnc_0.9.4-3build3.dsc: done.
Uploading
Right now, version 5.7.1-3 fails to build in Noble because of some
uninstallability issues:
The following packages have unmet dependencies:
libobjc-13-dev : Depends: gcc-13-base (= 13.2.0-13ubuntu1) but
13.2.0-17ubuntu2 is to be installed
Depends: libgcc-13-dev (=
I was able to build it now. Package uploaded:
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading gvmd_23.1.0-1ubuntu3.dsc: done.
Uploading gvmd_23.1.0-1ubuntu3.debian.tar.xz: done.
Uploading gvmd_23.1.0-1ubuntu3_source.changes: done.
Successfully uploaded packages.
--
You
Hi Dirk Su,
If I understood correctly, what you want here is someone to sponsor the
upload of lenovo-wwan-unlock, and this is the git repo with the source
package:
https://launchpad.net/ubuntu/+source/lenovo-wwan-unlock
Did I get it right?
You added the MIR bug description template here and it
I am unsubscribing ~ubuntu-sponsors for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058192
Title:
[MIR][needs-packaging] lenovo-wwan-unlock
To manage notifications about this bug go to:
The changes look good to me. However, when trying to build it in Noble
it fails at the moment (because of the ongoing transitions). If I build
it with noble-updates I get the following unmet dependencies:
The following packages have unmet dependencies:
libobjc-13-dev : Depends: gcc-13-base (=
The patch looks good, but I cannot build the package locally due to some
uninstallability issues with gcc-13 at the moment in Noble:
The following packages have unmet dependencies:
libobjc-13-dev : Depends: gcc-13-base (= 13.2.0-13ubuntu1) but
13.2.0-17ubuntu2 is to be installed
Public bug reported:
ruby-faraday-middleware was marked as deprecated by ruby-faraday 2.x:
https://github.com/lostisland/faraday_middleware?tab=readme-ov-
file#faraday-middleware
As expected, the tests do not work with the new version. We need to follow
Debian and request its removal:
Public bug reported:
ruby-behance/0.6.1-4 does not support ruby-faraday 2.x and last upstream
commit in the Github repo was from 6 years ago:
https://github.com/amedrz/behance
Apparently, there will not be any further developement. In Debian, the
Ruby team is planning to remove it from the
** Description changed:
[ Impact ]
Currently, the Pro client support a daemon named ubuntu-advantage.service that
performs two actions:
* Actively look for Pro licenses on Azure and GCP images to perform an
auto-attach
* Retry auto-attach on Pro images if that command fails on boot
** Description changed:
[ Impact ]
Currently, the Pro client support a daemon named ubuntu-advantage.service that
performs two actions:
* Actively look for Pro licenses on Azure and GCP images to perform an
auto-attach
* Retry auto-attach on Pro images if that command fails on boot
** Description changed:
[ Impact ]
- If the user has specified custom setup for the Pro client through cloud-init,
there is a high chance that this setup will be ignored.
+ Currently, the Pro client support a daemon named ubuntu-advantage.service that
+ performs two actions:
- This happened
** Description changed:
- We have recently updated the Pro to not strictly run after cloud-
- config.service. If cloud-config.service has not been started when pro
- runs, it can complete before cloud-config.service begins and thus the
- user-specificed pro configuration will be ignored since the
Public bug reported:
ruby-defaults/1:3.2~ubuntu1 is now in the release pocket (the default is
ruby3.2) and ruby3.1 (source and binaries) should be removed from Noble.
There is no package depending on it in Noble at the moment:
$ reverse-depends -r noble src:ruby3.1
$ reverse-depends -r noble
Public bug reported:
We have recently updated the Pro to not strictly run after cloud-
config.service. If cloud-config.service has not been started when pro
runs, it can complete before cloud-config.service begins and thus the
user-specificed pro configuration will be ignored since the instance
Hi Brandon Castillo,
I think that is a good idea and I agree that we can make this error
message better.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
Checking the logs, this is the problem you faced:
mysqld: Error on realpath() on '"/var/lib/mysql-files/";' (Error 2 - No
such file or directory)
Could you confirm that the /var/lib/mysql-files does not exist? Did
** Description changed:
+ [Impact]
+
+ This is causing a FTBFS, so rubyx.y cannot be rebuilt.
+
+ [Test Plan]
+
+ Build the package in the targeted releases. No test failure is expected.
+
+ [Where Problems could occur]
+
+ The test certificates were renewed, to be honest I fail to foresee
** Description changed:
+ [Impact]
+
+ Users might face a segfault when using ruby_free.
+
+ [Test Plan]
+
+ # apt update && apt install -y ruby ruby-nokogiri
+ # cat > reproducer.rb <=22.04 that causes
segfault relatively rarely. Even though rare with repetitions running
small wrappers it
No. Ruby 3.2 will be supported by Canonical during lifetime of Noble. We
do not change default interpreters in stable releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052313
Title:
Ubuntu
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: ruby3.1 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: ruby3.1 (Ubuntu Mantic)
Status: New => In Progress
** Changed in: ruby3.1 (Ubuntu Mantic)
Assignee: (unassigned) => Lucas Kanashiro (luc
Noble will be released with Ruby 3.2 as the default. Right now, many
transitions are ongoing and because of that the ruby one is not complete
yet. But do not worry, users will have Ruby 3.2 in Noble.
** Changed in: ruby3.1 (Ubuntu)
Status: New => Invalid
** Changed in: ruby-defaults
This is fixed in ruby3.2/3.2.3-1build2 in Noble.
** Changed in: ruby3.2 (Ubuntu Noble)
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/2049197
Title:
Ubuntu Noble)
Status: New => Triaged
** Changed in: ruby3.1 (Ubuntu Mantic)
Status: New => Triaged
** Changed in: ruby3.0 (Ubuntu Jammy)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: ruby3.1 (Ubuntu Mantic)
Assignee: (unassigned
** Merge proposal linked:
https://code.launchpad.net/~calvinmwadime/ubuntu/+source/walinuxagent/+git/walinuxagent/+merge/461115
** Merge proposal linked:
https://code.launchpad.net/~calvinmwadime/ubuntu/+source/walinuxagent/+git/walinuxagent/+merge/461117
** Merge proposal linked:
I am uploading src:runc to the SRU queue but it should land once the
src:runc-app is accepted from NEW (in all supported releases).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040460
Title:
MRE
c)
Status: New => In Progress
** Changed in: runc (Ubuntu Mantic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: runc (Ubuntu Jammy)
Status: New => In Progress
** Changed in: runc (Ubuntu Jammy)
Assignee: (unassigned) => Lucas Kanas
** Description changed:
- Backport container-stack as MRE to noble once the update for noble has
- been completed.
+ [Impact]
-
+ In order to follow our policy on keeping the container stack (docker.io-
+ app, containerd-app, runc, runc-app, docker-buildx, and docker-
+ compose-v2) up-to-date
Ubuntu Mantic)
Status: New => In Progress
** Changed in: docker-buildx (Ubuntu Jammy)
Status: New => In Progress
** Changed in: docker-buildx (Ubuntu Mantic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: docker-buildx (Ubuntu Jammy)
Assignee: (u
Hi Helga,
Thanks for taking the time to report this bug and trying to make Ubuntu
better.
From what I understood this is an issue with the snap package of
Thunderbird, if that's the case you should try to report here (?):
https://snapcraft.io/thunderbird
I am not sure if this bug will reach
Could you provide your config file? Also state if you applied any
customization in your set up? Those things would be useful to reproduce
what you described locally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Shouldn't this be marked as duplicate then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056443
Title:
CHECK_RCPT_SPF SPF check fails if inbound IP address is IPv6
To manage notifications about
I am working on it.
** Changed in: containerd-app (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: docker.io-app (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: containerd-app (Ubuntu)
Statu
Public bug reported:
I can not install the gpu driver without an error.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
ApportVersion:
Public bug reported:
ruby-gruff/0.6.0-2 do not support ruby-rmagick/5.3.0-2build2 and this is
blocking the ruby-defaults migration.
There is a new upstream release of ruby-gruff (a.k.a. version 0.23.0)
which seems to support this newer version of ruby-rmagick, however, it
requires some new
** Changed in: pcs (Ubuntu)
Status: New => In Progress
** Changed in: pcs (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/2040410
Title:
Public bug reported:
ruby-rgfa/1.3.1+dfsg-2 does not support ruby 3.2. Many core feature of
this gem rely on methods that were removed from ruby 3.2. I do not
expect any fix from upstream, since the last commit is from 8 years ago:
https://github.com/ggonnella/rgfa
FWIW this is the autopkgtest
Public bug reported:
diaspora-installer/0.7.18.2+debian4 do not support ruby 3.2. Initially
we have an issue with the configurate gem native extension build, which
can be seen in the autopkgtest log:
Hi,
Could you please share the core dump with us? That would help us
investigate better this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/720638
Title:
snmpd crashes with segfault
Hi Luís,
This CVE is indeed not fixed yet in none of the Ubuntu releases:
https://ubuntu.com/security/CVE-2022-22747
As you can see on the top of the page the priority was marked as Low, so
I think the Security team is not considering this too important. Maybe
someone from the Security team
*** This bug is a duplicate of bug 1960449 ***
https://bugs.launchpad.net/bugs/1960449
The backport of the following packages were done in Jammy, Impish and
Focal:
- runc version 1.1.0
- containerd version 1.5.9
- docker.io version 20.10.12
This is not fully complete (missing Bionic)
)
** Changed in: containerd (Ubuntu)
Milestone: ubuntu-22.08 => ubuntu-22.09
** Changed in: containerd (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: docker.io (Ubuntu)
Milestone: ubuntu-22.08 => ubuntu-22.09
** Changed in: docker.io (Ubuntu)
1 - 100 of 3386 matches
Mail list logo
