from:"Nick Rosbrook"

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread Nick Rosbrook

** Changed in: systemd (Ubuntu Noble)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  In Progress
Status in systemd source package in Noble:
  Fix Committed
Status in zfs-linux source package in Noble:
  In Progress

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread Nick Rosbrook

Since kernel rebuilds are required for the ZFS fix to be readily
available, I am uploading the systemd workaround to help mitigate the
problem.

** Changed in: systemd (Ubuntu Noble)
   Status: Triaged => In Progress

** Changed in: systemd (Ubuntu Noble)
   Importance: Medium => Critical

** Changed in: systemd (Ubuntu Noble)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

** Tags removed: systemd-sru-next

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in zfs-linux package in Ubuntu:
  In Progress
Status in systemd source package in Noble:
  In Progress
Status in zfs-linux source package in Noble:
  In Progress

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-18 Thread Nick Rosbrook

** Tags added: rls-nn-incoming

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-18 Thread Nick Rosbrook

Fix for systemd to work around this:
https://github.com/systemd/systemd/pull/32341.

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Triaged

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

** Tags added: systemd-sru-next

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058179

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2056784] Re: I am facing this problem since last update

2024-03-11 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056784

Title:
  I am facing this problem since last update

Status in linux package in Ubuntu:
  New

Bug description:
  After the latest update my Wifi is facing problems in turning on and
  off. If i try to turn in off from setting Linux hangs and doesnt
  respond so i have to force shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.19 [origin: unknown]
  ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:34937418:2024-03-07 00:08:13.097607256 +0500:2024-03-07 
00:08:08.389607314 
+0500:/var/crash/_opt_kingsoft_wps-office_office6_wps.1000.crash
   640:1000:124:22382432:2024-03-09 16:26:07.512111973 +0500:2024-03-09 
16:26:03.740094005 +0500:/var/crash/_usr_bin_nautilus.1000.crash
   640:1000:124:16745892:2024-03-10 15:07:04.239937641 +0500:2024-03-10 
15:07:02.491937663 
+0500:/var/crash/_opt_kingsoft_wps-office_office6_wpsoffice.1000.crash
   640:1000:124:14354661:2024-03-06 19:21:34.735971256 +0500:2024-03-06 
19:21:32.571971283 
+0500:/var/crash/_opt_kingsoft_wps-office_office6_wpscloudsvr.1000.crash
   640:1000:124:19132571:2024-02-27 11:56:01.657193535 +0500:2024-02-27 
11:55:58.205193577 +0500:/var/crash/_usr_bin_gnome-software.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 11 23:01:49 2024
  InstallationDate: Installed on 2024-02-02 (38 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056784/+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 2017846] Re: System kept waking up after pressing power button

2024-02-23 Thread Nick Rosbrook

** Changed in: systemd (Ubuntu)
   Status: Incomplete => 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/2017846

Title:
  System kept waking up after pressing power button

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Tried it 3 times in the last 15min, each time it keeps waking back up.

  ProblemType: Bug
  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
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC3:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC0:  yamiyuki  42974 F wireplumber
   /dev/snd/seq:yamiyuki  42972 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 27 00:45:37 2023
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  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.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570S AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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: 2023-02-05T17:07:36.420620
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  Package: systemd 252.5-2ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias:

[Kernel-packages] [Bug 2049234] Re: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later

2024-02-23 Thread Nick Rosbrook

*** This bug is a duplicate of bug 2037667 ***
https://bugs.launchpad.net/bugs/2037667

This sounds like a duplicate of 2037667, which is planned to be fixed
sometime soon-ish.

** This bug has been marked a duplicate of bug 2037667
   Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

-- 
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/2049234

Title:
  non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or
  later

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  jammy kernel 5.15.0-81.90 includes the following backport:

  
https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43
  https://bugs.launchpad.net/bugs/2029401

  This causes creation of ip6tnl tunnel interface to fail through
  systemd-networkd. The following systemd commit also has to be applied
  to jammy:

  
https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb

  (Other commits might be required along with above)

  Since the systemd commit is missing on jammy, Kind=ip6tnl netdev
  configuration fails as follows:

  > eno1: Could not create stacked netdev: Invalid argument

  I believe this is a regression; We encountered this linux-
  image-5.15.0-91-generic installed via unattended-upgrade -- Also
  EINVAL during creating tunnel interfaces let AcceptIPv6RA function not
  to start, so we lose connection to our server due to missing IP
  address.

  ```
  # eno1.network
  [Match]
  Name=eno1

  [Network]
  Tunnel=test_tun
  ```

  ```
  # test_tun.netdev
  [NetDev]
  Name=test_tun
  Kind=ip6tnl

  [Tunnel]
  Local=2001:db8::a
  Remote=2001:db8::b
  Mode=any
  ```

  ```
  # test_tun.network
  [Match]
  Name=test_tun

  [Network]
  Address=10.0.0.1/24
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049234/+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 1970069] Re: Annoying boot messages interfering with splash screen

2024-01-30 Thread Nick Rosbrook

AFAIK, the systemd-fsckd patch is still required, but we have vague
plans to get rid of it by making plymouth learn this functionality (i.e.
reading /run/systemd/fsck.progress directly). I have no idea about the
re-ordering, but it would be easy to test with a drop-in config.

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Low

-- 
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/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

2024-01-23 Thread Nick Rosbrook

** Tags added: systemd-sru-next

-- 
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/2037667

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2045407] Re: xhci_hcd usb storage does not boot with kernel 6.5.0-1007 raspi 4

2023-12-05 Thread Nick Rosbrook

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-release-upgrader (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045407

Title:
  xhci_hcd usb storage does not boot with kernel 6.5.0-1007 raspi 4

Status in linux package in Ubuntu:
  New

Bug description:
  Differential analisys

  FAIL BOOT WITH vmlinuz-6.5.0-1007-raspi
  2.411312] xhci_hcd :01:00.0: hcc params 0x002841eb hci version 0x100 qu
  2.414253] xhci hcd :01:00.0: xHCI Host Controller
  2.417066] xhci_hcd :01:00.0: new USB bus registered, assigned bus numbe
  2.418935] xhci_hcd :01:00.0: Host supports USB 3.0 SuperSpeed
  2.424202] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bc
  2.426301] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=
  2.428277] usb usb1: Product: xHCI Host Controller
  2.429833] usb usb1: Manufacturer: Linux 6.5.0-1007-raspi xhci-hcd
  2.431696] usb usb1: Serial Number: :01:00.0
  2.446311] hub 1-0:1.0: USB hub found
  2.449294] hub 1-0:1.0: 1 port detected
  2.455150] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bc
  2.456938] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=
  2.457289] uc2 fe98.usb: supply vusb_d not found, using dummy regulator
  2.458707] usb usb2: Product: XHCI Host Controller
  2.461093] duc2 fe98.usb: supply vusb_a not found, using dummy regulator
  2.481488] usb usb2: Manufacturer: Linux 6.5.0-1007-raspi xhci-hcd
  2.483294] usb usb2: SerialNumber: :01:00.0
  2.488946] hub 2-0:1.0: USB hub found 
  2.491438] hub 2-0:1.0: 4 ports detected
  2.498162] [drm] Initialized u3d 1.0.0 20180419 for fec0.v3d on minor O
  2.5429891 Console: switching to colour dummy device 80x25
  2.543898] vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4])
  2.544513] [drm] Initialized uc4 0.0.0 20140616 for gpu on minor 1
  2.6726471 dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM
  2.672838] dwc2 fe98.usb: DWC OTG Controller
  2.672852] dwc2 fe98.usb: new USB bus registered, assigned bus number 3
  2.672876] dwc2 fe98.usb: irq 39, io mem 0xfe98
  2.673046] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.05
  2.673052] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
  2.673058] usb usb3: Product: DWC OTG Controller
  2.673062] usb usb3: Manufacturer: Linux 6.5.0-1007-raspi duc2_hsotg
  2.673066] usb usb3: Serial Number: fe98.usb 2.6734161 hub 3-0:1.0: USB 
hub found
  2.673439] hub 3-0:1.0: 1 port detected
  2.791029] Console: switching to colour frame buffer device 480x135 2.7989511 
vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device
  9.660608] xhci_hcd :01:00.0: Error while assigning device slot ID: 
Command Aborted
  9.660661] xhci_hcd :01:00.0: Max number of devices this xHCI host 
supports is 32.
  9.660686] usb usb1-port1: couldn't allocate usb_device

  WORKS WITH initrd.img-6.2.0-1014-raspi
  [2.632992] xhci_hcd :01:00.0: xHCI Host Controller
  [2.635543] xhci_hcd :01:00.0: new USB bus registered, assigned bus 
number 1
  [2.639487] xhci_hcd :01:00.0: hcc params 0x002841eb hci version 0x100 
quirks 0x0001e4000890
  [2.642231] xhci_hcd :01:00.0: xHCI Host Controller
  [2.645472] xhci_hcd :01:00.0: new USB bus registered, assigned bus 
number 2
  [2.648041] xhci_hcd :01:00.0: Host supports USB 3.0 SuperSpeed
  [2.653521] [drm] Initialized v3d 1.0.0 20180419 for fec0.v3d on minor 0
  [2.688606] dwc2 fe98.usb: supply vusb_d not found, using dummy 
regulator
  [2.707205] dwc2 fe98.usb: supply vusb_a not found, using dummy 
regulator
  [2.710042] Console: switching to colour dummy device 80x25
  [2.710658] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.02
  [2.710693] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [2.710704] usb usb1: Product: xHCI Host Controller
  [2.710713] usb usb1: Manufacturer: Linux 6.2.0-1014-raspi xhci-hcd
  [2.710721] usb usb1: SerialNumber: :01:00.0
  [2.713279] vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops 
[vc4])
  [2.714004] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1
  [2.720612] hub 1-0:1.0: USB hub found
  [2.720701] hub 1-0:1.0: 1 port detected
  [2.917665] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in 
SPRAM
  [2.917858] dwc2 fe98.usb: DWC OTG Controller
  [2.986726] Console: switching to colour frame buffer device 480x135
  [3.038523] vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device
  [3.058104] dwc2 fe98.usb: new USB bus registered, assigned bus number 
3
  [3.058223] dwc2 fe98.usb: irq 40, io mem 0xfe98
  [3.058410] usb usb2: New USB device

[Kernel-packages] [Bug 2042929] Re: kernel ring buffer prints UBSAN: array-index-out-of-bounds

2023-11-07 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2042929

Title:
  kernel ring buffer prints UBSAN: array-index-out-of-bounds

Status in linux package in Ubuntu:
  New

Bug description:
  Context:
  
  $ lsb_release -a 2>/dev/null
  Distributor ID: Ubuntu
  Description:Ubuntu 23.10
  Release:23.10
  Codename:   mantic

  $ uname -rm
  6.5.0-10-generic x86_64

  $ lshw -short 2>/dev/null | grep display
  /0/100/1/0 /dev/fb0displayVenus XT [Radeon HD 8870M / R9 
M270X/M370X]

  
  Errors:
  ---
  fifix@fifix-Precision-M4800:~$ sudo dmesg | grep UBSAN
  [0.809092] UBSAN: array-index-out-of-bounds in 
/build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2717:34
  [0.809863] UBSAN: array-index-out-of-bounds in 
/build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2715:55
  [0.810629] UBSAN: array-index-out-of-bounds in 
/build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2705:39
  [0.811416] UBSAN: array-index-out-of-bounds in 
/build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/si_dpm.c:6831:39
  [0.812119] UBSAN: array-index-out-of-bounds in 
/build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/si_dpm.c:6868:32
  [   49.054671] UBSAN: array-index-out-of-bounds in 
/build/linux-UiLXaH/linux-6.5.0/include/linux/ieee80211.h:4304:28

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Tue Nov  7 12:15:43 2023
  InstallationDate: Installed on 2023-11-04 (3 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   LANGUAGE=
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042929/+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 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted

2023-10-16 Thread Nick Rosbrook

** Tags added: foundations-todo

-- 
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/1837227

Title:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original Description]
  In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode 
with a failed mount unit (ext4 file system), while the corresponding file 
system is in fact correctly mounted. It happens roughly once every 1000 reboots.

  It seems to be related with this bug :
  https://github.com/systemd/systemd/issues/10872

  Is it possible to apply the fix
  
(https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21)
  in Ubuntu 18.04 ?

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1837227/+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 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic

2023-10-05 Thread Nick Rosbrook

** 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/2038433

Title:
  systemd autopkgtest regression on arm64 and s390x on mantic

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in linux source package in Mantic:
  New
Status in systemd source package in Mantic:
  New

Bug description:
  tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
  ...
  Publishing instance: Image pack: 85% (5.51MB/s)

  Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
  6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
  6845s autopkgtest [09:11:14]: version 5.28ubuntu1
  6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
  7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
  7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
  7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
  7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results 
- - - - - - - - - -
  7064s tests-in-lxd FAIL non-zero exit status 1
  2:40 PM
  ...

  This introduces a regression that is blocking the promotion of new
  kernels in Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
  Uname: Linux 6.5.0-5-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:38:15 2023
  InstallationDate: Installed on 2023-09-25 (9 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.04
  dmi.board.asset.tag: Default string
  dmi.board.name: G1621-02
  dmi.board.vendor: GPD
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 2.3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: G1621-02
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: GPD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+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 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online

2023-10-02 Thread Nick Rosbrook

** Tags removed: rls-mm-incoming
** Tags added: foundations-todo

** Tags added: rls-mm-incoming

** Changed in: systemd (Ubuntu)
   Status: New => Triaged

** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

-- 
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/2036968

Title:
  Mantic minimized/minimal cloud images do not receive IP address during
  provisioning; systemd regression with wait-online

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Following a recent change from linux-kvm kernel to linux-generic
  kernel in the mantic minimized images, there is a reproducable bug
  where a guest VM does not have an IP address assigned as part of
  cloud-init provisioning.

  This is easiest to reproduce when emulating arm64 on amd64 host. The
  bug is a race condition, so there could exist fast enough
  virtualisation on fast enough hardware where this bug is not present
  but in all my testing I have been able to reproduce.

  The latest mantic minimized images from http://cloud-
  images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and
  no initrd to fallback to.

  This but is not present in the non minimized/base images @
  http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with
  the required drivers present for virtio-net.

  Reproducer

  ```
  wget -O "launch-qcow2-image-qemu-arm64.sh" 
