Public bug reported:
Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
In-situ OAM (IOAM6). This lack of support is also triggering the
following kernel selftest failure:
# selftests: net: ioam6.sh
# SKIP: iproute2 too old, missing ioam command
not ok 1 selftests: net: ioam
The 'signed-by' field is not supported in the python-apt classes that
are used by add-apt-repository and the gui software-properties.
- When adding a new source there's no argument to provide 'signed-by' or
'trusted' options, so those cannot be added via add-apt-repository or the gui
software-pr
For reference: https://gitlab.gnome.org/GNOME/gcr/-/issues/75
** Bug watch added: gitlab.gnome.org/GNOME/gcr/-/issues #75
https://gitlab.gnome.org/GNOME/gcr/-/issues/75
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcr i
** Also affects: iproute2 (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1951390
Title:
update iproute2 in jamm
Public bug reported:
[Summary]
chromium will be not responding after clicking the right mouse button and the
right-click box is blank
[Reproduce]
1. On ubuntu 20.04.3, open chromium.
2.click the right mouse button in the search box or above characters
[Expected result]
it will show copy paste……
It works fine before 20.2.6, but after I upgrade to 21.0.3, we found
this issue.
Commandline: apt install libegl-mesa0
Requested-By: u (1001)
Upgrade: libegl-mesa0:amd64 (20.2.6-0ubuntu0.20.04.1,
21.0.3-0ubuntu0.3~20.04.3), libglapi-mesa:amd64 (20.2.6-0ubuntu0.20.04.1,
21.0.3-0ubuntu0.3~20.04.3)
(updated the bug description with further details according to the SRU
template, including reproduction steps)
** Description changed:
** SRU TEMPLATE DRAFT **
[Impact]
+ In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
+
+ [Test
** Patch added: "iproute2-update-to-5.15.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+attachment/5541716/+files/iproute2-update-to-5.15.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to i
debdiff against Debian iproute2 5.15.0-1 (re-applied Ubuntu Fan driver).
v2: added this tracking bug to the changelog entry.
** Patch added: "iproute2-update-to-5.15-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+attachment/5541717/+files/iproute2-update-to-5.15-
Hello, is there anything needs me to provide for moving to the next
step?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1946096
Title:
Support manual firmware upgrad
As the fix is in Jammy I think we can mark the devel task as Fix
Released.
I doubt this is SRU material as the impact of the bug is really low;
maybe it could be done with a staged upload [1]. I'm marking the SRU
tasks as Triaged as the bug is well understood.
[1] https://wiki.ubuntu.com/StableRe
Older releases of Ubuntu used a group called "admin" instead of "sudo"
which is the name Debian chose later on.
We need to maintain the "admin" group rights in our sudoers file for
people upgrading from earlier Ubuntu releases. If we remove it, they
will no longer have sudo rights after upgrading.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/systemd/+question/699543
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubunt
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1951390
Title:
update iproute2 in jammy
Status in iproute2 package in Ubuntu:
New
Status in iproute
This bug was fixed in the package mesa - 21.0.3-0ubuntu0.3~20.04.4
---
mesa (21.0.3-0ubuntu0.3~20.04.4) focal; urgency=medium
* gallium-Reset-d-r-Priv-in-dri_unbind_context.patch: Fix chromium
hangs on WSL. (LP: #1950174)
-- Timo Aaltonen Wed, 10 Nov 2021 11:24:18 +0200
**
The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
I have the same issue on:
Dell E5495
AMD Ryzen 7 PRO 2700U w/ Radeon Vega Mobile Gfx
16Gb RAM
Linux Mint 19.3 (Ubuntu 18.04)
Kernel 5.15.2
Linux Firmware 1.173.20
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu
@arighi suggests used to be installed when one used to provide "needs-
suggests" restrictions or some such, but that got deprecated, so no
suggests are not getting installed by default.
However, we have a multi year MIR to seed and install nftables by
default let me check the status of that
ht
Public bug reported:
unable to update
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4
ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
Public bug reported:
When building ICU package from source, Time Zones tests are failing, leading to
a build failure.
This is happening because for Ubuntu, ICU uses tzdata package to retrieve Time
Zone information
And, tzdata is updated but ICU tests are not.
The tests that are failing are:
1)T
> I will attempt to upstream this fix to klibc, but I believe the change
to Bionic should happen in parallel/independently since the upstream
patch will not make its way back to Bionic (which is stuck at 2.0.4, as
mentioned above).
Yes that is the plan to SRU the fix on top of what is currently fo
** Merge proposal linked:
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/testresources/+git/testresources/+merge/412079
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-testtools in
Ubuntu.
https://bugs.lau
Thanks ddstreet, I agree 918e6f1c0151429f5095355f4f3f74f16e79724a could
be related as well, but unfortunately that commit produced quite some
fall-out.
Nevertheless, I've prepared a new systemd build in my PPA and the
"core18_2028_amd64.snap" at https://people.ubuntu.com/~slyon/uc18/
cherry-pi
Autopkgtests have now all passed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1940528
Title:
curl 7.68 does not init OpenSSL correctly
Status in curl package in Ubuntu:
I'm still suspecting dbus to be at fault here. We might need to bisect
dbus in order to find out more about this, but that is hard without a
reliable reproducer.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice
Thanks for catching that alexmurray. I'll upload new debdiffs in a
moment.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1951161
Title:
Please merge shadow 1:4.8.1-2 (main
> Do we even know for sure this krb5-k5tls is enough for fips
compliance, and that it replaces *all* crypto code in kerberos with
openssl calls?
No it does not. But intention is to make the over the network
communications with TLS to be FIPS-TLS compliant which is cheaper to
certify when reusing a
** Patch added: "Diff from Debian"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+attachment/5541800/+files/debian_ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bu
** Patch added: "Diff from 1:4.8.1-1ubuntu9"
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1951161/+attachment/5541799/+files/ubuntu_ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
** Package changed: glib2.0 (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1951434
Title:
package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to
Note one interesting point is that in a core18 system, a squashfs mount
(any loop-based mount, really) includes a dep from the mount to its loop
device, while the non-core system does not:
ddstreet@localhost:~$ cat /etc/issue
Ubuntu Core 18 on \4 (\l)
ddstreet@localhost:~$ systemctl list-dependen
This is normal behavior. The initramfs cannot know in which order the
devices need unlocking or if any need unlocking at all.
It starts trying lvm2 and to unlock cryptsetup, and that will make the
devices appear and boot continue.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed =
** Summary changed:
- Volume group "vgubuntu" not found when parition encrypted in LUKS
+ Prints message that 'Volume group "vgubuntu" not found' when partition
encrypted in LUKS
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Low
** Tags removed: rls-ff-incoming
** Tags add
This added BindsTo is what's causing the problem:
ddstreet@localhost:~$ systemctl show -p BindsTo snap-hello\\x2dworld-29.mount
BindsTo=
ddstreet@localhost:~$ sudo systemctl daemon-reload
ddstreet@localhost:~$ systemctl show -p BindsTo snap-hello\\x2dworld-29.mount
BindsTo=dev-loop6.device
ubu
Sorry to clarify that, the dep is added to the mount over a daemon-
reload, but only on core:
ddstreet@localhost:~$ systemctl list-dependencies snap-hello\\x2dworld-29.mount
snap-hello\x2dworld-29.mount
● ├─-.mount
● ├─snap.mount
● ├─system.slice
● └─var-lib-snapd.mount
ddstreet@localhost:~$ syst
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Changed in: software-properties (Ubuntu)
Status: New => In Progress
** Changed in: softw
Public bug reported:
When I connect a headphone and a speaker via bluetooth and select
headphone as the output device, the sound is still putout from the
speaker
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: openssh-server 1:8.2p1-4ubuntu0.3
ProcVersionSignature: Ubuntu 5.11.0-40.44~2
@Seth: The Ubuntu 20.04 that where I tested this issue was a virtualized
environments that runs Parallels Desktop over a Mac OS.
I cannot reproduce this issue on Debian Buster 10 (Arm64) with OpenSSL
using the same virtualized environment.
--
You received this bug notification because you are a
@Dan Thanks, this find about BindsTo is super interesting! It's not
something that snapd writes out, it's curious where this comes from.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad
I spend a bit more time bisecting the various core18 snaps to see at
what revision the failure started to become reproducible. Interestingly
I found that it started with r2208 AFAICT. It's all a bit annoying
because it's a race so I don't trust it 100% but the previous r2206 got
2 good runs in a ro
Ah, that's good for the health of your storage :)
Please follow up with the debug symbols and reproduction instructions.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bu
# Success testing on Bionic Desktop installer
1. Validate current behavior from bionic-updates
csmith@downtown:~$ IP=`uvt-kvm ip ubuntu18.04`
csmith@downtown:~$ ssh csmith@$IP
Welcome to Ubuntu 18.04.6 LTS (GNU/Linux 5.4.0-84-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management
# Success testing on Bionic Desktop installer
1. Validate current behavior from bionic-updates
csmith@downtown:~$ IP=`uvt-kvm ip ubuntu18.04`
csmith@downtown:~$ ssh csmith@$IP
Welcome to Ubuntu 18.04.6 LTS (GNU/Linux 5.4.0-84-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management
43 matches
Mail list logo
