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
Since these CVEs are now public, marking this bug as public too.
** 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 nvidia-graphics-drivers-470 in Ubuntu.
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
Subscribing ~ubuntu-archive to look at this request.
--
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/2041751
Title:
RM: Remove dangerously insecure MPPE PPTP from Ubuntu
Status in linux
Could the LXD team instead just read
/sys/kernel/security/apparmor/features/policy/unconfined_restrictions/userns
since this has the same value as the sysctl
/proc/sys/kernel/apparmor_restrict_unprivileged_userns
--
You received this bug notification because you are a member of Kernel
Packages,
This is planned to be fixed in the apparmor package itself in mantic by
proving a suitable profile for chrome - something like the following in
/etc/apparmor.d/opt.google.chrome.chrome
abi ,
include
/opt/google/chrome/chrome flags=(unconfined) {
userns,
# Site-specific additions and
Hmm after rebooting a few more times I see Bluetooth is now working as
expected on linux-image-6.2.0-23-generic - setting this ticket to
Incomplete unless I can gather some more information.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
Public bug reported:
After upgrading to the latest kernel updates in Lunar, I can no longer
enable Bluetooth in GNOME.
Rebooting back into 6.2.0-20-generic allows it to work again.
Looking at the journalctl log between the two, I see the following
differences for hci0:
$ diff <(journalctl
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
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
This is caused by duplicate entries in the DBX database shipped by
Lenovo on certain laptops:
https://lore.kernel.org/lkml/c8c65713-5cda-43ad-8018-20f2e32e4...@t-8ch.de/T/#m879b8faa1c2e415aef81e6cf42faa70f304773d9
It can be safely ignored.
** Information type changed from Private Security to
By marking this bug Private Security it is not able to be seen by the
required developers - I am marking it public again as there doesn't
appear to be anything security relevant here.
** Information type changed from Private Security to Public
--
You received this bug notification because you
By marking this bug Private Security it is not able to be seen by the
required developers - I am marking it public again as there doesn't
appear to be anything security relevant here.
** Information type changed from Private Security to Public
--
You received this bug notification because you
** Information type changed from Public Security 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/1912935
Title:
battery drain while notebook off / shutdown
Status in linux
*** This bug is a duplicate of bug 1991704 ***
https://bugs.launchpad.net/bugs/1991704
** This bug has been marked a duplicate of bug 1991704
Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
--
You received this bug notification because you are a member of Kernel
** 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.
https://bugs.launchpad.net/bugs/1991691
Title:
cannot change mount namespace
Status in Linux:
Looking at the commits between 5.19.7 and 5.19.8 this
https://git.launchpad.net/~ubuntu-kernel-
test/ubuntu/+source/linux/+git/mainline-
crack/commit/?h=cod/mainline/v5.19.8=c2798203315f4729bab0b917bf4c17a159abf9f8
looks suspiciously like the fix for this issue.
--
You received this bug
*** This bug is a duplicate of bug 1991704 ***
https://bugs.launchpad.net/bugs/1991704
Looks like a duplicate of LP: #1991704
** This bug has been marked a duplicate of bug 1991704
Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
--
You received this bug
Public bug reported:
Since upgrading to the 5.19.0.19.19 kernel (from 5.19.0-15.15) my
machine hangs when transitioning to plymouth. To boot successfully I
either have to use grub to select the older 5.19.0-15.15 kernel OR boot
into recovery mode and then choose to resume boot.
This occurs both
@lukenow could you please submit it as a merge request for the QA
Regression Testing project in Launchpad? https://code.launchpad.net/qa-
regression-testing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This sounds like a kernel regression.
The commit you link to is for SELinux, which is not enabled by default
in Ubuntu, so I doubt it is that specifically - instead I suspect this
is due to the following commit: https://git.launchpad.net/~ubuntu-
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
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
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
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
See this related debian bug https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1006368
--
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/1962276
Title:
[jammy] Laptop monitor does not turn
This appears to be caused (for me at least) by upower 0.99.16-1 - after
upgrading today to 0.99.16-2 things are working again as expected.
** Also affects: upower (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #1006368
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
** Package changed: libftdi (Ubuntu) => libftdi1 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libftdi in Ubuntu.
https://bugs.launchpad.net/bugs/1912371
Title:
[MIR] flashrom + libftdi
Status in flashrom package in Ubuntu:
I reviewed flashrom 1.2-5ubuntu1 as per the debdiff attached to this bug as
applied to 1.2-5 in impish. This shouldn't be considered a full audit but
rather a quick gauge of maintainability.
flashrom is a tool used for reading and flashing BIOS/ROM/firmware onto the
various flash chips within a
These failures of the mocked tests have been reported upstream at
https://github.com/flashrom/flashrom/issues/186 by others but no
response - however I am pretty sure this is due to the use of LTO in
impish - cmocka is known to fail with LTO due to the use of --wrap which
doesn't play nicely with
I am trying to do the security review of flashrom for this MIR but
currently it FTBFS with the attached debdiff in comment 9 - the build
log is attached. Can this please be resolved (along with removing the
'WILLIAM we're doing tests!' part of the output :)
** Attachment added:
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
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
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
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
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
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
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
*** This bug is a duplicate of bug 1902469 ***
https://bugs.launchpad.net/bugs/1902469
** This bug has been marked a duplicate of bug 1902469
drm/i915/dp_mst - System would hang during the boot up.
--
You received this bug notification because you are a member of Kernel
Packages, which
I can confirm the kernel in groovy-proposed fixes this issue:
# enable proposed
cat
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
There is a fix for this which will be in the OEM kernel -
https://bugs.launchpad.net/hwe-next/+bug/1902469 - and I am trying to
see if this can be merged for groovy as well -
https://lists.ubuntu.com/archives/kernel-team/2020-November/114483.html
--
You received this bug notification because you
FWIW I am seeing this also with my Lenovo X1 Carbon 6th when docked to
my Thinkpad Ultra Docking Station (that has 2 external monitors
connected to it). This booted fine on focal but after upgrading to
Groovy (or doing a fresh install) the boot hangs as soon as the plymouth
splash screen tries to
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
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
This is public in the Ubuntu CVE Tracker so making the bug public too.
** 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.
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
*** This bug is a duplicate of bug 1862865 ***
https://bugs.launchpad.net/bugs/1862865
Duping this against bug #1862865
** This bug has been marked a duplicate of bug 1862865
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
--
You received this bug notification because you are a
** Information type changed from Private Security 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/1856653
Title:
CVE-2019-0154 caused major power problem, pls backport
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1852300
Title:
xenial/linux-raspi2:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1852302
Title:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1852298
Title:
xenial/linux-kvm:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1852296
Title:
xenial/linux-aws:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1852248
Title:
disco/linux-oracle:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1852244
Title:
disco/linux-gcp:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1852241
Title:
bionic/linux-gcp:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1852236
Title:
disco/linux-aws:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1852233
Title:
disco/linux-raspi2:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Steve Beattie (sbeattie) => Ubuntu Security Team
(ubuntu-security)
** Changed in: kernel-sru-workflow/security-signoff
Assignee:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1852230
Title:
eoan/linux-oracle:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1852228
Title:
eoan/linux-kvm:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1852227
Title:
eoan/linux-gcp:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
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/1852225
Title:
eoan/linux-azure:
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1852223
Title:
eoan/linux-aws:
Lenovo upstream are aware of the issue and are looking to resolve it in
the BIOS for various models -
https://forums.lenovo.com/t5/Other-Linux-Discussions/X1C6-T480s-low-
cTDP-and-trip-temperature-in-Linux/m-p/4513821/highlight/true#M13563
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
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
See the attached log showing a successful build of glibc from bionic on
the launchpad staging build farm running the proposed kernel
(4.4.0-155).
** Attachment added:
"buildlog_ubuntu-bionic-i386.glibc_2.27-3ubuntu1_BUILDING.txt.gz"
Reassigning to the ubuntu-cve-tracker project since this is the relevant
project
** Package changed: linux (Ubuntu) => ubuntu-cve-tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Seth - the reason this is targeted against xenial is that the launchpad
builders are running the 4.4 xenial kernel - and so glibc *from eoan-
proposed* FTBFS when building on launchpad - and it would appear to be
as a result of this change. Oddly, I cannot reproduce the same failure
locally using
** Tags removed: eoan
--
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/1834315
Title:
Revert x86/vdso linker changes from #1830890 as this causes glibc
2.29-0ubuntu3 FTBFS on eoan
** 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/1834315
Title:
Revert x86/vdso linker changes from #1830890 as this
Public bug reported:
[Impact]
As reported in #1833067 and
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/comments/7 some
glibc testcases are still regressing on i386 after applying both the following
commits:
commit 379d98ddf41344273d9718556f761420f4dc80b3
Author: Alistair
** 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/1025525
Title:
DRM buffer permission model is inadequate
Status in
Sounds like this is a kernel bug / change which has caused this -
reassigning.
** Changed in: indicator-sensors
Status: New => Invalid
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Public bug reported:
[Impact]
* Currently it is not possible to use the SLB9670 TPM module with
Ubuntu Core since we do not ship the required devicetree overlay to
enable it
https://github.com/raspberrypi/linux/commit/c28ac2dc08bd73963f953a757a3362c64b5524ed
and there is no way for snaps to
This looks a lot like #1783110
** Information type changed from Private Security to Public
** Information type changed from Public to Private Security
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Kernel
The /boot partition is full (see Df.txt attached in comment #1)
--
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/1787932
Title:
package linux-image-4.4.0-133-generic (not installed)
92 matches
Mail list logo
