[Kernel-packages] [Bug 2061894] Re: package linux-image-6.8.0-22-generic 6.8.0-22.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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 dkms in Ubuntu. https://bugs.launchpad.net/bugs/2061894 Title: package linux-image-6.8.0-22-generic 6.8.0-22.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: After installing the Nvidia driver, the error was reported. The card is nvidia quadro p3200 and the driver is Nvidia-driver-550. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:opi3942 F pipewire /dev/snd/controlC0: opi3945 F wireplumber /dev/snd/controlC1: opi3945 F wireplumber CRDA: N/A CasperMD5CheckResult: pass Date: Tue Apr 16 20:58:41 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2024-04-05 (12 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 005: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Precision 7530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.12-1ubuntu7 SourcePackage: dkms Title: package linux-image-6.8.0-22-generic 6.8.0-22.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to noble on 2024-04-15 (1 days ago) dmi.bios.date: 01/28/2024 dmi.bios.release: 1.33 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.33.0 dmi.board.name: 07NCNV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.33.0:bd01/28/2024:br1.33:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn07NCNV:rvrA00:cvnDellInc.:ct10:cvr:sku0831: dmi.product.family: Precision dmi.product.name: Precision 7530 dmi.product.sku: 0831 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2061894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038514] Re: NVIDIA CVE-2023-{31018|31022}
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.
https://bugs.launchpad.net/bugs/2038514
Title:
NVIDIA CVE-2023-{31018|31022}
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
New
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Lunar:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Lunar:
Fix Released
Status in nvidia-graphics-drivers-525 source package in Lunar:
Fix Released
Status in nvidia-graphics-drivers-525-server source package in Lunar:
Fix Released
Status in nvidia-graphics-drivers-535 source package in Lunar:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Lunar:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Mantic:
Fix Released
Status in nvidia-graphics-drivers-525 source package in Mantic:
Fix Released
Status in nvidia-graphics-drivers-525-server source package in Mantic:
Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
Fix Released
Bug description:
NVIDIA CVE-2023-31018, NVIDIA CVE-2023-31022
https://nvidia.custhelp.com/app/answers/detail/a_id/5491
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2038514/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036143] Re: out-of-bounds error
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 privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.
** 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/2036143
Title:
out-of-bounds error
Status in linux package in Ubuntu:
New
Bug description:
kernel boots OK, but there are these errors at log (dmesg). I am not
sure this may be a security hole or not, that`s why i mark this bug as
if it is:
elhoir@elhoir-sobremesa:~$ sudo dmesg | grep bounds
[sudo] contraseña para elhoir:
[ 13.059453] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/sound/pci/ctxfi/ctamixer.c:346:48
[ 13.059520] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 17.146799] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3669:4
[ 17.146828] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 17.149755] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
[ 17.149775] __ubsan_handle_out_of_bounds+0xc6/0x110
elhoir@elhoir-sobremesa:~$
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-12-03 (333 days ago)
InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
IwConfig:
lono wireless extensions.
enp34s0 no wireless extensions.
virbr0no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=7601c1d1-2a20-422f-9131-05f4a4b73984 ro quiet splash
amd_pstate=active vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
RfKill:
Tags: mantic
Uname: Linux 6.5.0-10-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-07-23 (101 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/03/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.D0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A520M PRO (MS-7D14)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.D0:bd03/03/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D14:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA520MPRO(MS-7D14):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7D14
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036143/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
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 package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: New Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. IPSec OpenVPN Strongswan are much better alternatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040194] Re: apparmor restricts read access of user namespace mediation sysctls to root
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, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2040194 Title: apparmor restricts read access of user namespace mediation sysctls to root Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: lxc and lxd currently need to determine if the apparmor restriction on unprivileged user namespaces are being enforced, so that apparmor restrictions won't break lxc/d, and they won't clutter the logs by doing something like unshare true to test if the restrictions are being enforced. Ideally access to this information would be restricted so that any unknown access would be logged, but lxc/d currently aren't ready for this so in order to _not_ force lxc/d to probe whether enforcement is enabled, open up read access to the sysctls for unprivileged user namespace mediation. https://github.com/canonical/lxd/issues/11920#issuecomment-1756110109 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
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 overrides. See local/README for details.
include if exists
}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2017980
Title:
FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Status in OEM Priority Project:
New
Status in linux-meta-nvidia-5.19 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Bug description:
With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I
experience that google-chrome crashes.
It shows
```shell
[11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . :
Permission denied (13)
Trace/breakpoint trap (core dumped)".
```
To be honest I don't think it has anything to do with google-chrome at all.
When google-chrome starts it (normally) request the system key-manager
(KWallet in my case) for access to the users keys before it actually shows
anything from chrome. Not even that part (the KWallet password box) shows up.
I can only reproduce this problem with this specific kernel. It should
be possible to take google-chrome out of the equation by using another
application that starts by request the desktop key manager for access.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-nvidia-5.19 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92
Uname: Linux 5.15.0-1023-nvidia x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri Apr 28 11:23:23 2023
InstallationDate: Installed on 2016-01-08 (2666 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: linux-meta-nvidia-5.19
UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2017980/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024331] Re: Bluetooth fails to work after updating to linux-image-6.2.0-23-generic
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 notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024331 Title: Bluetooth fails to work after updating to linux-image-6.2.0-23-generic Status in linux package in Ubuntu: Incomplete Bug description: 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 -b-3 --grep hci0 --output short-monotonic | cut -c16-) <(journalctl -b0 --grep hci0 --output short-monotonic | cut -c16-) 12c12 < graphene kernel: Bluetooth: hci0: Firmware loaded in 1969096 usecs --- > graphene kernel: Bluetooth: hci0: Firmware loaded in 2052363 usecs 14c14 < graphene kernel: Bluetooth: hci0: Device booted in 14754 usecs --- > graphene kernel: Bluetooth: hci0: Device booted in 14605 usecs 19c19,22 < graphene bluetoothd[3532]: /org/bluez/hci0/dev_88_C9_E8_CE_3C_22/sep1/fd0: fd(44) ready --- > graphene kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 > graphene kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110) > graphene kernel: Bluetooth: hci0: unexpected event for opcode 0x0c03 > graphene kernel: Bluetooth: hci0: Intel version event size mismatch This looks similar to https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2019723 but I am filing a separate bug since that doesn't appear to have any traction. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-23-generic 6.2.0-23.23 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 19 10:31:38 2023 InstallationDate: Installed on 2021-08-03 (684 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) MachineType: LENOVO 20XWCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=igfx_off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-23-generic N/A linux-backports-modules-6.2.0-23-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-01-27 (142 days ago) dmi.bios.date: 04/05/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET84W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET84W(1.60):bd04/05/2023:br1.60:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024331] [NEW] Bluetooth fails to work after updating to linux-image-6.2.0-23-generic
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 -b-3 --grep hci0 --output short-monotonic | cut -c16-) <(journalctl -b0 --grep hci0 --output short-monotonic | cut -c16-) 12c12 < graphene kernel: Bluetooth: hci0: Firmware loaded in 1969096 usecs --- > graphene kernel: Bluetooth: hci0: Firmware loaded in 2052363 usecs 14c14 < graphene kernel: Bluetooth: hci0: Device booted in 14754 usecs --- > graphene kernel: Bluetooth: hci0: Device booted in 14605 usecs 19c19,22 < graphene bluetoothd[3532]: /org/bluez/hci0/dev_88_C9_E8_CE_3C_22/sep1/fd0: fd(44) ready --- > graphene kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 > graphene kernel: Bluetooth: hci0: Failed to read MSFT supported features > (-110) > graphene kernel: Bluetooth: hci0: unexpected event for opcode 0x0c03 > graphene kernel: Bluetooth: hci0: Intel version event size mismatch This looks similar to https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2019723 but I am filing a separate bug since that doesn't appear to have any traction. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-23-generic 6.2.0-23.23 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 19 10:31:38 2023 InstallationDate: Installed on 2021-08-03 (684 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) MachineType: LENOVO 20XWCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=igfx_off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-23-generic N/A linux-backports-modules-6.2.0-23-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-01-27 (142 days ago) dmi.bios.date: 04/05/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET84W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET84W(1.60):bd04/05/2023:br1.60:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- 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/2024331 Title: Bluetooth fails to work after updating to linux-image-6.2.0-23-generic Status in linux package in Ubuntu: New Bug description: 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 -b-3 --grep hci0 --output short-monotonic | cut -c16-) <(journalctl -b0 --grep hci0 --output short-monotonic | cut -c16-) 12c12 < graphene kernel: Bluetooth: hci0: Firmware loaded in 1969096 usecs --- > graphene kernel: Bluetooth: hci0: Firmware loaded in 2052363 usecs 14c14 < graphene kernel: Bluetooth: hci0: Device booted in 14754 usecs --- > graphene kernel: Bluetooth: hci0: Device booted in 14605 usecs 19c19,22 < graphene bluetoothd[3532]: /org/bluez/hci0/dev_88_C9_E8_CE_3C_22/sep1/fd0: fd(44) ready --- > graphene kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 > graphene kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110) > graphene kernel: Bluetooth: hci0: unexpected event for opcode 0x0c03 > graphene kernel: Bluetooth: hci0: Intel version event size mismatch This looks similar to https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2019723 but I am filing a separate bug since that doesn't appear to have any traction. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-23-generic 6.2.0-23.23 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
[Kernel-packages] [Bug 2024004] Re: package linux-image-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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 dkms in Ubuntu. https://bugs.launchpad.net/bugs/2024004 Title: package linux-image-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: I have no idea! ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Thu Jun 15 20:09:23 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-04-30 (45 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=c9812ea5-9708-43a1-b64a-4a17d336d214 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: dkms Title: package linux-image-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2018 dmi.bios.release: 15.87 dmi.bios.vendor: Insyde dmi.bios.version: F.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2296 dmi.board.vendor: Hewlett-Packard dmi.board.version: 78.21 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 78.33 dmi.modalias: dmi:bvnInsyde:bvrF.57:bd11/09/2018:br15.87:efr78.33:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097A12005F1600080:rvnHewlett-Packard:rn2296:rvr78.21:cvnHewlett-Packard:ct10:cvrChassisVersion:skuL1K08PA#UUF: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: L1K08PA#UUF dmi.product.version: 097A12005F1600080 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2024004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023958] Re: blue tooth is not working
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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/2023958 Title: blue tooth is not working Status in linux package in Ubuntu: New Bug description: blue tooth is not working in ubuntu 18.04 system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012789] Re: blacklist: Problem blacklisting hash (-13)
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 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/2012789 Title: blacklist: Problem blacklisting hash (-13) Status in linux package in Ubuntu: New Bug description: [0.794819] Key type blacklist registered [4.860504] blacklist: Loading compiled-in revocation X.509 certificates [4.916587] blacklist: Problem blacklisting hash (-13) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
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 are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000491] Re: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non-recoverable after screen lock and screen completely fades to black or after system goes into slee
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 are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2000491 Title: Dell Latitude 7390 running Ubuntu 18.04.6 fresh install system non- recoverable after screen lock and screen completely fades to black or after system goes into sleep Status in linux-hwe-5.4 package in Ubuntu: Invalid Bug description: This is a fresh install of Ubuntu 18.04.6 on Dell Latitude 7390. The system is non-recoverable after it goes into sleep. Or after the screen is locked by the user and after it fades to complete black. System becomes unresponsive, no mouse or keypress will get the system back on to work. If the systemctl suspend is issued, the system will not wake up again. Hard reset is needed. If Ubuntu 18.04.6 is booted from live USB, the same is happening. Sometimes, when the system is rendered unresponsive as a result of any of the above, the power led is sending the message of "processor failure" (2 x amber blinks followed by 1 x white blink). Any help is greatly appreciated! I will keep the system as is, without applying any updates for now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 27 01:13:12 2022 InstallationDate: Installed on 2022-12-26 (0 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2000491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown
** 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 package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992580] Re: i915 DG1 fails to load
*** 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 Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992580 Title: i915 DG1 fails to load Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-12-06 (674 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Tags: wayland-session kinetic Uname: Linux 5.19.0-19-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991691] Re: cannot change mount namespace
** 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: New Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991704] Re: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
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 notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991704 Title: Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen Status in linux package in Ubuntu: Triaged Bug description: After today's Kinetic update my Framework laptop won't boot. The boot hangs after this output: [0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci :00:07.1: DPC: RP PIO log size 8 is invalid [0.815754] pci :00:07.2: DPC: RP PIO log size 8 is invalid 0.816732] pci :00:07.3: DPC: RP PIO log size 0 is invalid [2.001649] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling inst ead Falling back to 5.19.0-15-generic works. My Thinkpad X1 Carbon 6th gen does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik4014 F wireplumber /dev/snd/seq:jik4009 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 4 13:55:09 2022 InstallationDate: Installed on 2022-09-17 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Framework Laptop (12th Gen Intel Core) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-02 (1 days ago) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA423350021 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992320] Re: boot hangs with 5.19.0.19.19
*** 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 notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992320 Title: boot hangs with 5.19.0.19.19 Status in linux package in Ubuntu: New Bug description: 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 with my laptop docked via a Thinkpad Thunderbolt 3 dock or when undocked. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.19.19 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 10 16:25:52 2022 InstallationDate: Installed on 2021-08-03 (433 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) MachineType: LENOVO 20XWCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=igfx_off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-08-27 (44 days ago) dmi.bios.date: 08/29/2022 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET80W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET80W(1.56):bd08/29/2022:br1.56:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992320] [NEW] boot hangs with 5.19.0.19.19
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 with my laptop docked via a Thinkpad Thunderbolt 3 dock or when undocked. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.19.19 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 10 16:25:52 2022 InstallationDate: Installed on 2021-08-03 (433 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) MachineType: LENOVO 20XWCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=igfx_off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-08-27 (44 days ago) dmi.bios.date: 08/29/2022 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET80W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET80W(1.56):bd08/29/2022:br1.56:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1992320 Title: boot hangs with 5.19.0.19.19 Status in linux package in Ubuntu: New Bug description: 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 with my laptop docked via a Thinkpad Thunderbolt 3 dock or when undocked. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-generic 5.19.0.19.19 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 10 16:25:52 2022 InstallationDate: Installed on 2021-08-03 (433 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) MachineType: LENOVO 20XWCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=igfx_off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-08-27 (44 days ago) dmi.bios.date: 08/29/2022 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET80W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET80W(1.56):bd08/29/2022:br1.56:efr1.33:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1
[Kernel-packages] [Bug 1990090] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed on Bionic 4.15
@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.
https://bugs.launchpad.net/bugs/1990090
Title:
test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
on Bionic 4.15
Status in QA Regression Testing:
New
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Incomplete
Bug description:
Issue found with Bionic 4.15.0-194.205
Test failed with:
Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel:
'4.15.0-194.205 (Ubuntu 4.15.0-194.205-generic 4.15.18)' arch: 'amd64' uid: 0/0
SUDO_USER: 'ubuntu')
test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754) ... FAIL
==
FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2976, in
test_520_config_random_trust_cpu
self.assertKernelConfig('RANDOM_TRUST_CPU', expected)
File "./test-kernel-security.py", line 233, in assertKernelConfig
self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 224, in assertKernelConfigUnset
'%s option was expected to be unset in the kernel config' % name)
AssertionError: RANDOM_TRUST_CPU option was expected to be unset in the
kernel config
--
Ran 1 test in 0.003s
FAILED (failures=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1990090/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes
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-
kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-
next=30bce26855c9171f8dee74d93308fd506730c914
The logic here:
int aa_profile_ns_perm(struct aa_profile *profile, struct common_audit_data *sa,
u32 request)
{
...
if (profile_unconfined(profile)) {
if (!unprivileged_userns_restricted ||
ns_capable_noaudit(current_user_ns(), CAP_SYS_ADMIN))
return 0;
aad(sa)->info = "User namespace creation restricted";
/* fall through to below allows complain mode to override */
} else {
struct aa_ruleset *rules = list_first_entry(>rules,
typeof(*rules),
list);
aa_state_t state;
state = RULE_MEDIATES(rules, aad(sa)->class);
if (!state)
/* TODO: add flag to complain about unmediated */
return 0;
perms = *aa_lookup_perms(>policy, state);
}
aa_apply_modes_to_perms(profile, );
return aa_check_perms(profile, , request, sa, audit_ns_cb);
}
Seems to indicate that all unconfined processes that do not have
CAP_SYS_ADMIN will be denied the ability to use user namespaces - this
feels like a definite regression / policy change within the kernel
itself.
Should the kernel instead be built with
CONFIG_SECURITY_APPARMOR_RESTRICT_USERNS=n ?
Or is this code not doing what it was intended to do.
** 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/1990064
Title:
unconfined profile denies userns_create for chromium based processes
Status in apparmor package in Ubuntu:
New
Status in linux package in Ubuntu:
New
Bug description:
For Ubuntu 22.10, since the last kernel update, i can´t launch any
chromium based browser, due to apparmor denying userns_create
dmesg shows:
apparmor="DENIED" operation="userns_create" class="namespace" info="User
namespace creation restricted" error=-13 profile="unconfined" pid=21323
comm="steamwebhelper" requested="userns_create" denied="userns_create"
This happens for every process which uses a chromium engine, like
google chrome itself or in this case steamwebhelper.
Might be related to this change?:
https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/
not sure if it got merged in this form though..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973574] Re: The system has become much choppier and no audio is being heard
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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/1973574 Title: The system has become much choppier and no audio is being heard Status in linux package in Ubuntu: Confirmed Bug description: The system has been getting choppy and the last upgrade is a failure.Also the sound is not coming even though the video is being played. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-110-generic 5.4.0-110.124 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 16 12:59:42 2022 InstallationDate: Installed on 2021-10-27 (200 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-110-generic root=UUID=5b9e5e8a-d7f3-42fd-9895-dd751e39ce69 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-110-generic N/A linux-backports-modules-5.4.0-110-generic N/A linux-firmware 1.187.30 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd01/25/2018:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 2EY84PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-10-28T20:41:46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968556] Re: nvidia-kernel-source-465 465.27-0ubuntu0.20.04.2: nvidia kernel module failed to build
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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 nvidia-graphics-drivers-465 in Ubuntu. https://bugs.launchpad.net/bugs/1968556 Title: nvidia-kernel-source-465 465.27-0ubuntu0.20.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-465 package in Ubuntu: New Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-465 (not installed) ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-39-generic Date: Mon Apr 11 06:37:30 2022 DuplicateSignature: dkms:nvidia-kernel-source-465:465.27-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/465.27/build/nvidia-drm/nvidia-drm-crtc.c:454:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-06-28 (286 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 465.27-0ubuntu0.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-465 Title: nvidia-kernel-source-465 465.27-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1968556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968402] Re: Ubuntu 20.04.3 boots to black screen, no TTY available
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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 nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1968402 Title: Ubuntu 20.04.3 boots to black screen, no TTY available Status in gdm: New Status in gnome-session: New Status in grub: New Status in os-prober-efi/trunk: New Status in shim: New Status in subiquity: New Status in tty: New Status in grub2 package in Ubuntu: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-450 package in Ubuntu: New Status in wayland package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: A fresh attempted install failed utterly, just as 20.04.1 failed two years ago. Has anyone been paying attention? Ubuntu 20.04.3 burned just now to a USB stick and attempted to be installed. The first fail was that the stick booted to a couple of impenetrable boot-time messages and hung. Really. I'm not making this up. It didn't just open the installer, as it should. The second fail was having just to guess that rebooting and trying another GRUB menu option might work and give that a try. Really. I'm not making this up, either. The installer was entirely incapable of providing any direction The third failure was that the installer was incapable of detecting the video configuration and proceeding accordingly. This is 20.04.3, the third attempt at getting this right, and it still fails. The fourth fail was an error message insisting on a designation of where root should be, even after the destination partition already had been specified. The fifth failure was that no obvious means existed to satisfy the installer about the root specification, which of course already had been made by specifying the destination partition. All one could do was to see whether a context menu existed for any object on the screen that might possibly drill down through a few layers to something approximating what the content of the error message suggested. The sixth failure was that no GRUB menu appeared during boot, notwithstanding that the EFI system partition had clearly been identified in the installer. The seventh failure was that the machine booted only to a black screen with a non-blinking _ midway toward the upper left. No login screen/display manager. No GUI at all. Just this little _. The eighth failure was that Ctrl-alt-f2, ctrl-alt-f5-f12 have no effect. No TTY is available. There is no way whatsoever to interact with the system. Expected behavior: The software would install and the computer would work. Actual behavior: The installer bricked my workstation. Obviously, no debug information is available BECAUSE THE SOFTWARE FAILED. This post is being made from a borrowed Windows laptop. Any thoughts about how to get a working system would be appreciated. I am not optimistic about the prospects for 22.04. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1968402/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967840] Re: System is super breached and many things are changing and specially in chromium based applications
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 https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: linux (Ubuntu) Status: New => 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/1967840 Title: System is super breached and many things are changing and specially in chromium based applications Status in linux package in Ubuntu: Invalid Bug description: System is super breached and many things are changing and specially in chromium based applications ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnm 2691 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 10:29:10 2022 MachineType: Hewlett-Packard HP ProBook 4540s ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=UUID=cf164159-2e29-4cee-aef2-f8d16c319f1a ro quiet splash crashkernel=512M-:192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2019 dmi.bios.release: 15.104 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.68 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.21 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 88.33 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.68:bd04/11/2019:br15.104:efr88.33:svnHewlett-Packard:pnHPProBook4540s:pvrA1008C11:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:skuB7A48EA#ABV: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 4540s dmi.product.sku: B7A48EA#ABV dmi.product.version: A1008C11 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
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 off/disconnect when the lid is closed Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
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 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 off/disconnect when the lid is closed Status in gnome-settings-daemon package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: After today's updates I can no longer run my Laptop in clam shell mode. I don't use a dock. I connect the second monitor via HDMI cable and and external keyboard/mouse via a USB hub. Usually I can just plugin the monitor and close the lid and the primary display will switch to the external monitor. Now it will default to Monitor 2 as part of the joint display. I also tested booting the machine and closing the lid but this still defaulted to the external monitor as the 2nd display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 16:44:37 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2226] InstallationDate: Installed on 2022-02-23 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) MachineType: LENOVO 20CLS3JN0F ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2015 dmi.bios.release: 1.7 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET30W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS3JN0F dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250: dmi.product.family: ThinkPad X250 dmi.product.name: 20CLS3JN0F dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961476] Re: The laptop turns off only through the button and won't wake up from sleep (black screen)
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1961476 Title: The laptop turns off only through the button and won't wake up from sleep (black screen) Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: A complete shutdown of the laptop occurs only with the help of the shutdown button. If this is not done, then the keyboard backlight and fans work, and the screen itself is turned off. And also the sleep mode does not work (black screen and no reaction), you have to turn it off with a button to get out of it. The problem has been observed since ubuntu version 20.04 and the BIOS update. These problems are not observed in Windows OS. The video card is no longer displayed as nvidia in both operating systems, now it is displayed only asMesa Intel® UHD Graphics 630 (CFL GT2). I didn't reboot myself before, apparently the kernel was fixed. Thanks to the developers, that now he at least reboots himself. It remains to solve the issue with the shutdown. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 19 14:35:10 2022 InstallationDate: Installed on 2022-02-01 (17 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) Product Name: G7 7790 BIOS Information Vendor: Dell Inc. Version: 1.14.0 10/20/2020 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eve1634 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-02-01 (17 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. G7 7790 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=72a43957-07b7-4ade-9aa6-30aede661648 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-30-generic N/A linux-backports-modules-5.13.0-30-generic N/A linux-firmware 1.187.26 Tags: focal Uname: Linux 5.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0PJ0RG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 6564055862 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd10/20/2020:br1.14:svnDellInc.:pnG77790:pvr:rvnDellInc.:rn0PJ0RG:rvrA00:cvnDellInc.:ct10:cvr:sku08EC: dmi.product.family: GSeries dmi.product.name: G7 7790 dmi.product.sku: 08EC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1961476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912371] Re: [MIR] flashrom + libftdi
** 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: New Status in libftdi1 package in Ubuntu: New Bug description: [Summary] Further review will be needed. The Package does not have a test suite that runs as autopkgtest. [Availability] Currently in universe. [Duplication] There is no other package in main providing the same functionality. [Rationale] fwupd depends on libflashrom1 for its flashrom plugin, something that's required to update Coreboot firmware. [Security] No CVE's, but due to the nature of the package security should review. [Quality Assurance] Package builds and runs easily [Dependencies] N/A [Standards Compliance] Complies with FHS, though the organization of files in the source package could be organized better. [Common blockers] flashrom does NOT have a test suite that runs at build time. flashrom does NOT have a test suite that runs as autopkgtest. [Maintenance] Actively maintained - https://github.com/flashrom/flashrom Packaging - https://salsa.debian.org/myczko-guest/flashrom.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912371] security audit
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 machine - this can include the UEFI BIOS or optionROMs plus other devices like NICs etc. - No CVE History - Relevant Build-Depends: - libpci-dev, libusb-1.0-0-dev, libftdi1-dev - No pre/post inst/rm scripts - No init scripts - No systemd units - No dbus services - No setuid binaries - 1 binary in PATH - /usr/sbin/flashrom - No sudo fragments - No polkit files - 1 udev rules - Grants read/write access to the various specific USB devices for users in the plugdev group - Includes unit tests run during build and autopkgtests to do more system-level testing via dummy devices - No cron jobs - Build logs: - No significant warnings during the build other than the following lintian issues: E: libflashrom1: symbols-file-contains-current-version-with-debian-revision on symbol LIBFLASHROM_1.0@LIBFLASHROM_1.0 and 23 others W: flashrom: appstream-metadata-missing-modalias-provide lib/udev/rules.d/60-flashrom.rules W: flashrom source: illegal-runtime-test-name emulated_programmer.sh in line 1 - Processes spawned - Uses popen() to call dmidecode() to read various hard-coded identifiers - as these are hard-coded there is no chance for these to be used for command injection so whilst this is a bit ugly it is safe. - Memory management - Being written in C there is a lot of dynamic memory management via malloc, realloc and free etc - but in general these seem quite defensive, with return values being checked and no instances that I could see with obvious chance for integer overflow when calculating sizes to allocate etc. - File IO - Opens and reads from a number of hard-coded paths or from paths as specified via command-line arguments - Can dump out to a user-specified path as well - Logging - Lots of printf() style logging but again this looks pretty defensive - No environment variable usage - Uses various privileged ioctl() calls so likely would need to be run as root in these cases but again I don't see any obvious chance to abuse this - No use of cryptography / random number sources - No use of temp files - Use of networking - Supports connecting to a remote serial programmer over TCP/IP - this is treated as trusted like a real device - No use of WebKit - No use of PolicyKit - No significant cppcheck/coverity results flashrom appears to be reasonably defensively written and does not have a history of security issues, whilst the upstream project seems relatively healthy so should likely be responsive and supporting for any potential future security issues. Security team ACK for promoting flashrom to main assuming this includes the changes from comment:14 above - can the lintian issues highlighted earlier please be investigated? ** Tags added: security-review-done ** Changed in: flashrom (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- 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: New Status in libftdi package in Ubuntu: New Bug description: [Summary] Further review will be needed. The Package does not have a test suite that runs as autopkgtest. [Availability] Currently in universe. [Duplication] There is no other package in main providing the same functionality. [Rationale] fwupd depends on libflashrom1 for its flashrom plugin, something that's required to update Coreboot firmware. [Security] No CVE's, but due to the nature of the package security should review. [Quality Assurance] Package builds and runs easily [Dependencies] N/A [Standards Compliance] Complies with FHS, though the organization of files in the source package could be organized better. [Common blockers] flashrom does NOT have a test suite that runs at build time. flashrom does NOT have a test suite that runs as autopkgtest. [Maintenance] Actively maintained - https://github.com/flashrom/flashrom Packaging - https://salsa.debian.org/myczko-guest/flashrom.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912371] Re: [MIR] flashrom + libftdi
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 LTO - so in this case, the original functions get called, not the wrapped ones - https://bugzilla.redhat.com/show_bug.cgi?id=1693831 I can't find an easy way to only disable LTO for these tests so perhaps just best to set DEB_BUILD_MAINT_OPTIONS = optimize=-lto in debian/rules for now. As such, I will proceed with the security audit based on this for now. ** Bug watch added: github.com/flashrom/flashrom/issues #186 https://github.com/flashrom/flashrom/issues/186 ** Bug watch added: Red Hat Bugzilla #1693831 https://bugzilla.redhat.com/show_bug.cgi?id=1693831 -- 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: New Status in libftdi package in Ubuntu: New Bug description: [Summary] Further review will be needed. The Package does not have a test suite that runs as autopkgtest. [Availability] Currently in universe. [Duplication] There is no other package in main providing the same functionality. [Rationale] fwupd depends on libflashrom1 for its flashrom plugin, something that's required to update Coreboot firmware. [Security] No CVE's, but due to the nature of the package security should review. [Quality Assurance] Package builds and runs easily [Dependencies] N/A [Standards Compliance] Complies with FHS, though the organization of files in the source package could be organized better. [Common blockers] flashrom does NOT have a test suite that runs at build time. flashrom does NOT have a test suite that runs as autopkgtest. [Maintenance] Actively maintained - https://github.com/flashrom/flashrom Packaging - https://salsa.debian.org/myczko-guest/flashrom.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912371] Re: [MIR] flashrom + libftdi
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: "flashrom_1.2-5ubuntu1_amd64-2021-05-19T04:46:52Z.build" https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+attachment/5498638/+files/flashrom_1.2-5ubuntu1_amd64-2021-05-19T04%3A46%3A52Z.build -- 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: New Status in libftdi package in Ubuntu: New Bug description: [Summary] Further review will be needed. The Package does not have a test suite that runs as autopkgtest. [Availability] Currently in universe. [Duplication] There is no other package in main providing the same functionality. [Rationale] fwupd depends on libflashrom1 for its flashrom plugin, something that's required to update Coreboot firmware. [Security] No CVE's, but due to the nature of the package security should review. [Quality Assurance] Package builds and runs easily [Dependencies] N/A [Standards Compliance] Complies with FHS, though the organization of files in the source package could be organized better. [Common blockers] flashrom does NOT have a test suite that runs at build time. flashrom does NOT have a test suite that runs as autopkgtest. [Maintenance] Actively maintained - https://github.com/flashrom/flashrom Packaging - https://salsa.debian.org/myczko-guest/flashrom.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927826] Re: package linux-headers-4.4.0-193 4.4.0-193.224 failed to install/upgrade: package linux-headers-4.4.0-193 is not ready for configuration cannot configure (current st
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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/1927826 Title: package linux-headers-4.4.0-193 4.4.0-193.224 failed to install/upgrade: package linux-headers-4.4.0-193 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: New Bug description: i don't have any details ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-193 4.4.0-193.224 ProcVersionSignature: Ubuntu 4.4.0-203.235-generic 4.4.249 Uname: Linux 4.4.0-203-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bonnie 1647 F...m pulseaudio /dev/snd/controlC0: bonnie 1647 F pulseaudio Date: Sat May 8 04:20:25 2021 DuplicateSignature: package:linux-headers-4.4.0-193:4.4.0-193.224 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package linux-headers-4.4.0-193 (--configure): package linux-headers-4.4.0-193 is not ready for configuration ErrorMessage: package linux-headers-4.4.0-193 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=3a013136-c7ad-4f26-8a47-c9d18a0cdb51 InstallationDate: Installed on 2017-12-28 (1227 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: DELL Inc. Studio XPS 435T/9000 PackageArchitecture: all ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-203-generic root=UUID=65964947-81b7-47d0-8ea8-365be049eda4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.29 RfKill: SourcePackage: linux Title: package linux-headers-4.4.0-193 4.4.0-193.224 failed to install/upgrade: package linux-headers-4.4.0-193 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2009 dmi.bios.vendor: DELL INC. dmi.bios.version: A13 dmi.board.name: 0X501H dmi.board.vendor: DELL Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: DELL Inc. dmi.modalias: dmi:bvnDELLINC.:bvrA13:bd07/28/2009:svnDELLInc.:pnStudioXPS435T/9000:pvr00:rvnDELLInc.:rn0X501H:rvrA02:cvnDELLInc.:ct3:cvr: dmi.product.name: Studio XPS 435T/9000 dmi.product.version: 00 dmi.sys.vendor: DELL Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928114]
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 https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! -- 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/1928114 Title: Pi 400 freeze Status in linux package in Ubuntu: Invalid Bug description: My Raspberry Pi 400 became extremely slow, and a few minutes later freezed. By the way, it didn't happen on the current session, but on May 3rd, the system was pretty the same. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-1007.7-raspi 5.11.12 Uname: Linux 5.11.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: norb 1423 F pulseaudio /dev/snd/controlC1: norb 1423 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 11 17:36:34 2021 ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=E4:5F:01:08:E0:A1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-5.11.0-1007-raspi N/A linux-backports-modules-5.11.0-1007-raspi N/A linux-firmware 1.197 SourcePackage: linux StagingDrivers: vc_sm_cma bcm2835_isp bcm2835_mmal_vchiq bcm2835_v4l2 bcm2835_codec snd_bcm2835 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928114] Re: Pi 400 freeze
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Changed in: linux (Ubuntu) Status: New => 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/1928114 Title: Pi 400 freeze Status in linux package in Ubuntu: Invalid Bug description: My Raspberry Pi 400 became extremely slow, and a few minutes later freezed. By the way, it didn't happen on the current session, but on May 3rd, the system was pretty the same. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-1007.7-raspi 5.11.12 Uname: Linux 5.11.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: norb 1423 F pulseaudio /dev/snd/controlC1: norb 1423 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue May 11 17:36:34 2021 ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=E4:5F:01:08:E0:A1 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-5.11.0-1007-raspi N/A linux-backports-modules-5.11.0-1007-raspi N/A linux-firmware 1.197 SourcePackage: linux StagingDrivers: vc_sm_cma bcm2835_isp bcm2835_mmal_vchiq bcm2835_v4l2 bcm2835_codec snd_bcm2835 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910736] Re: package libnvidia-compute-390 (not installed) failed to install/upgrade: paylaşılan '/etc/OpenCL/vendors/nvidia.icd' dosyasının üzerine yazılmaya çalışılıyor, dosya
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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 nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910736 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: paylaşılan '/etc/OpenCL/vendors/nvidia.icd' dosyasının üzerine yazılmaya çalışılıyor, dosya libnvidia- compute-390:amd64 paketinin diğer örneklerinden farklı Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: nvidia problem ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 13:48:05 2021 ErrorMessage: paylaşılan '/etc/OpenCL/vendors/nvidia.icd' dosyasının üzerine yazılmaya çalışılıyor, dosya libnvidia-compute-390:amd64 paketinin diğer örneklerinden farklı InstallationDate: Installed on 2021-01-07 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: paylaşılan '/etc/OpenCL/vendors/nvidia.icd' dosyasının üzerine yazılmaya çalışılıyor, dosya libnvidia-compute-390:amd64 paketinin diğer örneklerinden farklı UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910665] Re: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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 nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910665 Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Wifi is not beeen working the update is not getting completed. Now what to do about it? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-390 390.138-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 12:03:49 2021 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-11-09 (59 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to focal on 2020-12-30 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911585] Re: ouchpad doesn't work properly after Ubuntu Installation
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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/1911585 Title: ouchpad doesn't work properly after Ubuntu Installation Status in linux package in Ubuntu: Confirmed Bug description: Touchpad' incorrectly detected in 'Lenovo s740' after the ubuntu installation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-60-generic 5.4.0-60.67 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: felipe 1451 F pulseaudio /dev/snd/pcmC0D0p: felipe 1451 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 13 21:52:13 2021 InstallationDate: Installed on 2021-01-07 (6 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: LENOVO 81RM ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-60-generic root=UUID=32be46bd-d75e-4c0e-a754-56d7e63881ba ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-60-generic N/A linux-backports-modules-5.4.0-60-generic N/A linux-firmware1.187.7 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-08 (5 days ago) dmi.bios.date: 07/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BYCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBYCN36WW:bd07/15/2020:svnLENOVO:pn81RM:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL: dmi.product.family: Yoga S740-14IIL dmi.product.name: 81RM dmi.product.sku: LENOVO_MT_81RM_BU_idea_FM_Yoga S740-14IIL dmi.product.version: Lenovo Yoga S740-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911835] Re: package linux-firmware 1.187.7 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1911835 Title: package linux-firmware 1.187.7 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: Upgraded from 18.04 to 20.04 without doing a clean install. Just started encountering issues with updates. I'm not sure if it's related to my encrypted swap which seems to have been broken/unreadable at some point in upgrading. Happy to provide more info. $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.7 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 10 22:02:00 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c InstallationDate: Installed on 2016-07-02 (1657 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 80K9 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.7 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-12-06 (39 days ago) dmi.bios.date: 07/21/2015 dmi.bios.vendor: Lenovo dmi.bios.version: A9CN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Edge 15 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Edge 15 dmi.modalias: dmi:bvnLenovo:bvrA9CN61WW:bd07/21/2015:svnLENOVO:pn80K9:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoEdge15: dmi.product.family: IDEAPAD dmi.product.name: 80K9 dmi.product.sku: LENOVO_MT_80K9_BU_idea_FM_Lenovo Edge 15 dmi.product.version: Lenovo Edge 15 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1911835/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel]
*** 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 is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays through the dock (HDMI and VGA). My system uses graphical boot via plymouth. Dell logo remains on screen while ubuntu loads into gdm3 (when it is booting normally). I'm using LUKS. This is a regression from focal and kernel 5.4. If I boot the laptop with the thunderbolt dock connected, the system will get past the Dell logo, go to a black screen and remain there. The screen is powered up as I can see some light on the edges. It won't boot up or respond to any keys. After force-shutdown via power key long press, on the next boot the grub menu will appear. The system will boot normally then (with the dock still connected). If I boot the system with the dock disconnected, it will correctly go into disk encryption password prompt. If at that point I connect the dock and wait without entering the password, the system will correctly set up the dock: the displays lit up and the mouse and keyboard plugged into it become active. The system boots normally. I'm trying to bisect in which kernel version this happened. I'll put results in a comment. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.25.30 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luis 3332 F pulseaudio /dev/snd/controlC0: luis 3332 F pulseaudio CasperMD5CheckResult: skip Date: Fri Oct 23 16:27:30 2020 InstallationDate: Installed on 2019-08-17 (432 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=/dev/mapper/vglinux-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-09 (13 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902469] Re: drm/i915/dp_mst - System would hang during the boot up.
I can confirm the kernel in groovy-proposed fixes this issue: # enable proposed cat
[Kernel-packages] [Bug 1904288] Re: package bluez 5.53-0ubuntu3 failed to install/upgrade: il sottoprocesso installato pacchetto bluez script post-installation ha restituito lo stato di errore 1
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1904288 Title: package bluez 5.53-0ubuntu3 failed to install/upgrade: il sottoprocesso installato pacchetto bluez script post-installation ha restituito lo stato di errore 1 Status in bluez package in Ubuntu: New Bug description: I seguenti pacchetti sono stati installati automaticamente e non sono più richiesti: libbluetooth3-dbg libfprint-2-tod1 libsbc1 linux-headers-5.4.0-47 linux-headers-5.4.0-47-generic linux-image-5.4.0-47-generic linux-modules-5.4.0-47-generic linux-modules-extra-5.4.0-47-generic Usare "sudo apt autoremove" per rimuoverli. I seguenti pacchetti saranno RIMOSSI: bluez* bluez-btsco* bluez-dbg* gnome-bluetooth* pulseaudio-module-bluetooth* 0 aggiornati, 0 installati, 5 da rimuovere e 93 non aggiornati. Dopo quest'operazione, verranno liberati 14,9 MB di spazio su disco. Continuare? [S/n] s (Lettura del database... 226489 file e directory attualmente installati.) Rimozione di pulseaudio-module-bluetooth (1:13.99.1-1ubuntu3.7)... Rimozione di gnome-bluetooth (3.34.1-1)... Rimozione di bluez-btsco (1:0.50-0ubuntu7)... Rimozione di bluez-dbg (5.53-0ubuntu3)... Rimozione di bluez (5.53-0ubuntu3)... Elaborazione dei trigger per mime-support (3.64ubuntu1)... Elaborazione dei trigger per hicolor-icon-theme (0.17-2)... Elaborazione dei trigger per gnome-menus (3.36.0-1ubuntu1)... Elaborazione dei trigger per man-db (2.9.1-1)... Elaborazione dei trigger per dbus (1.12.16-2ubuntu2.1)... Elaborazione dei trigger per desktop-file-utils (0.24-1ubuntu3)... (Lettura del database... 226307 file e directory attualmente installati.) Eliminazione dei file di configurazione di bluez (5.53-0ubuntu3)... dpkg: attenzione: nel rimuovere bluez, la directory "/var/lib/bluetooth" è risul tata non vuota e non viene rimossa Elaborazione dei trigger per dbus (1.12.16-2ubuntu2.1)... Elaborazione dei trigger per systemd (245.4-4ubuntu3.2)... Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze Lettura informazioni sullo stato... Fatto I seguenti pacchetti sono stati installati automaticamente e non sono più richiesti: libbluetooth3-dbg libfprint-2-tod1 libsbc1 linux-headers-5.4.0-47 linux-headers-5.4.0-47-generic linux-image-5.4.0-47-generic linux-modules-5.4.0-47-generic linux-modules-extra-5.4.0-47-generic Usare "sudo apt autoremove" per rimuoverli. I seguenti pacchetti NUOVI saranno installati: bluez 0 aggiornati, 1 installati, 0 da rimuovere e 93 non aggiornati. È necessario scaricare 981 kB di archivi. Dopo quest'operazione, verranno occupati 4.910 kB di spazio su disco. Scaricamento di:1 http://it.archive.ubuntu.com/ubuntu focal/main amd64 bluez amd64 5.53-0ubuntu3 [981 kB] Recuperati 981 kB in 1s (985 kB/s) Selezionato il pacchetto bluez non precedentemente selezionato. (Lettura del database... 226300 file e directory attualmente installati.) Preparativi per estrarre .../bluez_5.53-0ubuntu3_amd64.deb... Estrazione di bluez (5.53-0ubuntu3)... Configurazione di bluez (5.53-0ubuntu3)... Created symlink /etc/systemd/system/dbus-org.bluez.service → /lib/systemd/system /bluetooth.service. Created symlink /etc/systemd/system/bluetooth.target.wants/bluetooth.service → / lib/systemd/system/bluetooth.service. Job for bluetooth.service failed because the control process exited with error c ode. See "systemctl status bluetooth.service" and "journalctl -xe" for details. invoke-rc.d: initscript bluetooth, action "start" failed. ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pres et: enabled) Drop-In: /etc/systemd/system/bluetooth.service.d └─override.conf Active: activating (auto-restart) (Result: exit-code) since Sat 2020-11-14 16:59:04 CET; 21ms ago Docs: man:bluetoothd(8) Process: 14788 ExecStart=/usr/lib/bluetooth/bluetoothd --debug -n (code=exit ed, status=1/FAILURE) Main PID: 14788 (code=exited, status=1/FAILURE) Status: "Starting up" dpkg: errore nell'elaborare il pacchetto bluez (--configure): il sottoprocesso installato pacchetto bluez script post-installation ha restitu ito lo stato di errore 1 Elaborazione dei trigger per systemd (245.4-4ubuntu3.2)... Elaborazione dei trigger per
[Kernel-packages] [Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel]
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 are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays through the dock (HDMI and VGA). My system uses graphical boot via plymouth. Dell logo remains on screen while ubuntu loads into gdm3 (when it is booting normally). I'm using LUKS. This is a regression from focal and kernel 5.4. If I boot the laptop with the thunderbolt dock connected, the system will get past the Dell logo, go to a black screen and remain there. The screen is powered up as I can see some light on the edges. It won't boot up or respond to any keys. After force-shutdown via power key long press, on the next boot the grub menu will appear. The system will boot normally then (with the dock still connected). If I boot the system with the dock disconnected, it will correctly go into disk encryption password prompt. If at that point I connect the dock and wait without entering the password, the system will correctly set up the dock: the displays lit up and the mouse and keyboard plugged into it become active. The system boots normally. I'm trying to bisect in which kernel version this happened. I'll put results in a comment. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.25.30 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luis 3332 F pulseaudio /dev/snd/controlC0: luis 3332 F pulseaudio CasperMD5CheckResult: skip Date: Fri Oct 23 16:27:30 2020 InstallationDate: Installed on 2019-08-17 (432 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=/dev/mapper/vglinux-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-09 (13 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads
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 display. Setting nospash in /etc/default/grub (GRUB_CMDLINE_LINUX_DEFAULT) works around this for now by disabling the splash screen. -- 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/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays through the dock (HDMI and VGA). My system uses graphical boot via plymouth. Dell logo remains on screen while ubuntu loads into gdm3 (when it is booting normally). I'm using LUKS. This is a regression from focal and kernel 5.4. If I boot the laptop with the thunderbolt dock connected, the system will get past the Dell logo, go to a black screen and remain there. The screen is powered up as I can see some light on the edges. It won't boot up or respond to any keys. After force-shutdown via power key long press, on the next boot the grub menu will appear. The system will boot normally then (with the dock still connected). If I boot the system with the dock disconnected, it will correctly go into disk encryption password prompt. If at that point I connect the dock and wait without entering the password, the system will correctly set up the dock: the displays lit up and the mouse and keyboard plugged into it become active. The system boots normally. I'm trying to bisect in which kernel version this happened. I'll put results in a comment. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.25.30 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luis 3332 F pulseaudio /dev/snd/controlC0: luis 3332 F pulseaudio CasperMD5CheckResult: skip Date: Fri Oct 23 16:27:30 2020 InstallationDate: Installed on 2019-08-17 (432 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=/dev/mapper/vglinux-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-09 (13 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895297] Re: My wifi adapter isn't working
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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/1895297 Title: My wifi adapter isn't working Status in linux package in Ubuntu: New Bug description: *-network UNCLAIMED description: Network controller product: QCA9377 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:01:00.0 version: 31 width: 64 bits clock: 33MHz capabilities: cap_list configuration: latency=0 resources: memory:d100-d11f dell inspiron ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gerardubuntu 6230 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 20:46:45 2020 HibernationDevice: RESUME=UUID=59a0929f-c7d7-4970-8d02-edc5a009e594 InstallationDate: Installed on 2019-01-23 (597 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp2s0no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 14-3467 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=e272a186-33cc-4a41-9d70-7765ce6f ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-24 (79 days ago) dmi.bios.date: 01/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 0HNKR2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd01/17/2019:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0HNKR2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 14-3467 dmi.product.sku: 0789 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895439] Re: Trackpad Issue
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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/1895439 Title: Trackpad Issue Status in linux package in Ubuntu: New Bug description: My trackpad is not working It was working just a while ago but now it's not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prayush1446 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 13 17:38:36 2020 InstallationDate: Installed on 2020-09-10 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:55a4 Shenzhen Goodix Technology Co.,Ltd. Goodix FingerPrint Device Bus 001 Device 002: ID 13d3:5415 IMC Networks Integrated Camera Bus 001 Device 007: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4G Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20RAS08A00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=d0dd47b0-3be5-437f-a507-e9fafca739b8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET25W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RAS08A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR16ET25W(1.11):bd04/21/2020:svnLENOVO:pn20RAS08A00:pvrThinkPadE14:rvnLENOVO:rn20RAS08A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 dmi.product.name: 20RAS08A00 dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14 dmi.product.version: ThinkPad E14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873074] Re: kernel panic hit by kube-proxy iptables-save/restore caused by aufs
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. https://bugs.launchpad.net/bugs/1873074 Title: kernel panic hit by kube-proxy iptables-save/restore caused by aufs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Bug description: [Impact] * Systems with aufs mounts are vulnerable to a kernel BUG(), which can turn into a panic/crash if panic_on_oops is set. * It is exploitable by unprivileged local users; and also remote access operations (e.g., web server) potentially. * This issue has also manifested in Kubernetes deployments with a kernel panic in iptables-save or iptables-restore after a few weeks of uptime, without user interaction. * Usually all Kubernetes worker nodes hit the issue around the same time. [Fix] * The issue is fixed with 2 patches in aufs4-linux.git: - 515a586eeef3 aufs: do not call i_readcount_inc() - f10aea57d39d aufs: bugfix, IMA i_readcount * The first addresses the issue, and the second addresses a regression in the aufs feature to change RW branches to RO. * The kernel v5.3 aufs patches had an equivalent fix to the second patch, which is present in the Focal aufs patchset (and on ubuntu-unstable/master & /master-5.8 on 20200629) - 1d26f910c53f aufs: for v5.3-rc1, maintain i_readcount (in aufs5-linux.git) [Test Case] * Repeatedly open/close the same file in read-only mode in aufs (UINT_MAX times, to overflow a signed int back to 0.) * Alternatively, monitor the underlying filesystems's file inode.i_readcount over several open/close system calls. (should not monotonically increase; rather, return to 0.) [Regression Potential] * This changes the core path that aufs opens files, so there is a risk of regression; however, the fix changes aufs for how other filesystems work, so this generally is OK to do. In any case, most regressions would manifest in open() or close() (where the VFS handles/checks inode.i_readcount.) * The aufs maintainer has access to an internal test-suite used to validate aufs changes, used to identify the first regression (in the branch RW/RO mode change), and then to validate/publish the patches upstream; should be good now. * This has also been tested with 'stress-ng --class filesystem' and with 'xfstests -overlay' (patch to use aufs vs overlayfs) on Xenial/Bionic/Focal (-proposed vs. -proposed + patches). No regressions observed in stress-ng/xfstests log or dmesg. [Other Info] * Applied on Unstable (branches master and master-5.8) * Not required on Groovy (still 5.4; should sync from Unstable) * Required on LTS releases: Bionic and Focal and Xenial. * Required on other releases: Disco and Eoan (for custom kernels) [Original Bug Description] Problem Report: -- An user reported several nodes in their Kubernetes clusters hit a kernel panic at about the same time, and periodically (usually 35 days of uptime, and in same order nodes booted.) The kernel panics message/stack trace are consistent across nodes, in __fput() by iptables-save/restore from kube-proxy. Example: """ [3016161.866702] kernel BUG at .../include/linux/fs.h:2583! [3016161.866704] invalid opcode: [#1] SMP ... [3016161.866780] CPU: 40 PID: 33068 Comm: iptables-restor Tainted: P OE 4.4.0-133-generic #159-Ubuntu ... [3016161.866786] RIP: 0010:[...] [...] __fput+0x223/0x230 ... [3016161.866818] Call Trace: [3016161.866823] [...] fput+0xe/0x10 [3016161.866827] [...] task_work_run+0x86/0xb0 [3016161.866831] [...] exit_to_usermode_loop+0xc2/0xd0 [3016161.866833] [...] syscall_return_slowpath+0x4e/0x60 [3016161.866839] [...] int_ret_from_sys_call+0x25/0x9f """ (uptime: 3016161 seconds / (24*60*60) = 34.90 days) They have provided a crashdump (privately available) used for analysis later in this bug report. Note: the root cause turns out to be independent of K8s, as explained in the Root Cause section. Related Report: -- This behavior matches this public bug of another user: https://github.com/kubernetes/kubernetes/issues/70229 """ I have several machines happen kernel panic，and these machine have same dump trace like below: KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-104-generic ... PANIC: "kernel BUG at .../include/linux/fs.h:2582!" ... COMMAND: "iptables-restor" ... crash> bt ... [exception RIP: __fput+541] ... #8 [880199f33e60] __fput at
[Kernel-packages] [Bug 1867141] Re: BUG: Bad rss-counter state mm:00000000f676147b type:MM_SWAPENTS val:-1
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1867141 Title: BUG: Bad rss-counter state mm:f676147b type:MM_SWAPENTS val:-1 Status in linux-5.4 package in Ubuntu: New Bug description: 1. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. linux-generic: Installed: 5.4.0.14.17 Candidate: 5.4.0.14.17 Version table: *** 5.4.0.14.17 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected my desktop computer to log in without an error message. 4. An error message popped up That happened after I installed 71 upgraded packages, then logged out of my Ubuntu session, then logged back in. Perhaps I should have rebooted? ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nick 139333 F pulseaudio /dev/snd/controlC0: nick 139333 F pulseaudio Date: Tue Mar 10 21:05:30 2020 Failure: oops IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: ASUSTeK Computer INC. CM1630 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-generic root=UUID=d0f01318-e4c8-4bc1-a9e9-63574bcc9718 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux-5.4 Title: BUG: Bad rss-counter state mm:f676147b type:MM_SWAPENTS val:-1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: CM1630 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd05/20/2010:svnASUSTeKComputerINC.:pnCM1630:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCM1630:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: CM1630 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1867141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863087] Re: i915 GPU HANG: ecode 9:1:0x00000000, hang on rcs0
*** 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 member of Kernel
Packages, which is subscribed to linux-signed-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1863087
Title:
i915 GPU HANG: ecode 9:1:0x, hang on rcs0
Status in linux-signed-5.4 package in Ubuntu:
Confirmed
Bug description:
During normal desktop use I noticed the whole desktop freeze and it
would not respond (even mouse was frozen and virtual consoles were
inaccessible) - so I rebooted using Alt-SysRq-RIESUB and the following
was in the logs:
Feb 13 16:15:19 slate kernel: i915 :00:02.0: GPU HANG: ecode
9:1:0x, hang on rcs0
Feb 13 16:15:19 slate kernel: GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
Feb 13 16:15:19 slate kernel: Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Feb 13 16:15:19 slate kernel: drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
Feb 13 16:15:19 slate kernel: The GPU crash dump is required to analyze GPU
hangs, so please always attach it.
Feb 13 16:15:19 slate kernel: GPU crash dump saved to
/sys/class/drm/card0/error
Feb 13 16:15:19 slate kernel: i915 :00:02.0: Resetting rcs0 for hang on
rcs0
Feb 13 16:15:19 slate kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 13 16:15:19 slate kernel: i915 :00:02.0: Resetting chip for hang on
rcs0
Feb 13 16:15:19 slate kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 13 16:15:19 slate kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
EDID vendor "DEL", prod id 53409
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Using hsync ranges from config file
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Using vrefresh ranges from config file
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Printing DDC gathered Modelines:
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125
+hsync +vsync (67.5 kHz eP)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1920x1080"x0.0 174.50 1920 1968 2000 2080 1080 1083 1088 1119
+hsync -vsync (83.9 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125
interlace +hsync +vsync (33.8 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync
+vsync (45.0 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync
(31.5 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525
interlace -hsync -vsync (15.7 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625
interlace -hsync -vsync (15.6 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync
(31.5 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125
interlace +hsync +vsync (28.1 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125
+hsync +vsync (56.2 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync
(31.2 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync
+vsync (37.5 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync
(37.9 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync
(37.5 kHz e)
Feb 13 16:15:20
[Kernel-packages] [Bug 1856653] Re: CVE-2019-0154 caused major power problem, pls backport upstream's fix
** 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 upstream's fix Status in linux package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/drm/intel/issues/614 the fix released as CVE-2019-0154 increases idle power consumption on intel i915 6th gen and later. That's because the GPU does not enter RC6 any more. For example, my Thinkpad P50 (6th gen) idles at 9w with current 5.3 kernels. Previously, it idled at 5W. Effects on a T480 (8th gen) are less dramatic but still significant. 5.5RC1 has the maintainer's second pass at this, which restores RC6 idling The maintainer's patch for 5.3 is here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 I have applied this to tag Ubuntu-hwe-5.3.0-25.27~18.04.2 and it builds. I am testing it now. I think it would be very helpful to backport this if you can. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856653/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854013] Re: bionic/linux-snapdragon: 4.15.0-1069.76 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1854013 Title: bionic/linux-snapdragon: 4.15.0-1069.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 27. November 2019 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1854011 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854027] Re: bionic/linux: 4.15.0-72.81 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854027 Title: bionic/linux: 4.15.0-72.81 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 27. November 2019 02:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854029 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1854012 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1854010 bionic/linux-snapdragon: bug 1854013 bionic/linux/pc-kernel: bug 1854024 bionic/linux/pc-lowlatency-kernel: bug 1854025 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1854026 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854029] Re: bionic/linux-aws: 4.15.0-1056.58 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1854029 Title: bionic/linux-aws: 4.15.0-1056.58 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 27. November 2019 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1854028 xenial/linux-aws-hwe: bug 1854030 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854010] Re: bionic/linux-raspi2: 4.15.0-1052.56 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1854010 Title: bionic/linux-raspi2: 4.15.0-1052.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 27. November 2019 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1854009 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852306 Title: xenial/linux: 4.4.0-170.199 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852300] Re: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker
** 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: 4.4.0-1126.135 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852306 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Updates phase-changed: Friday, 29. November 2019 10:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release trackers: xenial/linux-raspi2/pi2-kernel: bug 1852299 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852302] Re: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker
** 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: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852306 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Holding before Promote to Updates phase-changed: Friday, 29. November 2019 10:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1852301 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852298] Re: xenial/linux-kvm: 4.4.0-1063.70 -proposed tracker
** 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: 4.4.0-1063.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852306 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Updates phase-changed: Friday, 29. November 2019 10:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852296] Re: xenial/linux-aws: 4.4.0-1099.110 -proposed tracker
** 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: 4.4.0-1099.110 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852306 packages: main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Updates phase-changed: Friday, 29. November 2019 10:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release trackers: xenial/linux-aws/aws-kernel: bug 1852295 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852285] Re: xenial/linux-gcp: 4.15.0-1050.53 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1852285 Title: xenial/linux-gcp: 4.15.0-1050.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 14. November 2019 22:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1852283 xenial/linux-gcp/gke-kernel: bug 1852284 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852275] Re: xenial/linux-oracle: 4.15.0-1030.33~16.04.1 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852275 Title: xenial/linux-oracle: 4.15.0-1030.33~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852277 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 09:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852277] Re: bionic/linux-oracle: 4.15.0-1030.33 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852277 Title: bionic/linux-oracle: 4.15.0-1030.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 19:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1852275 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852273] Re: bionic/linux-kvm: 4.15.0-1051.51 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1852273 Title: bionic/linux-kvm: 4.15.0-1051.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 14. November 2019 22:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852266] Re: bionic/linux-oem: 4.15.0-1065.75 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1852266 Title: bionic/linux-oem: 4.15.0-1065.75 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 21. November 2019 15:15 UTC reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852253 Title: disco/linux: 5.0.0-37.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1853116 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1853901 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 unknown/unknown: bug 1852245 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852248] Re: disco/linux-oracle: 5.0.0-1008.13 -proposed tracker
** 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: 5.0.0-1008.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 15. November 2019 15:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.0: bug 1852247 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852245] Re: disco/linux-kvm: 5.0.0-1023.25 -proposed tracker
** 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 Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1852245 Title: disco/linux-kvm: 5.0.0-1023.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 14. November 2019 19:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852244] Re: disco/linux-gcp: 5.0.0-1026.27 -proposed tracker
** 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: 5.0.0-1026.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1852241 bionic/linux-gke-5.0: bug 1852243 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852241] Re: bionic/linux-gcp: 5.0.0-1026.27~18.04.1 -proposed tracker
** 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: 5.0.0-1026.27~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852244 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1852240 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852236] Re: disco/linux-aws: 5.0.0-1022.25 -proposed tracker
** 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: 5.0.0-1022.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 20. November 2019 14:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1852235 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852233] Re: disco/linux-raspi2: 5.0.0-1023.24 -proposed tracker
** 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: 5.0.0-1023.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 15. November 2019 08:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** 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: Ubuntu Security Team (ubuntu-security) => Canonical Security Team (canonical-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/1852232 Title: eoan/linux: 5.3.0-24.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1854020 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1854006 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852230] Re: eoan/linux-oracle: 5.3.0-1007.8 -proposed tracker
** 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: 5.3.0-1007.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852232 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 14:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1852229 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852228] Re: eoan/linux-kvm: 5.3.0-1008.9 -proposed tracker
** 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: 5.3.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852232 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Friday, 15. November 2019 13:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852227] Re: eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker
** 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: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852232 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-5.3: bug 1852226 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852225] Re: eoan/linux-azure: 5.3.0-1008.9 -proposed tracker
** 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: 5.3.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852232 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 15. November 2019 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1852224 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852223] Re: eoan/linux-aws: 5.3.0-1008.9 -proposed tracker
** 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: 5.3.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852232 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Friday, 15. November 2019 15:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 185 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851749] Re: Frequently getting thermal warnings and cpu throttling messages in syslog
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 https://forums.lenovo.com/t5/Other-Linux-Discussions/X1C6-T480s-low- cTDP-and-trip-temperature-in-Linux/m-p/4534109/highlight/true#M13637 throttled is not a great solution since this requires writing to MSRs which means users have to disable Secure Boot to use it - instead it is best to wait for the official solution from Lenovo IMO. -- 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/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: In Progress Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1841614] Re: Doesn't start
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Changed in: linux (Ubuntu) Status: New => 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/1841614 Title: Doesn't start Status in linux package in Ubuntu: Invalid Bug description: Hello everybody. I have an old 32 bit acer 1672 wlmi laptop and I have installed on it linux mint xfde 19.2 Tina with the latest kernel. I have installed some previous kernels also to avoid make format again and again. The latest kernel doesn't work propeprly as times as install it on. have erased a lot of times to make the perfect installation. Sometimes pc doesn't start at all, sometimes needs to enter the pass more than two times and sometimes doesn't shut down. I am waiting for your instructions. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841614]
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 https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! -- 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/1841614 Title: Doesn't start Status in linux package in Ubuntu: Invalid Bug description: Hello everybody. I have an old 32 bit acer 1672 wlmi laptop and I have installed on it linux mint xfde 19.2 Tina with the latest kernel. I have installed some previous kernels also to avoid make format again and again. The latest kernel doesn't work propeprly as times as install it on. have erased a lot of times to make the perfect installation. Sometimes pc doesn't start at all, sometimes needs to enter the pass more than two times and sometimes doesn't shut down. I am waiting for your instructions. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834315] Re: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan
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" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+attachment/5275017/+files/buildlog_ubuntu-bionic-i386.glibc_2.27-3ubuntu1_BUILDING.txt.gz ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [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 Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker [Fix] Revert both these patches to restore the original behaviour. [Test] ADT tests for glibc. [Regression Potential] Low. This restores the status quo before the original change to vdso/x86/Makefile to restore the original linker behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834439] Re: designated object in OVAL definition may be wrong
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. https://bugs.launchpad.net/bugs/1834439 Title: designated object in OVAL definition may be wrong Status in Ubuntu CVE Tracker: Confirmed Bug description: recently published OVAL definition (https://people.canonical.com /~ubuntu-security/oval/) may have some breaking change as following: all definition which referenced 'linux' binary package object, has been affected. How to reproduce: for example find definition id: oval:com.ubuntu.xenial:def:201911477000 then in criterions find test_ref="oval:com.ubuntu.xenial:tst:201911477000" then in that test, find object: oval:com.ubuntu.xenial:obj:20124542000, which represent 'linux' package binaries. # oval:com.ubuntu.xenial:obj:20124542000 in this `dpkginfo_object`, used to contain only the name of the binary package, but now it contains a var_ref which points to multiple full name of the most recent binary package for linux kernel image: # oval:com.ubuntu.xenial:var:20124542000 linux-image-4.4.0-151-generic linux-image-4.4.0-151-generic-lpae linux-image-4.4.0-151-lowlatency linux-image-4.4.0-151-powerpc-e500mc linux-image-4.4.0-151-powerpc-smp linux-image-4.4.0-151-powerpc64-emb linux-image-4.4.0-151-powerpc64-smp linux-image-unsigned-4.4.0-151-generic linux-image-unsigned-4.4.0-151-lowlatency In previous version, an object of 'Linux' package has no var_ref and looks like this: # oval:com.ubuntu.xenial:obj:20137445000 linux Compare the object above to the recent version oval:com.ubuntu.xenial:obj:20124542000, we can see there's a change of 'linux' package object, but of which meaning is not yet clear. I believe this is an error, an 'linux' binary package should not contain any version information, as can be seen in other packages objects which only contains a name of package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cve-tracker/+bug/1834439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834315] Re: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan
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 a xenial VM containing an eoan schroot. One data point - for me glibc from eoan-proposed builds fine in an eoan schroot running on a bionic host with the hwe-edge kernel - so it is not clear this needs to be reverted for disco/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 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Incomplete Bug description: [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 Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker [Fix] Revert both these patches to restore the original behaviour. [Test] ADT tests for glibc. [Regression Potential] Low. This restores the status quo before the original change to vdso/x86/Makefile to restore the original linker behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834315] Re: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan
** 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 Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Bug description: [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 Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker [Fix] Revert both these patches to restore the original behaviour. [Test] ADT tests for glibc. [Regression Potential] Low. This restores the status quo before the original change to vdso/x86/Makefile to restore the original linker behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834315] Re: 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 causes glibc 2.29-0ubuntu3 FTBFS on eoan Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Bug description: [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 Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker [Fix] Revert both these patches to restore the original behaviour. [Test] ADT tests for glibc. [Regression Potential] Low. This restores the status quo before the original change to vdso/x86/Makefile to restore the original linker behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834315] [NEW] Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan
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 Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker [Fix] Revert both these patches to restore the original behaviour. [Test] ADT tests for glibc. [Regression Potential] Low. This restores the status quo before the original change to vdso/x86/Makefile to restore the original linker behaviour. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) 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/1834315 Title: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Bug description: [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 Strachan Date: Fri Aug 3 10:39:31 2018 -0700 x86: vdso: Use $LD instead of $CC to link commit cd01544a268ad8ee5b1dfe42c4393f1095f86879 Author: Alistair Strachan Date: Fri Dec 14 14:36:37 2018 -0800 x86/vdso: Pass --eh-frame-hdr to the linker [Fix] Revert both these patches to restore the original behaviour. [Test] ADT tests for glibc. [Regression Potential] Low. This restores the status quo before the original change to vdso/x86/Makefile to restore the original linker behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1025525] Re: DRM buffer permission model is inadequate
** 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 linux package in Ubuntu: Fix Released Bug description: Currently the DRM permission model is roughly “if you've got drm master you can access any buffer and if you don't have drm master you can't access any of master's buffers”. This is ok for the existing fast-user-switching method of spawning a new X server and then VT switching, as the old server drops master and the new server becomes the drm master. Actually, the above is a lie: currently the DRM permission model is ‘if you're authenticated you can access any buffer any client has shared’, and X proxies drm auth for all clients. VT switching drops master, but dropping master does not drop authentication, so this does not prevent inactive users from snooping on shared buffers. For the system compositor this is a bit worse, as the root window of the user sessions will be shared buffers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825753] Re: fan speed not reported with Ubuntu 18.10 and 19.04
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 Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825753 Title: fan speed not reported with Ubuntu 18.10 and 19.04 Status in Hardware Sensors Indicator: Invalid Status in linux package in Ubuntu: New Bug description: after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list of available sensors To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822036] [NEW] Add devicetree overlay to support the SLB9670 TPM module for RPi
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 easily add their own devicetree overlay. Finally it is not practical to expect Ubuntu Core users to have to build and maintain their own kernels just to support a particular hardware device. For background discussion, refer to this thread on the snapcraft forums - https://forum.snapcraft.io/t/guidance-on-snap-interface-to-load-a -device-tree-overlay-on-rpi-core18/10106/11 * Once this overlay is added, then users simply need to modify the boot config.txt to enable the overlay to be loaded automatically. In the future, snapd might also enable support so this can be managed by snapd via snap system configuration. [Test Case] * Boot a RPi with a SLB9670 connected, modify /boot/config.txt to specify dtoverlay=tpm-slb9670, then load the tpm_tis_spi module and /dev/tpm0 should the be available. [Regression Potential] * Almost zero chance of regression potential since this is simply adding a new overlay to the kernel. This is not loaded automatically so there is no real chance of regression. [Other Info] * All that is required for this SRU is to merge https://github.com/raspberrypi/linux/commit/c28ac2dc08bd73963f953a757a3362c64b5524ed to the current bionic raspi kernel branch. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1822036 Title: Add devicetree overlay to support the SLB9670 TPM module for RPi Status in linux-raspi2 package in Ubuntu: New Bug description: [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 easily add their own devicetree overlay. Finally it is not practical to expect Ubuntu Core users to have to build and maintain their own kernels just to support a particular hardware device. For background discussion, refer to this thread on the snapcraft forums - https://forum.snapcraft.io/t/guidance-on-snap-interface-to- load-a-device-tree-overlay-on-rpi-core18/10106/11 * Once this overlay is added, then users simply need to modify the boot config.txt to enable the overlay to be loaded automatically. In the future, snapd might also enable support so this can be managed by snapd via snap system configuration. [Test Case] * Boot a RPi with a SLB9670 connected, modify /boot/config.txt to specify dtoverlay=tpm-slb9670, then load the tpm_tis_spi module and /dev/tpm0 should the be available. [Regression Potential] * Almost zero chance of regression potential since this is simply adding a new overlay to the kernel. This is not loaded automatically so there is no real chance of regression. [Other Info] * All that is required for this SRU is to merge https://github.com/raspberrypi/linux/commit/c28ac2dc08bd73963f953a757a3362c64b5524ed to the current bionic raspi kernel branch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1822036/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791893] Re: Trailing garbage data when sending on an AF_PACKET socket
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 Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791893 Title: Trailing garbage data when sending on an AF_PACKET socket Status in linux package in Ubuntu: New Bug description: When sending an Ethernet frame on an packet socket (AF_PACKET, SOCK_RAW), an additional 14 bytes of trailing data is sent on the interface. The extra 14 bytes are present regardless of the packet size. The extra data could be garbage/uninitialised kernel memory. Expected result: The raw Ethernet frame is sent on the interface. Actual result: The raw Ethernet frame plus an additional 14 bytes of unknown data is sent on the interface. Steps to reproduce: The attached test program inject.c can be used to reproduce the issue. # In window 1. Send an EAP packet without any payload. gcc inject.c -o inject sudo ./inject lo # Simultaneously in window 2. Tcpdump shows a payload of 14 bytes. sudo tcpdump -i lo -enlx 07:45:45.005652 02:00:00:00:00:01 > 02:00:00:00:00:00, ethertype EAPOL (0x888e), length 28: EAP packet (0) v64, len 0 0x: 4000 4000 Running strace on the "inject" program shows that send(2) is indeed called with the correct buffer size. The extra 14 bytes appear to be added by the kernel, and this might leak kernel memory. Ubuntu release: Ubuntu 18.04.1 LTS Package version: 4.15.0-33.36 The issue could not be reproduced on linux-image-4.15.0-22-generic or linux-image-4.15.0-23-generic. uname -a: Linux ubuntu 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787932] Re: package linux-image-4.4.0-133-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-4.4.0-133-generic
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) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-4.4.0-133-generic » vers « /boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) Status in linux package in Ubuntu: Invalid Bug description: message : espace insufisant ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-133-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amraoui052 1608 F pulseaudio /dev/snd/controlC1: amraoui052 1608 F pulseaudio Date: Thu Aug 16 20:03:27 2018 ErrorMessage: impossible de copier les données extraites pour « ./boot/vmlinuz-4.4.0-133-generic » vers « /boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) HibernationDevice: RESUME=UUID=d3976117-ce7f-4bd4-b7a3-a244cf609245 InstallationDate: Installed on 2018-03-27 (145 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK Computer INC. CM6731_CM6431_CM6331-8 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-131-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.4.0-133-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-4.4.0-133-generic » vers « /boot/vmlinuz-4.4.0-133-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6731_CM6431_CM6331 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd09/05/2012:svnASUSTeKComputerINC.:pnCM6731_CM6431_CM6331-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6731_CM6431_CM6331:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: CM6731_CM6431_CM6331-8 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