https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh

  chmod +x ./launch-qcow2-image-qemu-arm64.sh
  wget 
https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img
  ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image 
./livecd.ubuntu-cpc.img
  ```

  You will then be able to log in with user `ubuntu` and password
  `passw0rd`.

  You can run `ip a` and see that there is a network interface present
  (separate to `lo`) but no IP address has been assigned.

  ```
  ubuntu@cloudimg:~$ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enp0s1:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff

  ```

  This is because when cloud-init is trying to configure network
  interfaces it doesn't find any so it doesn't configure any. But by the
  time boot is complete the network interface is present but cloud-init
  provisioning has already completed.

  You can verify this by running `sudo cloud-init clean && sudo cloud-
  init init`

  You can then see a successfully configured network interface

  ```
  ubuntu@cloudimg:~$ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enp0s1:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
  inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1
     valid_lft 86391sec preferred_lft 86391sec
  inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr 
noprefixroute
     valid_lft 86393sec preferred_lft 14393sec
  inet6 fe80::5054:ff:fe12:3456/64 scope link
     valid_lft forever preferred_lft forever

  ```

  The bug is also reproducible with amd64 guest on adm64 host on
  older/slower hardware.

  The suggested fixes while debugging this issue are:

  * to include `virtio-net` as a built-in in the mantic generic kernel
  * understand what needs to change in cloud-init so that it can react to late 
additions of network interfaces

  I will file a separate bug against cloud-init to address the race
  condition on emulated guest/older hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036968/+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 2037068] Re: Last several kernel upgrades all lead to unbootable kernels and I have to fix by booting n-1 kernel and running "sudo apt-get install linux-headers-6.2.0-33-generic

2023-09-22 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037068

Title:
  Last several kernel upgrades all lead to unbootable kernels and I have
  to fix by booting n-1 kernel and running "sudo apt-get install linux-
  headers-6.2.0-33-generic" or whatever nth is manually.

Status in linux package in Ubuntu:
  New

Bug description:
  I think something is failing in the kernel upgrades and this leads to
  broken installs.

  I now know how to fix but many will find unbootable machines
  unsettling.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-release-upgrader-core 1:23.04.6
  ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   640:1000:117:28885688:2023-09-18 14:34:08.074278247 +0100:2023-09-18 
14:34:08.102277916 +0100:/var/crash/_usr_share_code_code.1000.crash
   600:0:0:187064:2023-09-19 09:02:50.932545294 +0100:2023-09-22 
09:43:12.853529474 +0100:/var/crash/linux-image-6.2.0-33-generic.0.crash
   600:112:117:37:2023-09-18 17:34:12.461589756 +0100:2023-09-18 
14:34:08.590272152 +0100:/var/crash/_usr_share_code_code.1000.uploaded
   644:1000:117:0:2023-09-18 14:34:08.074278247 +0100:2023-09-18 
14:34:08.074278247 +0100:/var/crash/_usr_share_code_code.1000.upload
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 10:31:22 2023
  InstallationDate: Installed on 2018-11-23 (1763 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to lunar on 2023-07-25 (59 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037068/+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 2034106] Re: Bluetooth is scanning for devices but it does not find anything, even if I have bluetooth devices close to the laptop

2023-09-07 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2034106

Title:
  Bluetooth is scanning for devices but it does not find anything, even
  if I have bluetooth devices close to the laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had the same problem with the previous version of Ubuntu, but I
  updated to Ubuntu 23.04, because I was thinking that with the update
  the bug would be fixed. I can turn on or off Bluetooth on my Asus
  Vivobook, but nothing happens, it does not find any device, like
  smartphone, speaker, etc.

  I did a little research on forums, and it seems that there is not a
  problem with the laptop's Bluetooth adapter, but with the kernel. So I
  decided to try this and it seems that if I boot Kernel version 6.0.19
  everything is working fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-release-upgrader-core 1:23.04.6
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 10:21:56 2023
  InstallationDate: Installed on 2023-08-26 (9 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034106/+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 2033923] Re: latest xubuntu jammy daily isos fail to install on asus, lenovo & msi

2023-09-05 Thread Nick Rosbrook

The deprecation of systemd-udev-settle.service has been in place since
at least v243[1], and upstream OpenZFS has been tracking this for a few
years[2].

I don't think anything should change in systemd WRT the deprecation
notice.

[1] 
https://github.com/systemd/systemd/commit/1662732768d4846805bb0143eb08bfaa38e89423
[2] 
https://github.com/systemd/systemd/commit/1662732768d4846805bb0143eb08bfaa38e89423

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2033923

Title:
  latest xubuntu jammy daily isos fail to install on asus, lenovo & msi

Status in Ubuntu CD Images:
  Invalid
Status in linux-hwe-6.2 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Hi,

  I downloaded the latest xubuntu jammy images 20230901 (and previous
  ones, verified them)

  On a Mac all went well with a fresh install, however on a Lenovo,
  Asus, MSI the installer fails...

  udev startup job hangs and is restarted several times with 3 minutes 
increments
  I get several different errors: 

  Dependency failed for Install ZFS kernel module
  Dependency failed for Import ZFS,...

  Failing start job without limit!
  Load Kernel Module efi_pstore

  Thank you for sorting this out
  Kind regards
  Otto

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/2033923/+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 2034068] Re: Ubuntu 22.04.3 linux 6.2 fails to autodetect nvidia aditional drivers

2023-09-05 Thread Nick Rosbrook

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2034068

Title:
  Ubuntu 22.04.3 linux 6.2 fails to autodetect nvidia aditional drivers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the system upgrades to 22.04.3 LTS using kernel 6.2, my nvidia
  card can't be located using "Software and Updates"->"More Drivers", my
  NVIDIA card.

  Using 'lspci' I got this:

  ´´´
  01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 
3060 Mobile / Max-Q] (rev a1)
  ´´´

  The system just stoped to use this card, with a big performance
  impact.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034068/+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 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop

2023-07-05 Thread Nick Rosbrook

Re-assigning since it sounds like this is not a systemd issue.

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988023

Title:
  Could not switch uppercase/lowercase by using keyboard of laptop

Status in linux package in Ubuntu:
  New

Bug description:
  1. Fresh install ubuntu server 22.04.1 on Lenovo server.
  2. Install console-data package 
  3. Get locale status: 
  # localectl status
 System Locale: LANG=en_US.UTF-8
 VC Keymap: n/a
X11 Layout: us
 X11 Model: pc105
  4. Fail to ist and set keymap with command "localectl", but the kmap file can 
be found in the /usr/share./keymaps/
  #localectl list-keymaps 
  Failed to read list of keymaps: No such file or directory 
  # localectl set-keymap us
  Failed to set keymap: Keymap us is not installed.
  # find /usr/ -name us.kmap.gz
  /usr/share/keymaps/i386/qwerty/us.kmap.gz 
  5. It need type "CapsLock" twice when want to switch uppercase/lowercase by 
using keyboard of laptop, not once, the other keyboard has no issue about it.
  # dumpkeys | grep -E "keymaps|58"
  keymaps 0-127
  keycode  58 = CtrlL_Lock 
  6. It can switch uppercase/lowercase normally after run command "loadkeys us".

  Please help check why need type twice "CapsLock" for switching 
uppercase/lowercase and how to fix it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-08-29 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  MachineType: Lenovo ThinkSystem SR630 V2
  Package: systemd 249.11-0ubuntu3.4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/21/2022
  dmi.bios.release: 1.30
  dmi.bios.vendor: Lenovo
  dmi.bios.version: AFE118I-1.30
  dmi.board.asset.tag: none
  dmi.board.name: 7Z70CTO1WW
  dmi.board.vendor: Lenovo
  dmi.board.version: 05
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: none
  dmi.ec.firmware.release: 1.80
  dmi.modalias: 
dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW:
  dmi.product.family: ThinkSystem
  dmi.product.name: ThinkSystem SR630 V2
  dmi.product.sku: 7Z70CTO1WW
  dmi.product.version: 05
  dmi.sys.vendor: Lenovo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988023/+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 2023401] Re: [Dell XPS 17 9700] Upon shutdown, shutdown process doesn't complete and the computer stays on

2023-07-05 Thread Nick Rosbrook

** Changed in: systemd (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/2023401

Title:
  [Dell XPS 17 9700] Upon shutdown, shutdown process doesn't complete
  and the computer stays on

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When I want to shutdown my computer, very often since last Ubuntu
  version, the process seems not to go to the end, and the computer
  never shuts down. I used not to notice it, physically close my laptop
  and put it back in my bag, then hours later find it very hot and with
  fans going at full speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  9 16:35:50 2023
  DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f]
 Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f]
  InstallationDate: Installed on 2021-04-12 (787 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. XPS 17 9700
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.24.0
  dmi.board.name: 0PV91W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9700
  dmi.product.sku: 098F
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023401/+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 1905179] Re: SDcard show wrong date (one month ahead)

2023-06-23 Thread Nick Rosbrook

** Changed in: systemd (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/1905179

Title:
  SDcard show wrong date (one month ahead)

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When mount an SD card date is wrong shown on SD-card (it is shown as to be 
one month ahead). Very strange.
  There is already some report about here, but I don't find a bug here in 
launchpad.
  https://www.explorelinux.com/ubuntu-wrong-date-from-sd-card-pictures/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1077 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (197 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b560 Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook Folio G1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=UUID=92c467dc-e394-4f19-a6a2-e7cf918f0ffb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-54-generic N/A
   linux-backports-modules-5.4.0-54-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-54-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: 07/12/2020
  dmi.bios.vendor: HP
  dmi.bios.version: N91 Ver. 01.49
  dmi.board.name: 8170
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 29.73
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.49:bd07/12/2020:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.73:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook Folio G1
  dmi.product.sku: V1C39EA#ABD
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1078 F pulseaudio
   /dev/snd/pcmC0D0p:   user   1078 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (199 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: HP HP EliteBook Folio G1
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=UUID=92c467dc-e394-4f19-a6a2-e7cf918f0ffb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-54-generic N/A
   linux-backports-modules-5.4.0-54-generic  N/A
   linux-firmware1.187.4
  StagingDrivers: exfat
  Tags:  focal staging
  Uname: Linux 5.4.0-54-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: 07/12/2020
  dmi.bios.vendor: HP
  dmi.bios.version: N91 Ver. 01.49
  dmi.board.name: 8170
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 29.73
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.49:bd07/12/2020:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.73:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook Folio G1
  dmi.product.sku: V1C39EA#ABD
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905179/+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 1932354] Re: systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21 (Test dependencies are unsatisfiable)

2023-06-23 Thread Nick Rosbrook

** Changed in: systemd (Ubuntu)
Status: New => Won't Fix

--
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/1932354

Title:
systemd/247.3-3ubuntu3.1 ADT test failure with linux/5.11.0-20.21
(Test dependencies are unsatisfiable)

Status in linux package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Won't Fix

Bug description:
This is a scripted bug report about ADT failures while running systemd
tests for linux/5.11.0-20.21 on hirsute. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be
determined.

Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210617_171802_98347@/log.gz
armhf:
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/armhf/s/systemd/20210616_224930_60c1e@/log.gz

storage PASS
networkd-test.py FAIL non-zero exit status 1
build-login FAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
boot-and-servicesFAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
udev FAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
root-unittests FAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
tests-in-lxd SKIP installation fails and skip-not-installable set
upstream FAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
boot-smoke FAIL badpkg
blame: systemd
badpkg: Test dependencies are unsatisfiable. A common reason is that your
testbed is out of date with respect to the archive, and you need to use a
current testbed or run apt-get update or use -U.
systemd-fsckdSKIP exit status 77 and marked as skippable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932354/+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 2012157] Re: Removable storage device reset in 22.04, works fine in 16.04

2023-06-22 Thread Nick Rosbrook

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2012157

Title:
  Removable storage device reset in 22.04, works fine in 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a kobo ebook reader. When I plug it in it connects but gets
  reset by something.

  I tried several cables and ports, same result. The device works fine
  on 16.04.

  some things are shown in dmesg:

  [31802.497386] usb 1-3: new high-speed USB device number 8 using xhci_hcd
  [31802.737788] usb 1-3: New USB device found, idVendor=2237, idProduct=4223, 
bcdDevice= 1.10
  [31802.737792] usb 1-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [31802.737793] usb 1-3: Product: eReader-4.25.15875
  [31802.737794] usb 1-3: Manufacturer: Kobo
  [31802.737795] usb 1-3: SerialNumber: RN4377AT01453
  [31802.756812] usb-storage 1-3:1.0: USB Mass Storage device detected
  [31802.756888] scsi host6: usb-storage 1-3:1.0
  [31803.768914] scsi 6:0:0:0: Direct-Access Kobo eReader-4.25.158 0110 
PQ: 0 ANSI: 2
  [31803.769056] sd 6:0:0:0: Attached scsi generic sg3 type 0
  [31803.771864] sd 6:0:0:0: Power-on or device reset occurred
  [31803.774869] sd 6:0:0:0: [sdd] 6614013 512-byte logical blocks: (3.39 
GB/3.15 GiB)
  [31803.883899] sd 6:0:0:0: [sdd] Write Protect is off
  [31803.883903] sd 6:0:0:0: [sdd] Mode Sense: 0f 00 00 00
  [31803.993898] sd 6:0:0:0: [sdd] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [31804.218106]  sdd:
  [31804.219125] sd 6:0:0:0: [sdd] Attached SCSI removable disk
  [31812.151422] r8169 :07:00.0: invalid VPD tag 0x00 (size 0) at offset 0; 
assume missing optional EEPROM
  [31829.639174] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31829.801174] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31835.427152] usb 1-3: reset high-speed USB device number 8 using xhci_hcd
  [31835.589902] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT 
driverbyte=DRIVER_OK cmd_age=31s
  [31835.589906] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 00 88 00 00 
78 00
  [31835.589907] blk_print_req_error: 17 callbacks suppressed
  [31835.589908] I/O error, dev sdd, sector 136 op 0x0:(READ) flags 0x80700 
phys_seg 15 prio class 0
  [31835.694978] sd 6:0:0:0: Power-on or device reset occurred
  [31835.694987] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK cmd_age=0s
  [31835.694989] sd 6:0:0:0: [sdd] tag#0 Sense Key : Unit Attention [current] 
  [31835.694991] sd 6:0:0:0: [sdd] tag#0 Add. Sense: Power on, reset, or bus 
device reset occurred
  [31835.694992] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 01 08 00 00 
08 00
  [31835.694993] I/O error, dev sdd, sector 264 op 0x0:(READ) flags 0x80700 
phys_seg 1 prio class 0
  [31836.078177] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31836.210175] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31838.124177] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31838.258176] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31841.381178] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31841.505179] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31841.680590] audit: type=1400 audit(1679182686.458:129): apparmor="DENIED" 
operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" 
pid=5680 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [31842.394175] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31842.493175] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31847.198179] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31847.316178] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31850.020180] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31850.113179] logitech-djreceiver 0003:046D:C537.0002: Unexpected input 
report number 128
  [31866.151085] usb 1-3: reset high-speed USB device number 8 using xhci_hcd
  [31866.314002] sd 6:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT 
driverbyte=DRIVER_OK cmd_age=30s
  [31866.314007] sd 6:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 00 00 01 10 00 00 
f0 00
  [31866.314009] I/O error, dev sdd, sector 272 op 0x0:(READ) flags 0x80700 
phys_seg 28 prio class 0
  [31866.316049] sd 6:0:0:0: Power-on or device reset occurred
  [31866.316062] sd 6:0:0:0: [sdd] tag#0 device offline or changed
  [31866.316065] I/O error, dev sdd, sector 272 op 0x0:(READ) flags 0x0 
phys_seg 8 prio class 0
  [31866.316068] buffer_io_error: 27

[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend

2023-06-22 Thread Nick Rosbrook

The original report for this is stale. If anyone is experiencing similar
issues on different hardware with newer releases, please open a separate
bug report.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1829399

Title:
  Lid switch triggered suspend takes much longer than UI triggered
  suspend

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  IBM T460
  5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  
  When triggering a suspend even from the lid switch of my Lenovo T460 it takes 
30 seconds to reach suspend state. Several others with different models of 
Lenovo laptops have also reproduced this issue. 

  It seems this is isolated to the lid switch as UI triggered suspend
  (alt+power icon) is far faster.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+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 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

2023-06-21 Thread Nick Rosbrook

According to the last comment, this was fixed by upgrading to 22.04.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => 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/1954843

Title:
  amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
  argument

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 21.10 does not succeed at setting the display brightness after
  booting (either to the GNOME login screen or to a logged-in user's
  desktop). The brightness is at its highest level until I adjust it
  with keyboard shortcuts or a GUI tool.

  The systemd-backlight@backlight:amdgpu_bl0 service seems to fail
  during startup, but I can subsequently run it after startup and it
  succeeds (and restores brightness):

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  [sudo] password for mdmower: 
  × systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: failed (Result: exit-code) since Tue 2021-12-14 13:26:05 PST; 
30s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 962 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=1/FAILURE)
 Main PID: 962 (code=exited, status=1/FAILURE)
  CPU: 3ms

  Dec 14 13:26:05 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:05 T14S systemd-backlight[962]: amdgpu_bl0: Failed to write 
system 'brightness' attribute: Invalid argument
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Main process exited, 
code=exited, status=1/FAILURE
  Dec 14 13:26:05 T14S systemd[1]: 
systemd-backlight@backlight:amdgpu_bl0.service: Failed with result 'exit-code'.
  Dec 14 13:26:05 T14S systemd[1]: Failed to start Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  mdmower@T14S ~ $ sudo systemctl start systemd-
  backlight@backlight:amdgpu_bl0

  mdmower@T14S ~ $ sudo systemctl status systemd-backlight@backlight:amdgpu_bl0
  ● systemd-backlight@backlight:amdgpu_bl0.service - Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0
   Loaded: loaded (/lib/systemd/system/systemd-backlight@.service; static)
   Active: active (exited) since Tue 2021-12-14 13:26:45 PST; 1s ago
 Docs: man:systemd-backlight@.service(8)
  Process: 5119 ExecStart=/lib/systemd/systemd-backlight load 
backlight:amdgpu_bl0 (code=exited, status=0/SUCCESS)
 Main PID: 5119 (code=exited, status=0/SUCCESS)
  CPU: 5ms

  Dec 14 13:26:45 T14S systemd[1]: Starting Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0...
  Dec 14 13:26:45 T14S systemd[1]: Finished Load/Save Screen Backlight 
Brightness of backlight:amdgpu_bl0.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 14 13:29:38 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:5095]
  InstallationDate: Installed on 2021-12-12 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XF004WUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=859a72cc-a3fe-470f-b525-37b151408289 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.14
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1NET44W (1.14)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XF004WUS
  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.ec.firmware.release: 1.14
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1NET44W(1.14):bd11/08/2021:br1.14:efr1.14:svnLENOVO:pn20XF004WUS:pvrThinkPadT14sGen2a:rvnLENOVO:rn20XF004WUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XF_BU_Think_FM_ThinkPadT14sGen2a:
  dmi.product.family: ThinkPad T14s Gen 2a
  dmi.product.name: 20XF004WUS

[Kernel-packages] [Bug 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it

2023-06-21 Thread Nick Rosbrook

Based on the workaround, it seems that the problem is with nvidia
systemd units, and not systemd itself.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1933880

Title:
  systemd-logind crash when suspend with nvidia-suspend.service masked,
  bringing session down with it

Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Run `sudo apt install nvidia-driver-465`. Then, without a need for a 
restart, run `sudo apt autoremove nvidia-driver-465`.
  2. Leaving the terminal open, suspend the machine.

  Expected behavior: the machine suspend successfully and can be woken up 
successfully.
  Actual behavior: the machine doesn't suspend. It either:
  - hang with no respond other than SysRq+REISUB (or maybe network, but I 
didn't test), or
  - return you back to the login screen. Upon logging in, you'll notice that 
the terminal you opened is gone.

  Upon further inspection (on a session that doesn't hang), it's been
  found that X server died with:

  Fatal server error:
  [66.422] (EE) systemd-logind disappeared (stopped/restarted?)

  And checking journal for systemd-logind log, it said:

  Error during inhibitor-delayed operation (already returned success to
  client): Unit nvidia-suspend.service is masked.

  before the new process takes it place.

  The system is Ubuntu 20.04, X.org session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 29 03:34:00 2021
  InstallationDate: Installed on 2021-03-15 (105 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=th_TH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=06f2a676-a62c-443a-8bc8-4e0eda4600f4 ro log_buf_len=2M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN31WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55756 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1933880/+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 2017846] Re: System kept waking up after pressing power button

2023-06-09 Thread Nick Rosbrook

I do see the behavior you are describing in those logs:

Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: Power key pressed short.
Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: The system will suspend now!
Apr 27 00:35:10 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished.
Apr 27 00:35:45 Y4M1-II systemd-logind[2855]: Power key pressed short.
Apr 27 00:35:45 Y4M1-II systemd-logind[2855]: The system will suspend now!
Apr 27 00:36:02 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished.
Apr 27 00:40:00 Y4M1-II systemd-logind[2855]: Power key pressed short.
Apr 27 00:40:00 Y4M1-II systemd-logind[2855]: The system will suspend now!
Apr 27 00:40:17 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished.
Apr 27 00:50:15 Y4M1-II systemd-logind[2855]: The system will power off now!
Apr 27 00:50:15 Y4M1-II systemd-logind[2855]: System is powering down.

Each gap is 17 seconds, which is interesting I guess.

If you are using suspend-then-hibernate (/etc/systemd/sleep.conf) and
your battery is low, the system might be waking up from suspend to then
hibernate (it does not look like you are on batter power though).
Otherwise there might be a timer unit installed with WakeSystem=true
that happens to be firing when you suspend. Besides that I don't think
systemd would do anything else to wake the system (I don't see any other
relevant uses of CLOCK_BOOTTIME_ALARM). If you want to investigate
systemd involvement further, than you can enable debug logs for systemd-
logind and attach updated logs if this issue occurs again.

$ cat > /etc/systemd/system/systemd-logind.service.d/debug-logs.conf << EOF
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
EOF

Probably best to reboot for that to take effect.

-- 
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/2017846

Title:
  System kept waking up after pressing power button

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Tried it 3 times in the last 15min, each time it keeps waking back up.

  ProblemType: Bug
  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
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC3:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC0:  yamiyuki  42974 F wireplumber
   /dev/snd/seq:yamiyuki  42972 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 27 00:45:37 2023
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  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.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570S AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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: 2023-02-05T17:07:36.420620
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu

[Kernel-packages] [Bug 1699942] Re: network-manager fails to deprecate addresses

2023-06-09 Thread Nick Rosbrook

This bug is stale, and it remains unclear if there is a systemd bug, so
marking invalid.

** Changed in: systemd (Ubuntu)
   Status: Incomplete => 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/1699942

Title:
  network-manager fails to deprecate addresses

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  network manager does not properly deprecate autoconfigured temporary IP 
addresses when ValidLifetime for a prefix is 0 in router advertisements. This 
behaviour is non-compliant with RFC 4861 § 6.3.4, which reads:
  If the prefix is already present in the host's Prefix List as
  the result of a previously received advertisement, reset its
  invalidation timer to the Valid Lifetime value in the Prefix
  Information option.  If the new Lifetime value is zero, time-out
  the prefix immediately.

  The hosts instead continued to use temporary addresses configured
  until they reached their timeout, rather than immediately dropping the
  addresses. It further appears that it is generating new temporary
  addresses when the previous ones expire, but I have not been
  monitoring hosts closely enough to tell for sure---I will update on
  this when I have further information.

  This problem was discovered on Ubuntu Studio 16.04.2; it is not
  present on Ubuntu Server (which uses Debian networking scripts).

  Additional Info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1979352] Re: system frozen after sleep

2023-06-09 Thread Nick Rosbrook

** Changed in: systemd (Ubuntu)
   Status: Incomplete => 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/1979352

Title:
  system frozen after sleep

Status in Ubuntu MATE:
  Incomplete
Status in acpid package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC
  2022 x86_64 x86_64 x86_64 GNU/Linux

  This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly 
but, at that time it was only apparent when I was using video ripping software 
on separate laptops and only when the machines became idle once the ripping 
program had finished.
  I don't think this bug was ever fixed and so I'm returning to it because I 
left my laptop in sleep mode over meal time to come back to a frozen system. I 
was not using the video ripping program this time, just surfing the Net. No 
other program was open.

  I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has
  happened when using an old Dell 1530 laptop.

  I do not believe I am unique in having this bug as someone has a
  similar bug when they have minimised Google Chrome and their system
  had went to sleep. I was also using Chrome this time but, as I have
  already said I was having this happen using another program and not
  using Chrome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

2023-06-08 Thread Nick Rosbrook

My understanding is that nothing needs to be done for systemd. Please
re-open if I am mistaken.

** Changed in: systemd (Ubuntu Lunar)
   Status: Confirmed => 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/2016908

Title:
  udev fails to make prctl() syscall with apparmor=0 (as used by maas by
  default)

Status in AppArmor:
  New
Status in MAAS:
  Fix Committed
Status in maas-images:
  Invalid
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in apparmor source package in Lunar:
  Confirmed
Status in linux source package in Lunar:
  Fix Committed
Status in systemd source package in Lunar:
  Invalid

Bug description:
  I'm assuming the image being used for these deploys is 20230417 or
  20230417.1 based on the fact that I saw a 6.2 kernel being used which
  I don't believe was part of the 20230319 serial. I don't have access
  to the maas server, so I can't directly check any log files.

  MAAS Version: 3.3.2

  Here's where the serial log indicates it can't download the squashfs. The 
full log is attached as scobee-lunar-no-squashfs.log (there are some other 
console message intermixed):
  no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf 
/run/net6
  -*.conf
  :: 
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
  date/squa[  206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, 
fsverity
  =yes
  shfs
  :: mount_squash downloading 
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
  4/lunar/candidate/squashfs to /root.tmp.img
  Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
  wget: can't connect to remote host (10.229.32.21): Network is unreachable
  :: mount -t squashfs -o loop  '/root.tmp.img' '/root.tmp'
  mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
  done.

  Still gathering logs and info and will update as I go.

  
  Kernel Bug / Apparmor
  reproducer

  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
  $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd 
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'

  #start the VM
  
  Starting systemd-udevd version 252.5-2ubuntu3
  Spawning shell within the initramfs

  BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) udevadm info --export-db
  Failed to set death signal: Invalid argument

  Observe that udevadm fails to setup death signal, with in systemd code
  is this

  
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
  util.c#L1252

  if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
  if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? 
SIGINT : SIGTERM) < 0) {
  log_full_errno(prio, errno, "Failed to set death 
signal: %m");
  _exit(EXIT_FAILURE);
  }

  
  workaround set kernel commandline to `apparmor=1`
  

  MAAS bug
  Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. 
Even for deployment and commisioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2017846] Re: System kept waking up after pressing power button

2023-04-27 Thread Nick Rosbrook

Can you please attach logs from systemd-logind?

$ journalctl -u systemd-logind.service -b 0 > systemd-logind-log.txt

** Changed in: systemd (Ubuntu)
   Status: New => 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/2017846

Title:
  System kept waking up after pressing power button

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Tried it 3 times in the last 15min, each time it keeps waking back up.

  ProblemType: Bug
  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
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC3:  yamiyuki  42974 F wireplumber
   /dev/snd/controlC0:  yamiyuki  42974 F wireplumber
   /dev/snd/seq:yamiyuki  42972 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 27 00:45:37 2023
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  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.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570S AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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: 2023-02-05T17:07:36.420620
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2022-01-14 (468 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER
  Package: systemd 252.5-2ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro 
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x 
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F5a
  dmi.board.asset.tag: Default string
  dmi.board.name: X570S AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias:

[Kernel-packages] [Bug 2017446] Re: Upgrade to 23.04 from 22.10 failed with error for linux-headers-6.2.0-20-generic

2023-04-24 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017446

Title:
  Upgrade to 23.04 from 22.10 failed with error for linux-
  headers-6.2.0-20-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  evdi modules seems to prevent configuring linux-
  headers-6.2.0-20-generic.

  
  sudo dpkg --configure -a
  Paramétrage de linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Paramétrage de linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Binary update-secureboot-policy not found, modules won't be signed

  Building module:
  Cleaning build area...
  make -j8 KERNELRELEASE=6.2.0-20-generic all 
INCLUDEDIR=/lib/modules/6.2.0-20-generic/build/include 
KVERSION=6.2.0-20-generic DKMS_BUILD=1...(bad exit status: 2)
  ERROR (dkms apport): binary package for evdi: 5.2.14 not found
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/evdi/5.2.14/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: erreur de traitement du paquet linux-headers-6.2.0-20-generic 
(--configure) :
   le sous-processus paquet linux-headers-6.2.0-20-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 1
  dpkg: des problèmes de dépendances empêchent la configuration de 
linux-headers-generic :
   linux-headers-generic dépend de linux-headers-6.2.0-20-generic; cependant :
   Le paquet linux-headers-6.2.0-20-generic n'est pas encore configuré.

  
  I used evdi (DisplayLink) in the past, I don't need it anymore.
  I do not have the displaylink-installer on my system.
  So I cannot use solution https://askubuntu.com/a/1464554

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-release-upgrader-core 1:23.04.6
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   600:0:123:1462045:2023-04-23 20:26:49.518934828 +0200:2023-04-23 
21:11:27.434989670 +0200:/var/crash/linux-headers-6.2.0-20-generic.0.crash
   644:0:0:2527871:2023-04-23 20:52:24.955584619 +0200:2023-04-23 
20:52:24.747575909 +0200:/var/crash/linux-image-6.2.0-20-generic.0.crash
   640:1000:123:588564:2023-04-23 20:00:08.615777930 +0200:2023-04-23 
20:00:08.431769749 
+0200:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_kf5_kioslave5.1000.crash
   640:1000:123:3339641:2023-04-23 20:00:37.677089616 +0200:2023-04-23 
20:00:36.449033419 
+0200:/var/crash/_usr_lib_libreoffice_program_soffice.bin.1000.crash
   640:1000:123:1428023:2023-04-23 20:00:07.083709851 +0200:2023-04-23 
20:00:06.591688015 
+0200:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash
  CurrentDesktop: KDE
  Date: Sun Apr 23 21:24:50 2023
  InstallationDate: Installed on 2019-07-15 (1378 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (0 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017446/+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 2017291] Re: install linux-header-6.2.0-20-generic impossible

2023-04-21 Thread Nick Rosbrook

There are dkms failures in the term log, e.g.:

/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-20-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
'make' -j4 KVER=6.2.0-20-generic 
KSRC=/lib/modules/6.2.0-20-generic/build...
Signing module /var/lib/dkms/rtl8812au/5.13.6/build/8812au.ko
Cleaning build area...

8812au.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.2.0-20-generic/updates/dkms/
depmod...
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area...
'make' -j 4 KVER=6.2.0-20-generic src=/usr/src/rtl88x2bu-5.8.7.1..(bad 
exit status: 2)
ERROR (dkms apport): binary package for rtl88x2bu: 5.8.7.1 not found
Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
Consult /var/lib/dkms/rtl88x2bu/5.8.7.1/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: erreur de traitement du paquet linux-headers-6.2.0-20-generic 
(--configure) :
 le sous-processus paquet linux-headers-6.2.0-20-generic script 
post-installation installé a renvoyé un état de sortie d'erreur 1

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017291

Title:
  install linux-header-6.2.0-20-generic  impossible

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mise à jour de ubuntu mate 22.10 64bits noyau 5.19.0-40 vers ubuntu
  mate 23.04 impossible

  message 1 :
  impossible d'installer "linux-headers-6.2.0-20-generic"
  la mise à niveau va continuer mais le paquet "linux-headers-6.2.0-20-generic" 
pourrait ne pas être fonctionnel.Veuillez signaler ceci comme un bug. Le 
sous-processus paquet linux-headers-6.2.0-20-generic script post-installation 
installé a renvoyé unétat de sortie d'erreur 1

  message 2 :
  impossible d'installer "linux-image-6.2.0-20-generic"
  la mise à niveau va continuer mais le paquet "linux-image-6.2.0-20-generic" 
pourrait ne pas être fonctionnel.Veuillez signaler ceci comme un bug. Le 
sous-processus paquet linux-image-6.2.0-20-generic script post-installation 
installé a renvoyé unétat de sortie d'erreur 1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-release-upgrader-core 1:23.04.6
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CrashReports:
   640:1000:125:3435944:2023-04-21 15:40:05.087342665 +0200:2023-04-21 
15:40:03.243351365 +0200:/var/crash/_usr_bin_marco.1000.crash
   640:1000:125:1820097:2023-04-21 14:46:11.554143233 +0200:2023-04-21 
14:46:10.846146530 +0200:/var/crash/_usr_libexec_tracker-extract-3.1000.crash
   600:0:125:900617:2023-04-21 15:05:21.278174148 +0200:2023-04-21 
15:05:21.234175399 +0200:/var/crash/linux-headers-6.2.0-20-generic.0.crash
   644:0:0:1245663:2023-04-21 15:12:57.143115671 +0200:2023-04-21 
15:12:57.067116251 +0200:/var/crash/linux-image-6.2.0-20-generic.0.crash
  CurrentDesktop: MATE
  Date: Fri Apr 21 16:13:07 2023
  InstallationDate: Installed on 2021-12-04 (502 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017291/+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 2017267] Re: Release upgrade to lunar lobster linux-headers-6.2.0-20 post-installation error

2023-04-21 Thread Nick Rosbrook

This is the relevant error from the apt term log:

Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.2.0-20-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
applying patch disable_fstack-clash-protection_fcf-protection.patch...patching 
file Kbuild
Hunk #1 succeeded at 118 (offset 47 lines).


Building module:
Cleaning build area...
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 
'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.2.0-20-generic 
IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/lib/modules/6.2.0-20-generic/build LD=/usr/bin/ld.bfd 
modules..(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
Consult /var/lib/dkms/nvidia/520.61.05/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
 installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017267

Title:
  Release upgrade to lunar lobster linux-headers-6.2.0-20 post-
  installation error

Status in linux package in Ubuntu:
  New

Bug description:
  Ended with a dialog box:

  Could not install 'linux-headers-6.2.0-20-generic'

  The upgrade will continue but the 'linux-headers-6.2.0-20-generic'
  package may not be in a working state. Please consider submitting a
  bug report about it.

  installed linux-headers-6.2.0-20-generic package post-installation
  script subprocess returned error exit status 1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-release-upgrader-core 1:23.04.6
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   600:0:125:674842:2023-04-21 08:04:24.525593724 -0500:2023-04-21 
08:04:24.613596272 -0500:/var/crash/linux-headers-6.2.0-20-generic.0.crash
   644:0:125:1078246:2023-04-21 08:04:24.461591872 -0500:2023-04-21 
08:04:24.869603682 -0500:/var/crash/nvidia-dkms-520.0.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 21 08:09:44 2023
  InstallationDate: Installed on 2021-01-04 (836 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-kitty
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago)
  VarLogDistupgradeTermlog:
   
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017267/+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 2009910] Re: After updrade (apt), my bluetooth headset microphone doesn't works

2023-04-10 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => bluez (Ubuntu)

-- 
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/2009910

Title:
  After updrade (apt), my bluetooth headset microphone doesn't works

Status in bluez package in Ubuntu:
  New

Bug description:
  Stop working after that upgrade.

  Start-Date: 2023-03-09  19:39:40
  Commandline: packagekit role='update-packages'
  Requested-By: kea (1000)
  Upgrade: udev:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
xscreensaver-screensaver-bsod:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), google-chrome-stable:amd64 (110.0.5481.177-1, 
111.0.5563.64-1), systemd-timesyncd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
xscreensaver-gl-extra:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), 
libpam-systemd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
libyaml-snake-java:amd64 (1.29-1, 1.29-1ubuntu0.22.10.1), libsystemd0:amd64 
(251.4-1ubuntu7, 251.4-1ubuntu7.1), libsystemd0:i386 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), xscreensaver-gl:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), libnss-systemd:amd64 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), libudev-dev:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
systemd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), libudev1:amd64 
(251.4-1ubuntu7, 251.4-1ubuntu7.1), libudev1:i386 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), xscreensaver:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), systemd-resolved:amd64 (251.4-1ubuntu7, 251
 .4-1ubuntu7.1), xscreensaver-data:amd64 (6.02+dfsg1-2ubuntu1, 
6.02+dfsg1-2ubuntu1.2), libsystemd-shared:amd64 (251.4-1ubuntu7, 
251.4-1ubuntu7.1), systemd-sysv:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), 
xscreensaver-data-extra:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), 
signal-desktop:amd64 (6.8.0, 6.9.0)
  End-Date: 2023-03-09  19:40:21

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Mar  9 21:58:06 2023
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to kinetic on 2023-02-10 (27 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2009910/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

2023-03-29 Thread Nick Rosbrook

This autopkgtest run for systemd from 245.4-4ubuntu3.21 focal-proposed
shows that armhf is passing again:
https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/armhf/s/systemd/20230327_104352_bc3ad@/log.gz.

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
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/1991285

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The armhf autopkgtests currently fail in Focal due to this, and failures are 
not marked as regressions. This limits our ability to catch other regressions 
on armhf.

  [Test Plan]
  The boot-and-services autopkgtest should not fail on armhf. Specifically, the 
test_no_failed test should ignore systemd-remount-fs.service failures on armhf 
only.

  [Where problems could occur]
  The fix is limited to the boot-and-services autopkgtest, so there is limited 
risk. Any bugs would show up in that test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

2023-03-13 Thread Nick Rosbrook

Thanks for reviewing, Steve.

I took a closer look at this. The failure is indeed caused by the
container environment, and not something specific to the armhf arch. In
particular, the lxd images ship with a non-empty /etc/fstab which
contains an entry for a disk label that is not present:

root@autopkgtest-lxd-iameji:/tmp/autopkgtest.DW7ZuH/build.h0Z/src# blkid -o list
device   fs_type   label  mount point  UUID
---
root@autopkgtest-lxd-iameji:/tmp/autopkgtest.DW7ZuH/build.h0Z/src# cat 
/etc/fstab 
LABEL=cloudimg-rootfs   /ext4   defaults0 1

Hence, systemd-remount-fs.service fails with the errors shown in comment
#4. I think it would be better to ignore the failure in containers
instead of just armhf.

-- 
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/1991285

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Incomplete

Bug description:
  [Impact]
  The armhf autopkgtests currently fail in Focal due to this, and failures are 
not marked as regressions. This limits our ability to catch other regressions 
on armhf.

  [Test Plan]
  The boot-and-services autopkgtest should not fail on armhf. Specifically, the 
test_no_failed test should ignore systemd-remount-fs.service failures on armhf 
only.

  [Where problems could occur]
  The fix is limited to the boot-and-services autopkgtest, so there is limited 
risk. Any bugs would show up in that test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 2009859] WifiSyslog.txt

2023-03-09 Thread Nick Rosbrook

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653265/+files/WifiSyslog.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias:

[Kernel-packages] [Bug 2009859] UdevDb.txt

2023-03-09 Thread Nick Rosbrook

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2009859/+attachment/5653264/+files/UdevDb.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-4:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-kinetic:cvnQEMU:ct1:cvrpc-i440fx-kinetic:sku:

[Kernel-packages] [Bug 2009859] acpidump.txt

2023-03-09 Thread Nick Rosbrook

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653266/+files/acpidump.txt

** Changed in: linux (Ubuntu Kinetic)
   Status: Incomplete => Confirmed

** 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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias:

[Kernel-packages] [Bug 2009859] ProcModules.txt

2023-03-09 Thread Nick Rosbrook

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653263/+files/ProcModules.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias:

[Kernel-packages] [Bug 2009859] ProcInterrupts.txt

2023-03-09 Thread Nick Rosbrook

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653262/+files/ProcInterrupts.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias:

[Kernel-packages] [Bug 2009859] ProcCpuinfoMinimal.txt

2023-03-09 Thread Nick Rosbrook

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653261/+files/ProcCpuinfoMinimal.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias:

[Kernel-packages] [Bug 2009859] ProcCpuinfo.txt

2023-03-09 Thread Nick Rosbrook

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653260/+files/ProcCpuinfo.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias:

[Kernel-packages] [Bug 2009859] Lspci-vt.txt

2023-03-09 Thread Nick Rosbrook

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653259/+files/Lspci-vt.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-4:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-kinetic:cvnQEMU:ct1:cvrpc-i440fx-kinetic:sku:

[Kernel-packages] [Bug 2009859] Lspci.txt

2023-03-09 Thread Nick Rosbrook

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2009859/+attachment/5653258/+files/Lspci.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-4:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-kinetic:cvnQEMU:ct1:cvrpc-i440fx-kinetic:sku:

[Kernel-packages] [Bug 2009859] Re: systemd: networkd-test.py fails with newer kinetic kernels

2023-03-09 Thread Nick Rosbrook

apport information

** Tags added: apport-collected kinetic

** Description changed:

  systemd autopkgtests are failing in kinetic, and they are not considered
  regressions. The failing test is one within networkd-test.py:
  
  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.
  
  --
  Ran 35 tests in 161.770s
  
  FAILED (errors=1, skipped=2)
  
  The failures started without any changes to the systemd package, i.e. it
  was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.
  
  This can be demonstrated locally with autopkgtest:
  
  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img
  
  Note in the above command I did not pass -U, so no packages in the test
  bed are upgraded. But, with:
  
  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img
  
  the kernel is upgraded, and the test fails.
  
  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:
  
  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns
  
- The attached journal.txt shows systemd-resolved logs from when the test
- is run. The failure is caused by the EHOSTUNREACH when trying to resolve
- math.lab.
+ The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
+  crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.23.1-0ubuntu3
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 22.10
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t:
+  
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 bochs-drmdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
+ ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
+ RelatedPackageVersions:
+  linux-restricted-modules-5.19.0-35-generic N/A
+  linux-backports-modules-5.19.0-35-generic  N/A
+  linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags:  kinetic
+ Uname: Linux 5.19.0-35-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 04/01/2014
+ dmi.bios.release: 0.0
+ dmi.bios.vendor: SeaBIOS
+ dmi.bios.version: 1.16.0-debian-1.16.0-4
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: QEMU
+ dmi.chassis.version: pc-i440fx-kinetic
+ dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-4:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-kinetic:cvnQEMU:ct1:cvrpc-i440fx-kinetic:sku:
+ dmi.product.name: Standard PC (i440FX + PIIX, 1996)
+ dmi.product.version: pc-i440fx-kinetic
+ dmi.sys.vendor: QEMU

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653257/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 2009859] [NEW] systemd: networkd-test.py fails with newer kinetic kernels

2023-03-09 Thread Nick Rosbrook

Public bug reported:

systemd autopkgtests are failing in kinetic, and they are not considered
regressions. The failing test is one within networkd-test.py:

==
ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
resolved: domain-restricted DNS servers
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 680, 
in test_resolved_domain_restricted_dns
out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
  File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.10/subprocess.py", line 524, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

--
Ran 35 tests in 161.770s

FAILED (errors=1, skipped=2)

The failures started without any changes to the systemd package, i.e. it
was caused by another package upload. In particular, the failures
started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
with linux 5.19.0-21.21, i.e. the version in kinetic-release.

This can be demonstrated locally with autopkgtest:

$ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
/home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

Note in the above command I did not pass -U, so no packages in the test
bed are upgraded. But, with:

$ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

the kernel is upgraded, and the test fails.

This can also be done manually by grabbing the systemd source on a
kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

$ sudo python3 test/networkd-test.py
DnsmasqClientTest.test_resolved_domain_restricted_dns

The attached journal.txt shows systemd-resolved logs from when the test
is run. The failure is caused by the EHOSTUNREACH when trying to resolve
math.lab.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Affects: systemd (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653247/+files/journal.txt

** Also affects: systemd (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- systemd: test-networkd.py fails with newer kinetic kernels
+ systemd: networkd-test.py fails with newer kinetic kernels

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  New
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in

[Kernel-packages] [Bug 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

2023-02-27 Thread Nick Rosbrook

** Description changed:

+ [Impact]
+ The armhf autopkgtests currently fail in Focal due to this, and failures are 
not marked as regressions. This limits our ability to catch other regressions 
on armhf.
+ 
+ [Test Plan]
+ The boot-and-services autopkgtest should not fail on armhf. Specifically, the 
test_no_failed test should ignore systemd-remount-fs.service failures on armhf 
only.
+ 
+ [Where problems could occur]
+ The fix is limited to the boot-and-services autopkgtest, so there is limited 
risk. Any bugs would show up in that test.
+ 
+ [Original Description]
+ 
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be determined.
  
  Testing failed on:
- armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz
+ armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

-- 
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/1991285

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Triaged

Bug description:
  [Impact]
  The armhf autopkgtests currently fail in Focal due to this, and failures are 
not marked as regressions. This limits our ability to catch other regressions 
on armhf.

  [Test Plan]
  The boot-and-services autopkgtest should not fail on armhf. Specifically, the 
test_no_failed test should ignore systemd-remount-fs.service failures on armhf 
only.

  [Where problems could occur]
  The fix is limited to the boot-and-services autopkgtest, so there is limited 
risk. Any bugs would show up in that test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

2023-02-24 Thread Nick Rosbrook

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu Focal)
   Status: New => Triaged

** Changed in: systemd (Ubuntu)
   Status: Triaged => 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/1991285

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Triaged

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

2023-02-24 Thread Nick Rosbrook

It appears the last time this worked was around linux 5.4.0-122-generic,
e.g. this test run: https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/armhf/s/systemd/20220907_155827_ae562@/log.gz.

Then we start seeing it around 5.4.0.128.129, e.g. this test run:
https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/armhf/s/systemd/20220922_145908_d6960@/log.gz.

In other words, it started failing with newer kernels but no changes to
systemd. I'm not sure this is having any real impact in the wild, but I
don't want actual armhf regressions to be lost due to this (britney does
not consider armhf failures a regression currently). I think we should
just ignore this failed service on armhf only.

-- 
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/1991285

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

2023-02-07 Thread Nick Rosbrook

** Description changed:

+ [SRU Impact]
+ 
+ Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c, 
test_protect_syscall
+ sysctl is called with the expectation the error result is EFAULT and not 
ENOSYS.
+ This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp, 
oem, gke, oracle).
+ 
+ [Fix]
+ Assertion checks if either EFAULT or ENOSYS is returned. This way it will 
work for focal-5.4 kernels and focal-5.15 kernels.
+ 
+ [Test to reproduce the issue]
+ 1. Create a vm and install one of the focal-5.15 kernels (i.e 
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
+ 2. Run the autotests for upstream and/or root-unittests:
+ autopkgtest --test-name=upstream systemd -- qemu 
+ 
+ [Test to verify the fix]
+ 1. Same as above
+ 2. Apply the fix in your local repo and run the tests using your local repo
+ autopkgtest --test-name=upstream  -- qemu 
+ 
+ [Where problems could occur]
+ This is not gonna affect end users since it is a change in the test only.
+ It may impact autotests, but it's a very low probability.
+ 
+ [Original Description]
+ 
  This is a scripted bug report about ADT failures while running systemd
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is
  caused by the dep8 tests of the tested source or the kernel has yet to
  be determined.
  
  Testing failed on:
- amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
+ amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
- ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
- s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz
+ ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
+ s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz
  
  In arm64, ppc64el and s390x, 'root-unittests' fails with:
  
  /* test_protect_sysctl */
  Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function 
test_protect_sysctl(). A
  borting.
  sysctlseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at s
  rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
  FAIL: test-seccomp (code: 134)
  
  In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
  apparently is caused by the same 'test-seccomp.c:311' assertion failure.

** Merge proposal linked:
   
https://code.launchpad.net/~roxanan/ubuntu/+source/systemd/+git/systemd/+merge/436747

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1933090

Title:
  systemd/245.4-4ubuntu3.6 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Triaged

Bug description:
  [SRU Impact]

  Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c, 
test_protect_syscall
  sysctl is called with the expectation the error result is EFAULT and not 
ENOSYS.
  This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp, 
oem, gke, oracle).

  [Fix]
  Assertion checks if either EFAULT or ENOSYS is returned. This way it will 
work for focal-5.4 kernels and focal-5.15 kernels.

  [Test to reproduce the issue]
  1. Create a vm and install one of the focal-5.15 kernels (i.e 
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
  2. Run the autotests for upstream and/or root-unittests:
  autopkgtest --test-name=upstream systemd -- qemu 

  [Test to verify the fix]
  1. Same as above
  2. Apply the fix in your local repo and run the tests using your local repo
  autopkgtest --test-name=upstream  -- qemu 

  [Where problems could occur]
  This is not gonna affect end users since it is a change in the test only.
  It may impact autotests, but it's a very low probability.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
  armhf:

[Kernel-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

2023-02-02 Thread Nick Rosbrook

** Changed in: systemd (Ubuntu Focal)
   Status: New => Triaged

** Changed in: systemd (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1933090

Title:
  systemd/245.4-4ubuntu3.6 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  New
Status in systemd source package in Focal:
  Triaged

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz

  In arm64, ppc64el and s390x, 'root-unittests' fails with:

  /* test_protect_sysctl */
  Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function 
test_protect_sysctl(). A
  borting.
  sysctlseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at s
  rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
  FAIL: test-seccomp (code: 134)

  In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
  apparently is caused by the same 'test-seccomp.c:311' assertion
  failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+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 1699942] Re: network-manager fails to deprecate addresses

2023-01-05 Thread Nick Rosbrook

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu)
   Status: Won't Fix => 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/1699942

Title:
  network-manager fails to deprecate addresses

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  network manager does not properly deprecate autoconfigured temporary IP 
addresses when ValidLifetime for a prefix is 0 in router advertisements. This 
behaviour is non-compliant with RFC 4861 § 6.3.4, which reads:
  If the prefix is already present in the host's Prefix List as
  the result of a previously received advertisement, reset its
  invalidation timer to the Valid Lifetime value in the Prefix
  Information option.  If the new Lifetime value is zero, time-out
  the prefix immediately.

  The hosts instead continued to use temporary addresses configured
  until they reached their timeout, rather than immediately dropping the
  addresses. It further appears that it is generating new temporary
  addresses when the previous ones expire, but I have not been
  monitoring hosts closely enough to tell for sure---I will update on
  this when I have further information.

  This problem was discovered on Ubuntu Studio 16.04.2; it is not
  present on Ubuntu Server (which uses Debian networking scripts).

  Additional Info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1998721] Re: ACPI errors following upgrade from 20.04 LTS to 22.04 LTS

2022-12-05 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1998721

Title:
  ACPI errors following upgrade from 20.04 LTS to 22.04 LTS

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 20.04, which has been running fine for the past 
two years, to Ubuntu 22.04, the system now takes approximately twice as long to 
boot and gives ACPI errors when booting as follows:
  [0.333898] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  [0.333923] ACPI: button: Power Button [PWRF]
  [0.334069] ACPI BIOS Error (bug): Could not resolve symbol 
[\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.334081] No Local Variables are initialized for Method [_CPC]

  [0.334082] No Arguments are initialized for method [_CPC]

  [0.334084] ACPI Error: Aborting method \_PR.PR01._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.334129] ACPI BIOS Error (bug): Could not resolve symbol 
[\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.334137] No Local Variables are initialized for Method [_CPC]

  [0.334138] No Arguments are initialized for method [_CPC]

  [0.334140] ACPI Error: Aborting method \_PR.PR02._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.334182] ACPI BIOS Error (bug): Could not resolve symbol 
[\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.334189] No Local Variables are initialized for Method [_CPC]

  [0.334190] No Arguments are initialized for method [_CPC]

  [0.334192] ACPI Error: Aborting method \_PR.PR03._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.334235] ACPI BIOS Error (bug): Could not resolve symbol 
[\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.334242] No Local Variables are initialized for Method [_CPC]

  [0.334244] No Arguments are initialized for method [_CPC]

  [0.334245] ACPI Error: Aborting method \_PR.PR04._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.334289] ACPI BIOS Error (bug): Could not resolve symbol 
[\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.334295] No Local Variables are initialized for Method [_CPC]

  [0.334297] No Arguments are initialized for method [_CPC]

  [0.334298] ACPI Error: Aborting method \_PR.PR05._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.334342] ACPI BIOS Error (bug): Could not resolve symbol 
[\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.334348] No Local Variables are initialized for Method [_CPC]

  [0.334350] No Arguments are initialized for method [_CPC]

  [0.334351] ACPI Error: Aborting method \_PR.PR06._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.334398] ACPI BIOS Error (bug): Could not resolve symbol 
[\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.334405] No Local Variables are initialized for Method [_CPC]

  [0.334407] No Arguments are initialized for method [_CPC]

  [0.334408] ACPI Error: Aborting method \_PR.PR07._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.334450] ACPI BIOS Error (bug): Could not resolve symbol 
[\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.334457] No Local Variables are initialized for Method [_CPC]

  [0.334458] No Arguments are initialized for method [_CPC]

  [0.334460] ACPI Error: Aborting method \_PR.PR08._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.334502] ACPI BIOS Error (bug): Could not resolve symbol 
[\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.334509] No Local Variables are initialized for Method [_CPC]

  [0.334510] No Arguments are initialized for method [_CPC]

  [0.334512] ACPI Error: Aborting method \_PR.PR09._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.334554] ACPI BIOS Error (bug): Could not resolve symbol 
[\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.334561] No Local Variables are initialized for Method [_CPC]

  [0.334562] No Arguments are initialized for method [_CPC]

  [0.334564] ACPI Error: Aborting method \_PR.PR10._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.334606] ACPI BIOS Error (bug): Could not resolve symbol 
[\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.334613] No Local Variables are initialized for Method [_CPC]

  [0.334615] No Arguments are initialized for method [_CPC]

  [0.334616] ACPI Error: Aborting method \_PR.PR11._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.335245] thermal LNXTHERM:00: registered as thermal_zone0
  [0.335247] ACPI: thermal: Thermal Zone [TZ00] (28 C)
  [

[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes

2022-11-10 Thread Nick Rosbrook

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

** Tags removed: foundations-triage-discuss

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993318

Title:
  ZFS + Encryption installations of Ubuntu Desktop do not come up
  correctly on first boot, systemd unmounts many of the zfs volumes

Status in Ubuntu Manual Tests:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in zsys package in Ubuntu:
  Invalid

Bug description:
  This is *probably* the wrong package, but it's the best I can figure
  for this, so here goes.

  Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core
  i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM,
  50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO.

  Steps to reproduce:

  1. Boot the Ubuntu desktop ISO.
  2. Select "Install Ubuntu" and proceed with the installation process.
  3. When you get to the "Installation type" screen, select "Advanced Options", 
and enable ZFS + Encryption.
  4. Proceed with the rest of the installation as normal.
  5. Reboot into the newly installed system.
  6. Log in.
  7. Run "sudo apt update" in a terminal.

  Expected result: The package database should be updated normally.

  Actual result: You are presented with the following errors at the end
  of the apt output:

  Reading package lists... Error!
  E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or 
directory)
  E: Could not open file  - open (2: No such file or directory)
  E: Problem opening 
  E: The package lists or status file could not be parsed or opened.

  
  Notes: Switching to a TTY will print a crash error message related to the 
same missing /var/lib/dpkg/status file. Running "sudo touch 
/var/lib/dpkg/status" will allow "sudo apt update" to function and fix the 
crashed process in the TTY.

  Once you log in, you'll notice that Firefox is missing (bug #1993279),
  and you will likely be presented with a ton of error messages and
  other scary junk. At least one of those error messages was related to
  update-manager in my experience, and another one was from "check-new-
  release-gtk".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: zsys (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 18 09:55:27 2022
  InstallationDate: Installed on 2022-10-18 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+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 1995962] Re: 22.10 slows down Thinkpad X270 i3-6100U

2022-11-08 Thread Nick Rosbrook

** Changed in: linux (Ubuntu)
   Status: Invalid => 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/1995962

Title:
  22.10 slows down Thinkpad X270 i3-6100U

Status in linux package in Ubuntu:
  New

Bug description:
  My Lenovo Thinkpad X270 with i3-6100U does 2490 MIPS (via "7zz b") on
  Ubuntu 22.10. The same notebook with Ubuntu 22.04.1 does 6836 MIPS.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  8 16:24:42 2022
  InstallationDate: Installed on 2022-10-12 (27 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995962/+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 1995962] Re: 22.10 slows down Thinkpad X270 i3-6100U

2022-11-08 Thread Nick Rosbrook

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Invalid => New

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

** 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/1995962

Title:
  22.10 slows down Thinkpad X270 i3-6100U

Status in linux package in Ubuntu:
  Invalid

Bug description:
  My Lenovo Thinkpad X270 with i3-6100U does 2490 MIPS (via "7zz b") on
  Ubuntu 22.10. The same notebook with Ubuntu 22.04.1 does 6836 MIPS.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  8 16:24:42 2022
  InstallationDate: Installed on 2022-10-12 (27 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995962/+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 1995787] Re: After upgrading my system suddenly my PC got freeze and start showing EXT4-fs error

2022-11-07 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1995787

Title:
  After upgrading my system suddenly my PC got freeze and start showing
  EXT4-fs error

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading my system suddenly my PC got freeze and start showing
  black screen and EXT4-fs error these are some last updated packages
  below and I user sudo apt upgrade cmd.

  
  2022-11-04 09:15:24 upgrade code-insiders:amd64 1.74.0-1667455053 
1.74.0-1667502703
  2022-11-04 09:15:38 upgrade mutter-common:all 42.2-0ubuntu1 42.5-0ubuntu1
  2022-11-04 09:15:38 upgrade gir1.2-mutter-10:amd64 42.2-0ubuntu1 42.5-0ubuntu1
  2022-11-04 09:15:38 upgrade libmutter-10-0:amd64 42.2-0ubuntu1 42.5-0ubuntu1
  2022-11-05 08:33:17 upgrade tzdata:all 2022e-0ubuntu0.22.04.0 
2022f-0ubuntu0.22.04.0
  2022-11-05 11:37:45 upgrade code-insiders:amd64 1.74.0-1667502703 
1.74.0-1667540431
  2022-11-05 11:37:58 upgrade nodejs:amd64 16.18.0-deb-1nodesource1 
16.18.1-deb-1nodesource1
  2022-11-06 12:12:28 upgrade distro-info-data:all 0.52ubuntu0.1 0.52ubuntu0.2

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.14
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  6 12:55:01 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995787/+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 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop suffer various severe problems related to the package manager

2022-10-18 Thread Nick Rosbrook

Here are some logs from the first boot of a buggy ZFS + encryption
installation.

** Attachment added: "journalctl"
   
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1993318/+attachment/5624931/+files/journalctl.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993318

Title:
  ZFS + Encryption installations of Ubuntu Desktop suffer various severe
  problems related to the package manager

Status in ubiquity package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  New
Status in zsys package in Ubuntu:
  Invalid

Bug description:
  This is *probably* the wrong package, but it's the best I can figure
  for this, so here goes.

  Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core
  i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM,
  50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO.

  Steps to reproduce:

  1. Boot the Ubuntu desktop ISO.
  2. Select "Install Ubuntu" and proceed with the installation process.
  3. When you get to the "Installation type" screen, select "Advanced Options", 
and enable ZFS + Encryption.
  4. Proceed with the rest of the installation as normal.
  5. Reboot into the newly installed system.
  6. Log in.
  7. Run "sudo apt update" in a terminal.

  Expected result: The package database should be updated normally.

  Actual result: You are presented with the following errors at the end
  of the apt output:

  Reading package lists... Error!
  E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or 
directory)
  E: Could not open file  - open (2: No such file or directory)
  E: Problem opening 
  E: The package lists or status file could not be parsed or opened.

  
  Notes: Switching to a TTY will print a crash error message related to the 
same missing /var/lib/dpkg/status file. Running "sudo touch 
/var/lib/dpkg/status" will allow "sudo apt update" to function and fix the 
crashed process in the TTY.

  Once you log in, you'll notice that Firefox is missing (bug #1993279),
  and you will likely be presented with a ton of error messages and
  other scary junk. At least one of those error messages was related to
  update-manager in my experience, and another one was from "check-new-
  release-gtk".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: zsys (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 18 09:55:27 2022
  InstallationDate: Installed on 2022-10-18 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1993318/+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 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop suffer various severe problems related to the package manager

2022-10-18 Thread Nick Rosbrook

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1993318/+attachment/5624930/+files/dmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993318

Title:
  ZFS + Encryption installations of Ubuntu Desktop suffer various severe
  problems related to the package manager

Status in ubiquity package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  New
Status in zsys package in Ubuntu:
  Invalid

Bug description:
  This is *probably* the wrong package, but it's the best I can figure
  for this, so here goes.

  Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core
  i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM,
  50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO.

  Steps to reproduce:

  1. Boot the Ubuntu desktop ISO.
  2. Select "Install Ubuntu" and proceed with the installation process.
  3. When you get to the "Installation type" screen, select "Advanced Options", 
and enable ZFS + Encryption.
  4. Proceed with the rest of the installation as normal.
  5. Reboot into the newly installed system.
  6. Log in.
  7. Run "sudo apt update" in a terminal.

  Expected result: The package database should be updated normally.

  Actual result: You are presented with the following errors at the end
  of the apt output:

  Reading package lists... Error!
  E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or 
directory)
  E: Could not open file  - open (2: No such file or directory)
  E: Problem opening 
  E: The package lists or status file could not be parsed or opened.

  
  Notes: Switching to a TTY will print a crash error message related to the 
same missing /var/lib/dpkg/status file. Running "sudo touch 
/var/lib/dpkg/status" will allow "sudo apt update" to function and fix the 
crashed process in the TTY.

  Once you log in, you'll notice that Firefox is missing (bug #1993279),
  and you will likely be presented with a ton of error messages and
  other scary junk. At least one of those error messages was related to
  update-manager in my experience, and another one was from "check-new-
  release-gtk".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: zsys (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 18 09:55:27 2022
  InstallationDate: Installed on 2022-10-18 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zsys
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1993318/+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 1979352] Re: system frozen after sleep

2022-10-14 Thread Nick Rosbrook

Please run apport-collect 1979352 so that the appropriate logs are
attached to the bug. Without proper logs, we will not be able to
investigate this issue.

** Changed in: ubuntu-mate
   Status: Confirmed => Incomplete

** Changed in: acpid (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: upower (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/1979352

Title:
  system frozen after sleep

Status in Ubuntu MATE:
  Incomplete
Status in acpid package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC
  2022 x86_64 x86_64 x86_64 GNU/Linux

  This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly 
but, at that time it was only apparent when I was using video ripping software 
on separate laptops and only when the machines became idle once the ripping 
program had finished.
  I don't think this bug was ever fixed and so I'm returning to it because I 
left my laptop in sleep mode over meal time to come back to a frozen system. I 
was not using the video ripping program this time, just surfing the Net. No 
other program was open.

  I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has
  happened when using an old Dell 1530 laptop.

  I do not believe I am unique in having this bug as someone has a
  similar bug when they have minimised Google Chrome and their system
  had went to sleep. I was also using Chrome this time but, as I have
  already said I was having this happen using another program and not
  using Chrome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

2022-10-13 Thread Nick Rosbrook

Here's a bit more information about the service failure:

-- Logs begin at Sun 2022-09-25 00:05:05 UTC, end at Thu 2022-09-29 12:03:20 
UTC. --
Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd-remount-fs[74]: mount: /: can't 
find LABEL=cloudimg-rootfs.
Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd-remount-fs[59]: /bin/mount for / 
exited with exit status 1.
Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd[1]: systemd-remount-fs.service: 
Main process exited, code=exited, status=1/FAILURE
Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd[1]: systemd-remount-fs.service: 
Failed with result 'exit-code'.
Sep 29 12:02:57 autopkgtest-lxd-fexenj systemd[1]: Failed to start Remount Root 
and Kernel File Systems.
FAIL

This makes me think it's bug 1576341 again. According to the git
history, that patch was not carried in Ubuntu past 2019. I will try to
find out if we ever attempted to upstream the change.

** Tags removed: foundations-triage-discuss

** Changed in: systemd (Ubuntu)
   Status: New => Triaged

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Low

-- 
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/1991285

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1991975] Re: dev file system is mounted without nosuid or noexec

2022-10-12 Thread Nick Rosbrook

FWIW upstream systemd removed the MS_NOEXEC flag from /dev in
https://github.com/systemd/systemd/commit/4eb105fa4aae30566d23382e8c9430eddf1a3dd4.

-- 
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/1991975

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+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 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system

2022-09-30 Thread Nick Rosbrook

> and which gets from "/etc/os-release/"

Yes, maybe casper should be parsing $VERSION (which contains the point
release number), rather than using $VERSION_ID to build the default iso
URL.

Note however that the script does allow the user to provide their own
url, i.e. when it prompts "url:" as shown above:

Attempt interactive netboot from a URL?
yes no (default yes):
[... snip ...]
 https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default)
 https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso
url: < This prompt

** Also affects: casper (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: casper (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: casper (Ubuntu)
   Status: New => Triaged

** Changed in: casper (Ubuntu)
   Importance: Undecided => Low

** Changed in: casper (Ubuntu Jammy)
   Importance: Undecided => Low

-- 
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/1990621

Title:
  PXE Boot contains wrong suggested link to ISO for live file system

Status in casper package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in casper source package in Jammy:
  Triaged
Status in linux source package in Jammy:
  Invalid

Bug description:
  When PXE booting without pulling in squashfs correctly the system
  tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release
  contains a link to the old version which is not present anymore.

  ---
  Unable to find a medium containing a live file system
  Attempt interactive netboot from a URL?
  yes no (default yes): 
  Two methods available for IP configuration:
* static: for static IP configuration
* dhcp: for automatic IP configuration
  static dhcp (default 'dhcp'): 
  vlan id (optional): 
   https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso 
(default)
   https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso
  url: 
  http_proxy (optional): 
  [  125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: RX/TX
  [  125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
  Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount 
https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... 

  BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443)
  wget: server returned error: HTTP/1.1 404 Not Found
  done.
  Unable to find a medium containing a live file system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+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 1990964] Re: FTBFS on kinetic

2022-09-30 Thread Nick Rosbrook

** Changed in: strace (Ubuntu)
   Status: New => Triaged

** Changed in: strace (Ubuntu)
   Importance: Undecided => High

-- 
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/1990964

Title:
  FTBFS on kinetic

Status in linux package in Ubuntu:
  In Progress
Status in strace package in Ubuntu:
  Triaged

Bug description:
  As can be seen in [1], strace FTBFS in kinetic: this is caused by the
  kernel headers (linux-libc-dev) which do not define F_GETLK64 and
  other on 64b builds because the kernel contains a bogus commit
  (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in
  fcntl.h"). This commit actually did the opposite of what it was
  supposed to do, namely defining those macros even on 64b builds. There
  is an attempt here to fix this which was not merged yet:
  
https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/

  [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic-
  amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+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 1990813] Re: Failed to start NVIDIA Persistence Daemon - pci 0000:02:00.0: can't change power state from D3cold to D0 (config space inaccessible)

2022-09-26 Thread Nick Rosbrook

This does not look like a systemd bug, so I am re-assigning to linux.
But, this sounds similar to your issue:
https://forums.developer.nvidia.com/t/nvidia-probe-of-00-0-failed-
with-error-1/199301, based on looking at your attached CurrentDmesg.txt.



** Package changed: systemd (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990813

Title:
  Failed to start NVIDIA Persistence Daemon - pci :02:00.0: can't
  change power state from D3cold to D0 (config space inaccessible)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I don't get this message every time at boot but sometimes it happens.
  I sent logs in attachments

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 10:07:16 2022
  InstallationDate: Installed on 2022-03-02 (207 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512FLC_R564FL
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=2d8fb36c-c4c1-48be-b649-9fffa7a1440c ro loglevel=1 quiet splash 
loglevel=1 vt.handoff=7
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512FLC.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512FLC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512FLC.304:bd01/26/2021:br5.16:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512FLC_R564FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512FLC_R564FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990813/+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 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42

2022-09-26 Thread Nick Rosbrook

*** This bug is a duplicate of bug 1967576 ***
https://bugs.launchpad.net/bugs/1967576

This was fixed in bug 1967576, so I am marking this a duplicate of that.

** This bug has been marked a duplicate of bug 1967576
   systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount 
units

-- 
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/1965293

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with
  linux/5.13.0-37.42

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  Won't Fix
Status in linux source package in Jammy:
  Incomplete
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-37.42 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz

  The "tests-in-lxd" testcase is failing with all kernels in Impish:

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service snap-lxd-22662.mount 
---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
lxd, revision 22662...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for lxd, revision 22662.
   journal for failed service snap-snapd-15177.mount ---
  -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 
10:01:49 UTC. --
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for 
snapd, revision 15177...
  Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: 
mount failed: Operation not permitted.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Mount process exited, code=exited, status=1/FAILURE
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: 
Failed with result 'exit-code'.
  Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit 
for snapd, revision 15177.
  FAIL
  [...]
  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", 
line 69, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['snap-lxd-22662.mount   loaded failed fai[119 
chars]177'] != []

  First list contains 2 additional elements.
  First extra element 0:
  'snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision 
22662'

  + []
  - ['snap-lxd-22662.mount   loaded failed failed Mount unit for lxd, revision '
  -  '22662',
  -  'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, 
revision '
  -  '15177']

  
  This testcase started to fail with the latest re-spin of the kernels 
(uploaded on mar-16), however the only patch applied between the previous 
kernels and the current ones is a CVE fix which is unlikely to be causing this 
failure:

  "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()"
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965293/+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 1987184] Re: I am not sure about crash reports but I am having multiple issues with keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts working erractically

2022-08-23 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1987184

Title:
  I am not sure about crash reports but I am having multiple issues with
  keyboard and touchpad.Touchpad gets stuck and keyboard keys are starts
  working erractically

Status in linux package in Ubuntu:
  New

Bug description:
  OS VERSION: Ubuntu 22.04
  Laptop: Dell Precision 5550
  Keyboard Layout Set: English(US)

  Touch pad gets stuck quite frequently while external mouse works just
  fine during that time. Sometimes using "sudo modprode psmouse" make
  touchpad start working again.

  Keyboard start working erratically suddenly and os suddenly starts
  acting erratically random things like opening mouse right click
  menu,closing apps,minimizing apps screen and so on.Normally issue
  comes while using vsCode since I do most my text work there.
  ctrl,shift,down arrow keys especially trigger this behaviour. I have
  no idea why this is happening though I know it did not happen in
  Ubuntu 20. Things get so bad only option is to reboot. And this
  happens quite frequently.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.13
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:57730349:2022-08-16 22:46:36.768890857 +0530:2022-08-16 
22:46:37.768890857 +0530:/var/crash/_opt_google_chrome_chrome.1000.crash
   664:1000:124:0:2022-08-16 22:46:37.772890783 +0530:2022-08-16 
22:46:37.772890783 +0530:/var/crash/_opt_google_chrome_chrome.1000.upload
   640:1000:124:672458:2022-08-14 18:59:42.264840602 +0530:2022-08-17 
13:10:25.015404871 +0530:/var/crash/_usr_libexec_gvfsd-mtp.1000.crash
   600:117:124:37:2022-08-16 22:46:39.708866983 +0530:2022-08-17 
13:10:25.015404871 +0530:/var/crash/_opt_google_chrome_chrome.1000.uploaded
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 21 04:31:10 2022
  InstallationDate: Installed on 2022-08-08 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987184/+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 1987052] Re: Running MySQL8 in Docker on ZFS only works if you have ZFS 2.1.5. Ubuntu 22.04 only has 2.1.4 right now.

2022-08-23 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => zfs-linux
(Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1987052

Title:
  Running MySQL8 in Docker on ZFS only works if you have ZFS 2.1.5.
  Ubuntu 22.04 only has 2.1.4 right now.

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Running MySQL 8 using Docker on a ZFS system currently is not possible due to 
a bug in ZFS.
  It has been fixed in ZFS 2.1.5, but jammy-updates is still on 2.1.4

  Can someone please update from 2.1.4 to 2.1.5?

  MySQL 8 is a popular database and running using Docker (and ZFS) is
  more and more common.

  More details on this and confirmed by the MySQL Docker team:
  https://github.com/docker-library/mysql/issues/868

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987052/+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 1981985] Re: Mouse cursor not showing after update

2022-07-18 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981985

Title:
  Mouse cursor not showing after update

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 LTS :: kernel 5.15.0-41-generic :: HP ENVY x360
  Convertible 15-bq1xx

  After last update the mouse cursor does not show when starting up
  laptop. This has been a problem in past but was working fine for the
  previous kernel.

  The cursor issue reappeared when latest kernel update implemented.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.11
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   644:122:117:0:2022-07-09 18:01:42.491084186 -0400:2022-07-09 
18:01:42.491084186 
-0400:/var/crash/_usr_lib_systemd_systemd-timesyncd.122.upload
   600:111:117:37:2022-07-09 18:03:37.895751031 -0400:2022-07-09 
18:03:37.895751031 
-0400:/var/crash/_usr_lib_systemd_systemd-timesyncd.122.uploaded
   640:122:117:391724:2022-07-09 18:01:42.491084186 -0400:2022-07-09 
18:01:42.507084719 -0400:/var/crash/_usr_lib_systemd_systemd-timesyncd.122.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 18 08:07:45 2022
  InstallationDate: Installed on 2018-05-14 (1525 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2022-04-22T10:25:52.110406

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981985/+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 1981933] Re: ACPI BIOS Error (bug) Could not resolve symbols

2022-07-18 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981933

Title:
   ACPI BIOS Error (bug) Could not resolve symbols

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading the kernel to newest official supported kernel
  version, it caused a bug. I upgraded the system with "sudo apt update
  && sudo apt full-upgrade".

  Everytime the desktop PC boots, it prints out the following errors
  before the Ubuntu GUI loaded completely.

  [0.960130] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960141] ACPI Error: Aborting method \_SB.PR01._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960165] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960171] ACPI Error: Aborting method \_SB.PR02._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960193] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960198] ACPI Error: Aborting method \_SB.PR03._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960220] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960225] ACPI Error: Aborting method \_SB.PR04._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960284] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960302] ACPI Error: Aborting method \_SB.PR05._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960337] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960342] ACPI Error: Aborting method \_SB.PR06._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960366] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960371] ACPI Error: Aborting method \_SB.PR07._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960393] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960398] ACPI Error: Aborting method \_SB.PR08._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960420] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960425] ACPI Error: Aborting method \_SB.PR09._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960447] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960452] ACPI Error: Aborting method \_SB.PR10._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960473] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960478] ACPI Error: Aborting method \_SB.PR11._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960500] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960505] ACPI Error: Aborting method \_SB.PR12._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960527] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960532] ACPI Error: Aborting method \_SB.PR13._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960554] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960559] ACPI Error: Aborting method \_SB.PR14._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.960581] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
  [0.960585] ACPI Error: Aborting method \_SB.PR15._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.11
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 17 19:39:35 2022
  InstallationDate: Installed on 2022-04-03 (105 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (87 days ago)
  VarLogDistupgradeXorgFixuplog:

[Kernel-packages] [Bug 1977684] Re: After Upgrade to 22.04. System does not boot into graphical mode without being connected to the network

2022-06-06 Thread Nick Rosbrook

Thanks. I noticed the following kernel stack trace in that log:

---
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: BUG: kernel 
NULL pointer dereference, address: 0058
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: #PF: 
supervisor read access in kernel mode
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: #PF: 
error_code(0x) - not-present page
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: PGD 0 P4D 0
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: Oops:  
[#1] SMP NOPTI
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: CPU: 5 PID: 
141 Comm: kworker/5:1 Tainted: G W 5.15.0-33-generic #34-Ubuntu
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: Hardware 
name: HP HP ENVY x360 Convertible 13-ar0xxx/85DE, BIOS F.19 12/26/2019
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: Workqueue: 
events_long ucsi_init_work [typec_ucsi]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: RIP: 
0010:typec_register_altmode+0x30/0x3b0 [typec]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: Code: 48 89 
e5 41 57 41 56 41 55 49 89 f5 41 54 49 89 fc 48 8d bf 00 03 00 00 53 48 83 ec 
30 65 48 8b 04 25 28 00 00 00 48 89 45 d0 <48> 8b 87 58 fd ff ff 48 3d 80 37 3c 
c0 74 1a 49 8d 94 24 f0 02 00
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: RSP: 
0018:a7b78077fca0 EFLAGS: 00010286
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: RAX: 
b2e6484fbd696500 RBX: 944f4324a000 RCX: 0001
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: RDX: 
 RSI: a7b78077fd78 RDI: 0300
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: RBP: 
a7b78077fcf8 R08:  R09: 
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: R10: 
0001 R11:  R12: 
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: R13: 
a7b78077fd78 R14: a7b78077fd78 R15: 
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: FS: 
() GS:9451d0b4() knlGS:
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: CS: 0010 
DS:  ES:  CR0: 80050033
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: CR2: 
0058 CR3: 000109c2 CR4: 003506e0
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: Call Trace:
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel:
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: ? 
wait_for_completion_timeout+0x1d/0x20
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: 
typec_partner_register_altmode+0xe/0x10 [typec]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: 
ucsi_register_altmode.constprop.0+0x1e4/0x270 [typec_ucsi]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: 
ucsi_register_altmodes+0x156/0x210 [typec_ucsi]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: 
ucsi_check_altmodes+0x1c/0x50 [typec_ucsi]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: 
ucsi_register_port+0x4d0/0x510 [typec_ucsi]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: 
ucsi_init+0xce/0x1b0 [typec_ucsi]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: 
ucsi_init_work+0x16/0x30 [typec_ucsi]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: 
process_one_work+0x22b/0x3d0
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: 
worker_thread+0x53/0x410
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: ? 
process_one_work+0x3d0/0x3d0
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: 
kthread+0x12a/0x150
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: ? 
set_kthread_struct+0x50/0x50
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: 
ret_from_fork+0x22/0x30
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel:
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: Modules 
linked in: snd_hda_codec_hdmi(+) amd64_edac(+) sunrpc(+) snd_hda_intel 
snd_intel_dspcfg edac_mce_amd snd_intel_sdw_acpi snd_hda_codec kvm_amd 
snd_hda_core iommu_v2 snd_hwdep rtw88_8822be gpu_sched kvm snd_pcm 
drm_ttm_helper crct10dif_pclmul rtw88_8822b ghash_clmulni_intel uvcvideo btusb 
ttm rtw88_pci nls_iso8859_1 btrtl aesni_intel btbcm rtw88_core 
videobuf2_vmalloc snd_seq_midi crypto_simd btintel snd_seq_midi_event cryptd 
videobuf2_memops rapl drm_kms_helper snd_rawmidi videobuf2_v4l2 bluetooth 
mac80211 cec input_leds videobuf2_common snd_seq rc_core videodev serio_raw 
ecdh_generic ecc i2c_algo_bit hp_wmi

[Kernel-packages] [Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume

2022-05-23 Thread Nick Rosbrook

I think this a duplicate of, or closely related to bug 1966203.

-- 
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/1971955

Title:
  systemd-udevd  call unshare process  when attaching nvme volume

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  In Progress

Bug description:
  env: PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 (Jammy Jellyfish)"
  VERSION_CODENAME=jammy

  # lsb_release -rd
  Description:Ubuntu 22.04 LTS
  Release:22.04

  
  host connect dellemc powerstore with nvme-tcp connection

  # nvme list-subsys
  nvme-subsys0 - NQN=nqn.1988-11.com.dell:powerstore:00:d42d581e674f2B16F2E2
  \
   +- nvme1 tcp traddr=172.16.100.165 trsvcid=4420 live
   +- nvme2 tcp traddr=172.16.200.164 trsvcid=4420 live
   +- nvme3 tcp traddr=172.16.200.165 trsvcid=4420 live
   +- nvme4 tcp traddr=172.16.100.164 trsvcid=4420 live

  when attaching new volume to host.  systemd-udevd trigger unshare
  process to run snap import command on new volumes and it fail.
  volume finally map to host.  it doesn't affect volume usage. but some
  udev rule need to check for this strange behavior.

  
  May 06 08:16:43 e2e-l4-094051 systemd-udevd[33374]: nvme0n234: Process 
'/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n234' failed 
with exit code 1.
  May 06 08:16:43 e2e-l4-094051 systemd-udevd[33371]: nvme0n232: Process 
'/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n232' failed 
with exit code 1.
  May 06 08:16:43 e2e-l4-094051 systemd-udevd[33378]: nvme0n236: Process 
'/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n236' failed 
with exit code 1.
  May 06 08:16:43 e2e-l4-094051 systemd-udevd[33384]: nvme0n239: Process 
'/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239' failed 
with exit code 1.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  6 08:14 seq
   crw-rw 1 root audio 116, 33 May  6 08:14 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-04 (2 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 8 channel internal hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
   |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/6p, 480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 05/14/2021
  dmi.bios.release: 2.13
  dmi.bios.version: 2.13.0
  dmi.board.name: 072T6D
  dmi.board.version: A01
  dmi.chassis.type: 23
  dmi.modalias: 
dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn072T6D:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=:
  dmi.product.sku: SKU=NotProvided;ModelName=

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1971955/+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 1973709] Re: laptop won't turn off properly after upgrade to 22.04

2022-05-17 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1973709

Title:
  laptop won't turn off properly after upgrade to 22.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If I click shutdown it will enter a "limbo" state, where some LEDs are
  on but it won't react to anything except holding power for a forced
  shutdown. It will drain the batteries this way. Quite annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 17 09:31:34 2022
  InstallationDate: Installed on 2020-01-13 (855 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to jammy on 2022-05-13 (3 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973709/+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 1972791] Re: If i want my P.C. OK, i must to start with the 5.11.0-40-generic Kernel Release . Not another.

2022-05-10 Thread Nick Rosbrook

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1972791

Title:
  If i want my P.C. OK, i must to start with the 5.11.0-40-generic
  Kernel Release . Not another.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If i want my P.C. OK, i must to start with the 5.11.0-40-generic
  Kernel Release . Not another !!! (lol)

  When i try to work whith the 5.11.0-43-generic  Kernel Release (or
  41-generic) : My computeur can't make a reboot yet normaly.   My
  question is : is using the 40-generic Kernel Release (and not sup.
  version) present security risk for me* ? (*my sytems's stability and
  security)

  I use an ASUS VivoBook S14

  Many thanks for your answer. With best regards.
  LVH

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.38
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 09:22:10 2022
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972791/+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

76 matches

Mail list logo