** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1918960
Title:
kernel does not honor mokx revocations, allowing kexec
I tried earlyprintk=efi command line option but it still does not
display anything after boot
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
https://lore.kernel.org/lkml/1884195.1615482...@warthog.procyon.org.uk/
is still not upstream.
https://lore.kernel.org/lkml/20210312171232.2681989-1-...@digikod.net/
may also be worth watching.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1918960
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Pop OS 20.10 has updated to kernel 5.11 and touchpad now works out of the box
without patching.
This is a great day for my laptop!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
T
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-26541
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
Updated the [Where problems will occur] part.
** Description changed:
[Impact]
On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.
[Fix]
Disable IEC958 (SPDIF) through ALSA UCM.
[Test]
With the UCM applied, `pactl` and audio panel in gnome-control-center
** Tags added: binder
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1921976
Title:
Can't create additional binder devices the user needs to specify them
Status in linux-azure pac
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1920685
Title:
Shity ubujntu 20.04 upgrade
S
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux - 5.11.0-13.14
---
linux (5.11.0-13.14) hirsute; urgency=medium
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cases for unprivileged
* CVE-2020-27171
This bug was fixed in the package linux-riscv - 5.11.0-1004.4
---
linux-riscv (5.11.0-1004.4) hirsute; urgency=medium
[ Ubuntu: 5.11.0-13.14 ]
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cas
This bug was fixed in the package linux-riscv - 5.11.0-1004.4
---
linux-riscv (5.11.0-1004.4) hirsute; urgency=medium
[ Ubuntu: 5.11.0-13.14 ]
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cas
This bug was fixed in the package linux-riscv - 5.11.0-1004.4
---
linux-riscv (5.11.0-1004.4) hirsute; urgency=medium
[ Ubuntu: 5.11.0-13.14 ]
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cas
This bug was fixed in the package linux-riscv - 5.11.0-1004.4
---
linux-riscv (5.11.0-1004.4) hirsute; urgency=medium
[ Ubuntu: 5.11.0-13.14 ]
* CVE-2020-27170
- bpf: Prohibit alu ops for pointer types not defining ptr_limit
- bpf, selftests: Fix up some test_verifier cas
Hi,
thanks for trying this out.
If this is still reproducible, please give the latest mainline kernel [1] a try
to see if you issue exists in the upstream kernel. Instructions could be found
in [2]
Please flip the bug status back to confirmed after your test.
Thank you!
[1] https://kernel.ubunt
Ok. I got it working.
I built from here.
git clone https://github.com/thesofproject/linux.git
with
CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
I uploaded my kernel debian/ubuntu packages to
https://drive.google.com/drive/folders/1L9DpjMamc37tZ19s5u_4RfmV221F4222?usp=sharing
Affected Spectre X360 l
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1921974
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
ubuntu azure seems not support binder FS.
$ uname -r
5.8.0-1026-azure
$ sudo modprobe binder_linux
$ mkdir ./tbinder
$ sudo mount -t binder binder ./tbinder
mount: /tbinder: unknown filesystem type 'binder'.
$ cat /proc/filesystems | grep binder
Another generic server work
Public bug reported:
[Impact]
On CML-R, after S3, No screen show on all three connector(3*DP).
[Fix]
The v4 patch has been landed on drm-tip.
For Legacy S3 suspend/resume GEN9 BC needs to enable and setup TGP PCH.
[Test Case]
1. Connected the monitor on one of 3*DP on CML-R.
2. Suspend&resume th
** Changed in: linux (Ubuntu Bionic)
Importance: Medium => High
** Changed in: linux (Ubuntu Focal)
Importance: Medium => High
** Changed in: linux (Ubuntu Groovy)
Importance: Medium => High
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Confirmed that on a working system, just updating to the new kernel breaks it.
So that SRU kernel is definitely broken and should not be shipped.
[8.996651] BUG: unable to handle kernel NULL pointer dereference at
e12c1a77
[8.998738] IP: [] fuse_do_setattr+0x52/
When a single test fails occasionally, it can be an issue with LXD or
with the test, but when a bugfix release of a stable kernel suddenly
causes one of the most trivial tests to fail on all architectures, this
strongly suggests that the kernel is the issue.
--
You received this bug notification
This looks like a kernel regression to me.
** Package changed: lxd (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921969
Title:
lxd 2.0.11-0ubuntu1~16.04.4 A
You have been subscribed to a public bug:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUT
** Tags added: armhf focal groovy kqa-blocker sru-20210315
** Summary changed:
- nvidia-graphics-drivers-390 390.141-0ubuntu0.20.10.1 ADT test failure with
linux 5.8.0-49.55
+ nvidia-graphics-drivers-390 390.141-0ubuntu0.20.10.1 ADT test failure on
groovy and focal
** Description changed:
- T
Public bug reported:
Testing failed on:
armhf:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz
** Affects: nvidia-graphics-drivers-390 (Ubuntu)
Importanc
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1921944
and then change the status of the bug to 'Confirmed'.
If, due to the nature
hi Bambang, the fix is present in the current proposed version, 4.15.0-141 -
both versions 4.15.0-139 and -140 are CVE fixes only, so they didn't include
the KVM fix.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921944
Title:
ubuntu 20.04 kernel 5.8.0.48 freezes when thinkpad stylus touches
screen Leno
You have been subscribed to a public bug:
Description:Ubuntu 20.04.2 LTS
Release:20.04
When ubuntu 20.04 kernel 5.8.0.48 is running and stylus touches screen, ubuntu
freezes completely and hard restart via on/of button laptop is necessary.
In kernel 5.8.0.44 it still worked/works O
As you requested, this is the last journalctl log after freeze.
On Sun, Mar 28, 2021 at 10:25 PM Daniel van Vugt <1919...@bugs.launchpad.net>
wrote:
> The good news is there are no more "general protection fault" app
> crashes in those logs so the new RAM has fixed one big problem.
>
> As for th
Verified for Bionic following the same test procedure from comment #13, running
on the current -proposed kernel:
ubuntu@snorlax:~$ uname -rv
4.15.0-141-generic #145-Ubuntu SMP Wed Mar 24 18:08:07 UTC 2021
I had to adjust the tx_desc_addr probes, subtracting 0x4 from both offsets and
changing the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-azure (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bu
Verified for Xenial following the same test procedure from comment #13, running
on the current -proposed kernel:
ubuntu@snorlax:~/kprobe$ uname -rv
4.4.0-207-generic #239-Ubuntu SMP Thu Mar 25 02:59:26 UTC 2021
The offsets don't seem to have changed on any of the probes, so I've
used the same set
Hello Dave, or anyone else affected,
Accepted bluez into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.53-0ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1905020
Title:
[21.04 FEAT] Add kernel debug infos for decompressor stage to kernel-
d
Also affected by this issue. Asus Zenbook Flip 13 UX363EA. Ubuntu 20.04.
I can turn on/off the numberpad lights with the commands:
i2ctransfer -f -y 14 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00 0x0d 0x14
0x03 0x01 0xad
i2ctransfer -f -y 14 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: thermald (Ubuntu Focal)
Status: New => In Progress
** Changed in: thermald (Ubuntu Groovy)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete => In Prog
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1921916
and then change the status of the bug to 'Confirmed'.
If, due to the nature
--- Comment From stefan.ra...@de.ibm.com 2021-03-30 10:59 EDT---
OK, would that be a consideration? The idea is to have a service that logs kvm
events in a round-robin manner. To do so, 2 things need to happen:
(1) install the unit file kvm_stat.service
(2) install a respective logrotate f
Public bug reported:
CIFS GCM256 encryption is implemented in stable kernels beginning with
v5.10.y. These commits are required to support GCM256 in linux v5.8:
45a4546c6167a2da348a31ca439d8a8ff773b6ea
63ca5656350a9b798a20a8e5bd55be164a5abeb6
fd08f2dbf0c2e95f8503e2c79339fe5711f1aa1d
511ac89e591ab
Hi Stefan, no we don't ship the service file (at least not with 20.04 to 21.04):
$ dpkg -L linux-tools-host
/.
/usr
/usr/bin
/usr/bin/kvm_stat
/usr/share
/usr/share/doc
/usr/share/doc/linux-tools-host
/usr/share/doc/linux-tools-host/changelog.Debian.gz
/usr/share/doc/linux-tools-host/copyright
/usr
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921870
Title:
[UBUNTU 21.04] tools/kvm_stat: Add restart del
4th try: Works, but
[350616.380035] [drm:drm_dp_check_act_status [drm_kms_helper]] *ERROR* Failed
to get ACT after 3000ms, last status: 00
[350619.421657] [drm:drm_dp_check_act_status [drm_kms_helper]] *ERROR* Failed
to get ACT after 3000ms, last status: 00
So something seems to be still flacky
Sorry, didn't see the request :-/
I just tried with 5.8 from HWE. After my frist reconnect, I got a
[350240.293152] failed hdr00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
(nothing else!) in dmesg, nothing about the external monitors in xrandr.
At the second try (no restart), they work again.
--- Comment From stefan.ra...@de.ibm.com 2021-03-30 09:10 EDT---
OK, that sounds good!
Related question: Do you install that unit file and make available the kvm
service in Ubuntu at all? If so, could you try to reboot with the service
enabled to verify that it does work as expected (i.e.
Due to kind of report are no logs available.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921902
Title:
Security-
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1921902
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Verification done - see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918714/comments/5
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Public bug reported:
Today [XSA 371](http://xenbits.xen.org/xsa/advisory-371.html) was published
which contain a security patch for a commit which is included in proposed
5.4.0-71.
The [Patch](http://xenbits.xen.org/xsa/xsa371-linux.patch) is only 1 line maybe
you can add this security fix to 5
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1910291
Title:
update ENA driver, incl. new ethtool stats
Status in li
** Tags added: sru-20210315
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1880645
Title:
icmp_redirect.sh in net from ubuntu_kernel_selftests failed on
F-OEM-5.6 / G /
Marked as Incomplete as per request in comment #23
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1870786
Title:
Ker
Hello,
I can still see this failure on Groovy Azure kernel (5.8.0-1027.29-azure), do
we have this patch applied to groovy variants?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1917609
*** This bug is a duplicate of bug 1918148 ***
https://bugs.launchpad.net/bugs/1918148
Should have been fixed in 5.11.0-12.13 or newer. Mark duplicate to bug
1918148 instead.
** This bug has been marked a duplicate of bug 1918148
hirsute/linux: 5.11.0-13.14 -proposed tracker
--
You recei
*** This bug is a duplicate of bug 1918148 ***
https://bugs.launchpad.net/bugs/1918148
Public bug reported:
Since debhelper >= 13.3[1], dh-systemd has been moved into debhelper
itself and the transitional package has been removed[2], so the Build-
Deps for linux should be updated instead.
[1
This test fails on Groovy as expected now:
# selftests: net: xfrm_policy.sh
# PASS: policy before exception matches
# FAIL: expected ping to .254 to fail (exceptions)
# PASS: direct policy matches (exceptions)
# PASS: policy matches (exceptions)
# FAIL: expected ping to .254 to fail (exceptio
Since Ubuntu has KVM built-in (rather than being compiled as module)
this should not be needed for Ubuntu.
$ lsb_release -r
Release:21.04
$ arch
s390x
$ grep -i CONFIG_KVM= /boot/config-5.11.0-13-generic
CONFIG_KVM=y
$ lsmod | grep -i kvm
$ kvm-ok
INFO: /dev/kvm exists
KVM acceleration c
Default Comment by Bridge
** Attachment added: "Patch to fix the issue"
https://bugs.launchpad.net/bugs/1921870/+attachment/5482319/+files/tools-kvm_stat-Add_restart-delay.patch
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package change
You have been subscribed to a public bug:
Description: tools/kvm_stat: Add restart delay
Symptom: If the kvm service is enabled and the system rebooted,
Systemd's initial attempt to start the kvm unit file may
fail in case the kvm module is not loaded. However
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
This was fixed by https://launchpad.net/ubuntu/+source/qtwebengine-
opensource-src/5.15.2+dfsg-3ubuntu1.
And the tests pass since then:
http://autopkgtest.ubuntu.com/packages/n/notepadqq/hirsute/armhf.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Package changed: notepadq
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-groovy
--
You received this bug notification because you are a member of Kerne
84 matches
Mail list logo
