[Touch-packages] [Bug 1646739] Re: "Use of uninitialized value" in debconf via update-manager
*** This bug is a duplicate of bug 1679435 *** https://bugs.launchpad.net/bugs/1679435 I just ran into the same problem: ``` Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88299. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88306. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88315. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88322. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88331. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88338. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88347. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88354. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88363. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88370. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88379. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88386. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88395. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88402. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88411. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88418. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88427. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88434. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88443. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88450. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88459. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88466. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88475. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88482. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88491. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88498. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88507. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88514. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88523. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88530. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88539. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88546. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88555. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 88562. ``` And the line number is increasing every time, high cpu usagec aused by pkg-debconf-helpber. Killling this process led to different errors: ``` Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 91263. Use of uninitialized value in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 227, line 91263. Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 237, line 91263. Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 91263. Use of uninitialized value in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 227, line 91263. Use of
[Touch-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
The process is Intellij IDEA, running on Java 17 in Xwayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206592] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077726+03:00 mavi-ThinkPad-T14s kernel: [
[Touch-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Unfortunately the problem is still reproducible even with the newest mesa, even though it looks like it's much less frequent. Yesterday evening I got another crash, with mesa 23.2.1-1ubuntu2: ``` 2023-10-04T22:33:15.415854+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119146] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:4 pasid:32770, for process Xwayland pid 4940 thread Xwayland:cs0 pid 5015) 2023-10-04T22:33:15.415871+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119168] amdgpu :06:00.0: amdgpu: in page starting at address 0xe5ea2326e000 from IH client 0x1b (UTCL2) 2023-10-04T22:33:15.415873+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119180] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00400430 2023-10-04T22:33:15.415874+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119187] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-10-04T22:33:15.415875+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119194] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x0 2023-10-04T22:33:15.415876+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119200] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-10-04T22:33:15.415878+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119206] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-10-04T22:33:15.415878+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119212] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-10-04T22:33:15.415879+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119218] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-10-04T22:33:15.415881+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119750] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:4 pasid:32770, for process Xwayland pid 4940 thread Xwayland:cs0 pid 5015) 2023-10-04T22:33:15.415881+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119768] amdgpu :06:00.0: amdgpu: in page starting at address 0xe5ea2326f000 from IH client 0x1b (UTCL2) 2023-10-04T22:33:15.415883+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119780] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00400430 2023-10-04T22:33:15.415884+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119787] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-10-04T22:33:15.415885+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119793] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x0 2023-10-04T22:33:15.415885+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119800] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-10-04T22:33:15.415886+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119806] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-10-04T22:33:15.415887+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119812] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-10-04T22:33:15.415888+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119818] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-10-04T22:33:25.115577+03:00 mavi-ThinkPad-T14s kernel: [ 1085.820288] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_low timeout, signaled seq=75561, emitted seq=75563 2023-10-04T22:33:25.115600+03:00 mavi-ThinkPad-T14s kernel: [ 1085.821169] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 4940 thread Xwayland:cs0 pid 5015 2023-10-04T22:33:25.115602+03:00 mavi-ThinkPad-T14s kernel: [ 1085.822031] amdgpu :06:00.0: amdgpu: GPU reset begin! 2023-10-04T22:33:25.347547+03:00 mavi-ThinkPad-T14s kernel: [ 1086.052065] [drm] psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117) 2023-10-04T22:33:25.375820+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078048] amdgpu :06:00.0: amdgpu: MODE2 reset 2023-10-04T22:33:25.375835+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078296] amdgpu :06:00.0: amdgpu: GPU reset succeeded, trying to resume 2023-10-04T22:33:25.375837+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078498] [drm] PCIE GART of 1024M enabled. 2023-10-04T22:33:25.375838+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078503] [drm] PTB located at 0x00F43FC0 2023-10-04T22:33:25.375839+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078625] [drm] PSP is resuming... 2023-10-04T22:33:26.075542+03:00 mavi-ThinkPad-T14s kernel: [ 1086.780162] [drm] reserve 0x40 from 0xf43f80 for PSP TMR 2023-10-04T22:33:26.363527+03:00 mavi-ThinkPad-T14s kernel: [ 1087.066834] amdgpu :06:00.0: amdgpu: RAS: optional ras ta ucode is not available 2023-10-04T22:33:26.375796+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078189] amdgpu :06:00.0: amdgpu: RAP: optional rap ta ucode is not available 2023-10-04T22:33:26.375806+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078196] amdgpu :06:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available 2023-10-04T22:33:26.375808+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078204] amdgpu :06:00.0: amdgpu: SMU is resuming... 2023-10-04T22:33:26.375809+03:00 mavi-ThinkPad-T14s kernel: [ 1087.079063] amdgpu :06:00.0: amdgpu: SMU is resumed
[Touch-packages] [Bug 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit
Filed follow-up https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2038500 to track when the underlying issue is fixed and the workaround can be removed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970634 Title: FTBFS: mariadb fails to start due to low MEMLOCK limit Status in mariadb-10.6 package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in mariadb-10.6 source package in Jammy: Fix Released Status in systemd source package in Jammy: Won't Fix Bug description: [Impact] Jammy's MariaDB will fail to build, and also fail to start, if the underlying kernel is 5.4.x (focal's) and if it's running in an unprivileged container (lxd, docker). It will also fail to build in launchpad builders. Common scenarios where this combination exists is a focal host, running an unprivileged jammy container (lxd or docker), or even a chroot (the launchpad builders). Jammy's MariaDB was built with io_uring support, and it tries to enable it at runtime if it deems it's running on a supported kernel. There is a range of kernel versions it checks, but of interest for this SRU, the Focal (5.4.x) kernel is inside this range and io_uring will be enabled. The jammy kernel (5.15) is not, so io_uring will not be enabled there, and thus the bug is not manifested in that case. If io_uring is enabled, a higher MEMLOCK limit is required than what is set by default in focal or jammy (64Mb is what we get, 256Mb or more is required). The systemd unit file for mariadb tries to raise this limit, but in an unprivileged container this won't work. MariaDB has checks in place to catch when MEMLOCK is too low, in which case it will not use io_uring, but these checks are failing because of the LTO build flags that were used in the jammy build of mariadb. It's unclear if it's a bug in gcc or something else. There is more information in comment #1, comment #5 and later. The suggested fix here is to disable LTO for the jammy build. This has been done for kinetic already, and is also applied to the debian packaging (inside a distro-specific conditional). [Test Plan] The test plan is to launch mariadb in a jammy lxd container running on a focal host. lxc launch ubuntu:focal f --vm lxc shell f lxd init # just hit enter for all questions lxc launch ubuntu:jammy j lxc shell j ulimit -l # confirm it's less than 256 apt update && apt install mariadb-server -y After the installation, mariadb will not be running, and this can be checked with: systemctl status mariadb.service or journalctl -u mariadb.server You will see something like this: Jun 17 18:32:01 jammy-mariadb systemd[1]: Starting MariaDB 10.6.7 database server... Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] /usr/sbin/mariadbd (server 10.6.7-MariaDB-2ubuntu1) starting as process 1864 ... Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] InnoDB: The first data file './ibdata1' did not exist. A new tablespace will be created! Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] InnoDB: Using transactional memory Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] InnoDB: Number of pools: 1 Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOMEM: try larger memory locked limit, ulimit -l, or https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd (262144 bytes required) Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 220617 18:32:01 [ERROR] mysqld got signal 6 ; And a crash dump. With the fixed version, the service will be running normally after installation. [Where problems could occur] The proposed fix is not a surgical strike. It's unfortunate that we didn't get to the bottom of why LTO is causing this behavior. Reverting it is still the quickest and less risky change at the moment, though. This gets us on par with upstream binary builds, and debian builds, and these also have wide test coverage and ample user base. The other regression possibility is that this is a rebuild of mariadb in the current jammy environment, and the package that is currently in jammy was built on March 10th, 2022. Most likely the reverse dependencies were updated in jammy since then. It's unclear how 10.6.7-2ubuntu1 migrated in jammy. I checked build logs and dep8 logs, and can't tell why the tests passed. At least the build log in jammy shows the host kernel was 5.4.x,
[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
Ah no it's a bit simpler than that https://github.com/util-linux/util- linux/issues/2528. --disable-libmount-mountfd-support looking better tbh. ** Bug watch added: github.com/util-linux/util-linux/issues #2528 https://github.com/util-linux/util-linux/issues/2528 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: New Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Status in util-linux source package in Mantic: New Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
So the cause of this, I am fairly sure, is the new "libmount-mountfd" support in util-linux which seems to have the consequence that "mount -o remount $mountpoint" fails for an overlay that references paths no longer available in the current mount namespace. You can see the discussion of a similar-but-not-the-same issue here https://github.com/util-linux/util-linux/issues/1992 I'm trying to come up with a reproducer but I have to head afk now. I'll file a bug upstream when I get that done. Maybe we should build util-linux with --disable-libmount-mountfd-support for now (bit late in the release cycle to be uploading util-linux though...) ** Bug watch added: github.com/util-linux/util-linux/issues #1992 https://github.com/util-linux/util-linux/issues/1992 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: New Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Status in util-linux source package in Mantic: New Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: New Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Status in util-linux source package in Mantic: New Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038436] Re: System doesnt recognize second monitor
Thanks for the bug report. Please run the following commands: sudo apt install drm-info drm_info > drminfo.txt grep . /sys/class/drm/*/status > connections.txt and then attach the two resulting text files here. ** Tags added: multimonitor ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2038436 Title: System doesnt recognize second monitor Status in Ubuntu: Incomplete Bug description: I am using an old monitor which using a DVI connectors but I used a DVI to HDMI adapter which works fine on Windows operating system... My monitor is HP W2072a... I hope with the information provided helps... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 21:17:37 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Device [1b50:1018] InstallationDate: Installed on 2023-09-30 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ILLEGEAR SDN BHD ATOMIC 16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=e60cc65c-b597-415b-b294-3cb6a76ecbd0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2022 dmi.bios.release: 0.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q3AIL.02 dmi.board.asset.tag: Default string be filled by O.E.M dmi.board.name: ATOMIC dmi.board.vendor: ILLEGEAR SDN BHD dmi.board.version: Default string be filled by O.E.M dmi.chassis.asset.tag: Default string be filled by O.E.M dmi.chassis.type: 9 dmi.chassis.vendor: Default string be filled by O.E.M dmi.chassis.version: Default string be filled by O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ3AIL.02:bd07/26/2022:br0.2:svnILLEGEARSDNBHD:pnATOMIC16:pvrDefaultstringbefilledbyO.E.M:rvnILLEGEARSDNBHD:rnATOMIC:rvrDefaultstringbefilledbyO.E.M:cvnDefaultstringbefilledbyO.E.M:ct9:cvrDefaultstringbefilledbyO.E.M:skuATOMIC16-ADL1: dmi.product.family: ATOMIC dmi.product.name: ATOMIC 16 dmi.product.sku: ATOMIC16-ADL1 dmi.product.version: Default string be filled by O.E.M dmi.sys.vendor: ILLEGEAR SDN BHD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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/+bug/2038436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038313] Re: upscayl software do not work
Please report the bug to Upscayl. Although it is possible the cause is the driver issue here so I'll make that more clear in the bug title... ** Summary changed: - upscayl software do not work + MESA-INTEL: warning: Haswell Vulkan support is incomplete ** Changed in: mesa (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2038313 Title: MESA-INTEL: warning: Haswell Vulkan support is incomplete Status in mesa package in Ubuntu: New Bug description: upscayl software do not work BACKEND REPORTED: Selected File Path: /home/anders/Downloads/1695568515335.png Selected Image Path: /home/anders/Downloads/1695568515335.png Selected Image Directory: /home/anders/Downloads imagePath: /home/anders/Downloads/1695568515335.png Extension: png Resetting Upscaled Image Path UPSCAYL BACKEND REPORTED: Updating Overwrite: false BACKEND REPORTED: ✅ Upscayl Variables: [object Object] BACKEND REPORTED: Upscayl Command: -i,/home/anders/Downloads/1695568515335.png,-o,/home/anders/Downloads/1695568515335_upscayl_4x_ultrasharp.png,-s,4,-m,/tmp/.mount_upscaygPuzIl/resources/models,-n,ultrasharp,,,-f,png BACKEND REPORTED: Updating Child Processes: [object Object] BACKEND REPORTED: Updating Stopped: false BACKEND REPORTED: image upscayl: MESA-INTEL: warning: Haswell Vulkan support is incomplete UPSCAYL_PROGRESS: MESA-INTEL: warning: Haswell Vulkan support is incomplete BACKEND REPORTED: image upscayl: [0 Intel(R) HD Graphics 4600 (HSW GT2)] queueC=0[1] queueG=0[1] queueT=0[1] [0 Intel(R) HD Graphics 4600 (HSW GT2)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] fp16-p/s/a=1/0/0 int8-p/s/a=1/0/0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] subgroup=32 basic=1 vote=1 ballot=1 shuffle=1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] queueC=0[1] queueG=0[1] queueT=0[1] [1 llvmpipe (LLVM 15.0.7, 256 bits)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [1 llvmpipe (LLVM 15.0.7, 256 bits)] fp16-p/s/a=1/1/1 int8-p/s/a=1/1/1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] subgroup=8 basic=1 vote=1 ballot=1 shuffle=1 UPSCAYL_PROGRESS: [0 Intel(R) HD Graphics 4600 (HSW GT2)] queueC=0[1] queueG=0[1] queueT=0[1] [0 Intel(R) HD Graphics 4600 (HSW GT2)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] fp16-p/s/a=1/0/0 int8-p/s/a=1/0/0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] subgroup=32 basic=1 vote=1 ballot=1 shuffle=1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] queueC=0[1] queueG=0[1] queueT=0[1] [1 llvmpipe (LLVM 15.0.7, 256 bits)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [1 llvmpipe (LLVM 15.0.7, 256 bits)] fp16-p/s/a=1/1/1 int8-p/s/a=1/1/1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] subgroup=8 basic=1 vote=1 ballot=1 shuffle=1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 3 14:45:19 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. 4th Gen Core Processor Integrated Graphics Controller [10cf:17af] InstallationDate: Installed on 2023-09-06 (26 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 1c4f:0034 SiGma Micro XM102K Optical Wheel Mouse Bus 001 Device 002: ID 8087:07dc Intel Corp. Bluetooth wireless interface 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=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 9: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: FUJITSU LIFEBOOK E554 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=cdedb299-9f30-4ac9-aec9-82dafceeaf91 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Touch-packages] [Bug 2038490] [NEW] Apt and apt-get reporting different lists of packages to be held back/upgraded
Public bug reported: When running apt-get from a script (or command line), I see a different list of packages to be held back / upgraded vs when I run apt. I am running Kubuntu 23.04. The version of apt and apt-get I first noticed the problem in is 2.6.0ubuntu0.1 I also see the problem on my servers running Ubuntu 22.04.3 with apt and apt-get version 2.4.10. I upgraded my copy on Kubuntu 23.04 to 2.7.6 through the launchpad.net ppa deity/sid (actually version 2.7.6+0~202309200852~ubuntu23.04.1) and the problem remains. I've spent a few hours looking for the correct place to search for this being already reported and have reviewed recent commits at https://salsa.debian.org/apt-team/apt. I'm hesitant but I do not see any other mention of this issue. I have tried deleting my /var/cache/apt and running apt update. To duplicate the issue one needs to have an Ubuntu version that has not yet received the update to linux-headers-6.2.0-34, et al. I attempted to duplicate the issue on a fresh install of Ubuntu Desktop 23.04, but discovered that the system is upgraded to linux 6.2.0-34 during the install process. Please see the output of the apt- get and apt commands below. $ apt-get update Hit:1 http://ftp.usf.edu/pub/ubuntu lunar InRelease Hit:2 http://ftp.usf.edu/pub/ubuntu lunar-updates InRelease Hit:3 http://ftp.usf.edu/pub/ubuntu lunar-backports InRelease Hit:4 https://dl.winehq.org/wine-builds/ubuntu lunar InRelease Hit:5 http://ftp.usf.edu/pub/ubuntu lunar-security InRelease Hit:6 http://packages.microsoft.com/repos/code stable InRelease Hit:7 https://repo.steampowered.com/steam stable InRelease Hit:8 https://pkg.cloudflareclient.com jammy InRelease Hit:9 https://download.sublimetext.com apt/stable/ InRelease Get:10 https://pkgs.tailscale.com/stable/ubuntu jammy InRelease Ign:11 https://repo.vivaldi.com/stable/deb stable InRelease Hit:12 https://repo.vivaldi.com/stable/deb stable Release Hit:13 https://download.virtualbox.org/virtualbox/debian jammy InRelease Ign:16 https://download.webmin.com/download/repository sarge InRelease Hit:17 https://ppa.launchpadcontent.net/cappelikan/ppa/ubuntu lunar InRelease Hit:18 https://download.webmin.com/download/repository sarge Release Hit:21 https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu lunar InRelease Hit:14 https://packagecloud.io/github/git-lfs/ubuntu lunar InRelease Hit:15 https://packagecloud.io/eugeny/tabby/ubuntu jammy InRelease Hit:22 https://ppa.launchpadcontent.net/cubic-wizard/release/ubuntu lunar InRelease Hit:23 https://repo.waydro.id bullseye InRelease Hit:24 https://ppa.launchpadcontent.net/deity/sid/ubuntu lunar InRelease Hit:25 https://ppa.launchpadcontent.net/papirus/papirus/ubuntu lunar InRelease Fetched 6,557 B in 3s (2,503 B/s) Reading package lists... Done $ apt-get upgrade --assume-no Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: grub-efi-amd64-bin grub-efi-amd64-signed linux-generic linux-headers-generic linux-image-generic The following packages will be upgraded: code freerdp2-x11 libfreerdp-client2-2 libfreerdp-server2-2 libfreerdp2-2 libwinpr2-2 6 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. Need to get 97.1 MB of archives. After this operation, 1,480 kB of additional disk space will be used. Do you want to continue? [Y/n] N Abort. $ apt upgrade --assume-no Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-6.2.0-34 linux-headers-6.2.0-34-generic
[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
Dave - This happens to me on Pi as well. I have wlan0 fully disabled, so that doesn't appear to be the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Lunar: Fix Committed Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted
This bug is awaiting verification that the linux-azure/5.4.0-1118.125 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-azure' to 'verification-done-focal- linux-azure'. If the problem still exists, change the tag 'verification- needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-azure-v2 verification-needed-focal-linux-azure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
** Tags added: foundaitions-todo ** Tags removed: foundaitions-todo ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
I believe reproducer is: wget https://images.maas.io/ephemeral-v3/candidate/mantic/amd64/20231004.1/ga-23.10/generic/boot-kernel wget https://images.maas.io/ephemeral-v3/candidate/mantic/amd64/20231004.1/ga-23.10/generic/boot-initrd qemu-system-x86_64 -m 4G -smp 2 -nic user,model=virtio-net-pci -kernel boot-kernel -initrd boot-initrd --append 'ip=dhcp root=squash:http://images.maas.io/ephemeral-v3/candidate/mantic/amd64/20231004.1/squashfs overlayroot=tmpfs overlayroot_cfgdisk=disabled systemd.log_level=debug systemd.log_target=console systemd.journald.forward_to_console=1 debug=y' for faster download you might want to have squashfs on local lan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen
Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed right after you reported this issue. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037672 Title: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Incomplete Bug description: Hi, Switching a video to or from fullscreen freezes the screen for around 10 seconds. This happens with Totem as well as VLC so its not related to a specific app. Additional observations: - The issue seems to be connected to the video's bitrate. With low bitrate videos I cannot trigger the freeze. However, videos with high bandwidth trigger the freeze reliably. Specs: Ubuntu 23.10 up to date as of 28.09.2023 AMD Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic Grub configured with: amdgpu.vm_update_mode=3 Syslog shows: 2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid 2311) 2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038453] Re: [SRU] apt snapshot integration backport
** Changed in: ubuntu-pro/18.04 Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2038453 Title: [SRU] apt snapshot integration backport Status in Ubuntu Pro: Triaged Status in Ubuntu Pro 18.04 series: Triaged Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Won't Fix Status in apt source package in Focal: Confirmed Status in apt source package in Jammy: Confirmed Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Released Bug description: [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T00Z, it should download the snapshot 3. run apt install --snapshot 20231001T00Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2038453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038453] Re: [SRU] apt snapshot integration backport
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2038453 Title: [SRU] apt snapshot integration backport Status in Ubuntu Pro: Triaged Status in Ubuntu Pro 18.04 series: Triaged Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Won't Fix Status in apt source package in Focal: Confirmed Status in apt source package in Jammy: Confirmed Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Released Bug description: [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T00Z, it should download the snapshot 3. run apt install --snapshot 20231001T00Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2038453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038453] Re: [SRU] apt snapshot integration backport
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2038453 Title: [SRU] apt snapshot integration backport Status in Ubuntu Pro: Triaged Status in Ubuntu Pro 18.04 series: Triaged Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Won't Fix Status in apt source package in Focal: Confirmed Status in apt source package in Jammy: Confirmed Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Released Bug description: [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T00Z, it should download the snapshot 3. run apt install --snapshot 20231001T00Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2038453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038453] Re: [SRU] apt snapshot integration backport
** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Bionic) Status: New => Won't Fix ** Also affects: ubuntu-pro Importance: Undecided Status: New ** Also affects: ubuntu-pro/18.04 Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2038453 Title: [SRU] apt snapshot integration backport Status in Ubuntu Pro: New Status in Ubuntu Pro 18.04 series: New Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Won't Fix Status in apt source package in Focal: New Status in apt source package in Jammy: New Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Released Bug description: [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T00Z, it should download the snapshot 3. run apt install --snapshot 20231001T00Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2038453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
** Changed in: webkit2gtk (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in Webkit: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: In Progress Status in yelp package in Ubuntu: Triaged Status in webkit2gtk package in Debian: Confirmed Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an override-redirect
[Touch-packages] [Bug 2031340] Re: slic3r-prusa autopkgtest flaky
Just adding that I tried rebuilding the package and tests are still failing 2.6.1+dfsg-3 https://launchpad.net/~mitchdz/+archive/ubuntu/slic3r-prusa- mantic/+builds?build_text=_state=all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gmp in Ubuntu. https://bugs.launchpad.net/bugs/2031340 Title: slic3r-prusa autopkgtest flaky Status in fontconfig package in Ubuntu: Fix Released Status in gmp package in Ubuntu: Fix Released Status in nlopt package in Ubuntu: Fix Released Status in slic3r-prusa package in Ubuntu: New Bug description: autopkgtest was added to slic3r-prusa as late as last April. They have never let version 2.6.0 of slic3r-prusa migrate to Debian testing, and seemingly need more work. slic3r-prusa 2.6.0+dfsg-2 was uploaded to unstable on July 27 but hasn't migrated to testing yet due to failing autopkgtest. In Ubuntu the flaky tests currently prevent fontconfig and nlopt (in addition to slic3r-prusa itself) from migrating to mantic-release. Probably some kind of hint is motivated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2031340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037417] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2037417 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in linux source package in Mantic: Incomplete Status in systemd source package in Mantic: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
** Project changed: linux => linux (Ubuntu) ** Changed in: linux (Ubuntu) Milestone: None => ubuntu-23.10 ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Mantic) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in linux source package in Mantic: New Status in systemd source package in Mantic: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in linux source package in Mantic: New Status in systemd source package in Mantic: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
** Also affects: linux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in linux source package in Mantic: New Status in systemd source package in Mantic: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038453] Re: [SRU] apt snapshot integration backport
** Description changed: [Impact] - The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning. + The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T00Z, it should download the snapshot 3. run apt install --snapshot 20231001T00Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04 with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. ** Description changed: [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T00Z, it should download the snapshot 3. run apt install --snapshot 20231001T00Z hello, it should install hello from the snapshot [Where problems could occur] - The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04 with only a minor editorial change. This significantly limits the risk. + The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04, with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2038453 Title: [SRU] apt snapshot integration backport Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: New Status in apt source package in Jammy: New Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Released Bug description: [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run
[Touch-packages] [Bug 2017401] Re: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2017401 Title: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled Status in unattended-upgrades package in Ubuntu: Confirmed Status in unattended-upgrades source package in Focal: Confirmed Status in unattended-upgrades source package in Jammy: Confirmed Bug description: Following the resolution for bug #1747499, after a kernel upgrade when Livepatch is enabled, the current behaviour in unattended-upgrades (2.3ubuntu0.2 and later) is not to touch /var/run/reboot-required so as not to confuse users with two separate messages calling for a restart in motd. This functionality is implemented in the script at /etc/kernel/postinst.d/unattended-upgrades. While this works as intended in terms of suppressing an extra message in motd, it defeats the ability of unattended-upgrades to restart automatically with the new kernel, which is reliant on /var/run/reboot-required being present. This is unexpected / unwanted behaviour in scenarios where a) Livepatch is being used to provide fast-response kernel patching; and b) Unattended-Upgrade::Automatic-Reboot is set to true, to enable automatic reboots during a regular maintenance window. In this case, without administrative intervention, the system could never boot into the new kernel even though it would be expected to, leaving Livepatch to do all the heavy lifting indefinitely, and unnecessarily. I believe this counts as a regression caused by the resolution to bug #1747499. It also has the potential to be a security threat if Livepatch doesn't work comprehensively for a particular kernel flaw, and an administrator is reliant on expected behaviour according to unattended-upgrades settings. Potential options for a fix that come to mind: 1. Revert to original behaviour in /etc/kernel/postinst.d/unattended-upgrades, and change the ***System restart required*** message to be less alarming or confusing when the cause is a kernel upgrade that's being patched by Livepatch. 2. Add an extra configuration setting (eg Unattended-Upgrade::Automatic-Reboot-After-Livepatch) that triggers a reboot when it's 'recommended' by Livepatch, not reliant on the presence of /var/run/reboot-required. 3. Add support in /etc/kernel/postinst.d/unattended-upgrades for an extra file somewhere. When present, /var/run/reboot-required is always touched, even if Livepatch is enabled. (This is my first time reporting a bug in this system, and I apologise if I haven't followed the usual descriptive format.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2017401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038453] [NEW] [SRU] apt snapshot integration backport
Public bug reported: [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T00Z, it should download the snapshot 3. run apt install --snapshot 20231001T00Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04 with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. ** Affects: apt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** Affects: apt (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: apt (Ubuntu Lunar) Importance: Undecided Status: Won't Fix ** Affects: apt (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Also affects: apt (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Mantic) Status: New => Fix Released ** Changed in: apt (Ubuntu Lunar) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2038453 Title: [SRU] apt snapshot integration backport Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: New Status in apt source package in Jammy: New Status in apt source package in Lunar: Won't Fix Status in apt source package in Mantic: Fix Released Bug description: [Impact] The snapshot service provides users access to older states of the archive with ease of use, and enables a consistent user experience across all supported releases, as otherwise users would have to rewrite their sources.list to make use of snapshots and set up pinning; hence partners requested the feature be SRUed to older releases as well. [Test plan] The complete regression test suite in autopkgtests includes an automatic test case for this and the known limitations that have been fixed. Aside from that, it is also worthwhile to do an end-to-end test: Configure snapshot=yes for Ubuntu sources in your sources.list and 1. run apt update - it should not use snapshot 2. run apt update --snapshot 20231001T00Z, it should download the snapshot 3. run apt install --snapshot 20231001T00Z hello, it should install hello from the snapshot [Where problems could occur] The integration has been purposefully limited in how it works to reduce the impact it has on the APT code; hence it was possible to cherry-pick this into 22.04, 20.04, and even 18.04 with only a minor editorial change. This significantly limits the risk. This feature is only enabled for sources with snapshot=yes (.list) or Snapshot: yes (.sources) or other truthy values apt recognizes. Most users will not have such entries as they did not have an APT supporting it. This combined should ensure that users do not experience any regressions. However the feature may be lacking in some ways that we may want to address in follow up SRUs; it has not been used in the wild a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2038453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017401] Re: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2017401 Title: Unexpected / unwanted unattended-upgrades behaviour after kernel upgrade when Livepatch enabled Status in unattended-upgrades package in Ubuntu: Confirmed Status in unattended-upgrades source package in Focal: Confirmed Status in unattended-upgrades source package in Jammy: Confirmed Bug description: Following the resolution for bug #1747499, after a kernel upgrade when Livepatch is enabled, the current behaviour in unattended-upgrades (2.3ubuntu0.2 and later) is not to touch /var/run/reboot-required so as not to confuse users with two separate messages calling for a restart in motd. This functionality is implemented in the script at /etc/kernel/postinst.d/unattended-upgrades. While this works as intended in terms of suppressing an extra message in motd, it defeats the ability of unattended-upgrades to restart automatically with the new kernel, which is reliant on /var/run/reboot-required being present. This is unexpected / unwanted behaviour in scenarios where a) Livepatch is being used to provide fast-response kernel patching; and b) Unattended-Upgrade::Automatic-Reboot is set to true, to enable automatic reboots during a regular maintenance window. In this case, without administrative intervention, the system could never boot into the new kernel even though it would be expected to, leaving Livepatch to do all the heavy lifting indefinitely, and unnecessarily. I believe this counts as a regression caused by the resolution to bug #1747499. It also has the potential to be a security threat if Livepatch doesn't work comprehensively for a particular kernel flaw, and an administrator is reliant on expected behaviour according to unattended-upgrades settings. Potential options for a fix that come to mind: 1. Revert to original behaviour in /etc/kernel/postinst.d/unattended-upgrades, and change the ***System restart required*** message to be less alarming or confusing when the cause is a kernel upgrade that's being patched by Livepatch. 2. Add an extra configuration setting (eg Unattended-Upgrade::Automatic-Reboot-After-Livepatch) that triggers a reboot when it's 'recommended' by Livepatch, not reliant on the presence of /var/run/reboot-required. 3. Add support in /etc/kernel/postinst.d/unattended-upgrades for an extra file somewhere. When present, /var/run/reboot-required is always touched, even if Livepatch is enabled. (This is my first time reporting a bug in this system, and I apologise if I haven't followed the usual descriptive format.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2017401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034539] Re: Create the usbmux user in the preinst script
** Description changed: The installation of this package as part of the upgrade process from Lunar to Mantic (it's already present in Desktop images so it's not a problem there apparently) is triggering an issue in Netplan https://bugs.launchpad.net/netplan/+bug/1999178 This package will install a udev .rules file referring to a user that will be created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 + + + How to reproduce the issue: launch a LXD Lunar default or cloud image and try to do a do-release-upgrade to mantic. You'll notice that at some point during the "setting up" phase the process will stuck every time a install script calls a systemctl daemon-reload. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/2034539 Title: Create the usbmux user in the preinst script Status in usbmuxd package in Ubuntu: New Bug description: The installation of this package as part of the upgrade process from Lunar to Mantic (it's already present in Desktop images so it's not a problem there apparently) is triggering an issue in Netplan https://bugs.launchpad.net/netplan/+bug/1999178 This package will install a udev .rules file referring to a user that will be created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 How to reproduce the issue: launch a LXD Lunar default or cloud image and try to do a do-release-upgrade to mantic. You'll notice that at some point during the "setting up" phase the process will stuck every time a install script calls a systemctl daemon-reload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/2034539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted
This bug was fixed in the package linux - 5.4.0-164.181 --- linux (5.4.0-164.181) focal; urgency=medium * focal/linux: 5.4.0-164.181 -proposed tracker (LP: #2033867) * Please enable Renesas RZ platform serial installer (LP: #2022361) - [Config] enable hihope RZ/G2M serial console * Azure: hv_netvsc: add support for vlans in AF_PACKET mode (LP: #2030872) - hv_netvsc: add support for vlans in AF_PACKET mode * systemd mount units fail during boot, while file system is correctly mounted (LP: #1837227) - list: introduce list_for_each_continue() - proc/mounts: add cursor * CVE-2023-40283 - Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_ready_cb * CVE-2023-20588 - x86/bugs: Increase the x86 bugs vector size to two u32s - x86/CPU/AMD: Do not leak quotient data after a division by 0 - x86/CPU/AMD: Fix the DIV(0) initial fix attempt * CVE-2023-4194 - net: tun_chr_open(): set sk_uid from current_fsuid() - net: tap_open(): set sk_uid from current_fsuid() * CVE-2023-1206 - tcp: Reduce chance of collisions in inet6_hashfn(). * CVE-2021-4001 - bpf: Fix toctou on read-only map's constant scalar tracking * Focal update: v5.4.248 upstream stable release (LP: #2031121) - test_firmware: fix a memory leak with reqs buffer - KEYS: asymmetric: Copy sig and digest in public_key_verify_signature() - dasd: refactor dasd_ioctl_information - s390/dasd: Use correct lock while counting channel queue length - power: supply: ab8500: Fix external_power_changed race - power: supply: sc27xx: Fix external_power_changed race - power: supply: bq27xxx: Use mod_delayed_work() instead of cancel() + schedule() - ARM: dts: vexpress: add missing cache properties - power: supply: Ratelimit no data debug output - platform/x86: asus-wmi: Ignore WMI events with codes 0x7B, 0xC0 - regulator: Fix error checking for debugfs_create_dir - irqchip/meson-gpio: Mark OF related data as maybe unused - power: supply: Fix logic checking if system is running from battery - btrfs: handle memory allocation failure in btrfs_csum_one_bio - parisc: Improve cache flushing for PCXL in arch_sync_dma_for_cpu() - parisc: Flush gatt writes and adjust gatt mask in parisc_agp_mask_memory() - MIPS: Alchemy: fix dbdma2 - mips: Move initrd_start check after initrd address sanitisation. - xen/blkfront: Only check REQ_FUA for writes - drm:amd:amdgpu: Fix missing buffer object unlock in failure path - ocfs2: fix use-after-free when unmounting read-only filesystem - ocfs2: check new file size on fallocate call - nios2: dts: Fix tse_mac "max-frame-size" property - nilfs2: fix incomplete buffer cleanup in nilfs_btnode_abort_change_key() - nilfs2: fix possible out-of-bounds segment allocation in resize ioctl - kexec: support purgatories with .text.hot sections - powerpc/purgatory: remove PGO flags - nouveau: fix client work fence deletion race - RDMA/uverbs: Restrict usage of privileged QKEYs - net: usb: qmi_wwan: add support for Compal RXM-G1 - ALSA: hda/realtek: Add a quirk for Compaq N14JP6 - Remove DECnet support from kernel - [Config] updateconfigs for DECNET - USB: serial: option: add Quectel EM061KGL series - serial: lantiq: add missing interrupt ack - usb: dwc3: gadget: Reset num TRBs before giving back the request - spi: spi-fsl-dspi: Remove unused chip->void_write_data - spi: fsl-dspi: avoid SCK glitches with continuous transfers - netfilter: nfnetlink: skip error delivery on batch in case of ENOMEM - ping6: Fix send to link-local addresses with VRF. - RDMA/rxe: Remove the unused variable obj - RDMA/rxe: Removed unused name from rxe_task struct - RDMA/rxe: Fix the use-before-initialization error of resp_pkts - iavf: remove mask from iavf_irq_enable_queues() - IB/uverbs: Fix to consider event queue closing also upon non-blocking mode - IB/isert: Fix dead lock in ib_isert - IB/isert: Fix possible list corruption in CMA handler - IB/isert: Fix incorrect release of isert connection - ipvlan: fix bound dev checking for IPv6 l3s mode - sctp: fix an error code in sctp_sf_eat_auth() - igb: fix nvm.ops.read() error handling - drm/nouveau/dp: check for NULL nv_connector->native_mode - drm/nouveau/kms: Don't change EDID when it hasn't actually changed - drm/nouveau: add nv_encoder pointer check for NULL - net/sched: cls_api: Fix lockup on flushing explicitly created chain - net: lapbether: only support ethernet devices - net: tipc: resize nlattr array to correct size - selftests/ptp: Fix timestamp printf format for PTP_SYS_OFFSET - afs: Fix vlserver probe RTT handling - neighbour: Remove unused inline function neigh_key_eq16() - net: Remove unused inline function dst_hold_and_use() - neighbour: delete neigh_lookup_nodev as not used -
[Touch-packages] [Bug 2038446] [NEW] mantic:linux: net:rtnetlink.sh: address proto IPv(4/6) failing
Public bug reported: 9017s 12:26:37 DEBUG| [stdout] # PASS: neigh get 9018s 12:26:38 DEBUG| [stdout] # PASS: bridge_parent_id 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9018s 12:26:38 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9018s 12:26:38 DEBUG| [stdout] # FAIL: address proto IPv4 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9019s 12:26:39 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9019s 12:26:39 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9019s 12:26:39 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9019s 12:26:39 DEBUG| [stdout] # FAIL: address proto IPv6 ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Mantic) Importance: Medium Status: Confirmed ** Tags: kernel-adt-failure ** Also affects: apparmor (Ubuntu Mantic) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: apparmor (Ubuntu) ** No longer affects: apparmor (Ubuntu Mantic) ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2038446 Title: mantic:linux: net:rtnetlink.sh: address proto IPv(4/6) failing Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed Bug description: 9017s 12:26:37 DEBUG| [stdout] # PASS: neigh get 9018s 12:26:38 DEBUG| [stdout] # PASS: bridge_parent_id 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9018s 12:26:38 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9018s 12:26:38 DEBUG| [stdout] # FAIL: address proto IPv4 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9018s 12:26:38 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9019s 12:26:39 DEBUG| [stdout] # Error: either "dev" is duplicate, or "proto" is a garbage. 9019s 12:26:39 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9019s 12:26:39 DEBUG| [stdout] # RTNETLINK answers: Cannot assign requested address 9019s 12:26:39 DEBUG| [stdout] # FAIL: address proto IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Updated from related card - https://github.com/thesofproject/linux/issues/4055 ** Bug watch added: github.com/thesofproject/linux/issues #4055 https://github.com/thesofproject/linux/issues/4055 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038443] [NEW] mantic:linux: ubuntu_qrt_apparmor: ApparmorTestsuites.test_regression_testsuiteattach_disconnected.
Public bug reported: This might be apparmor, the test case, kernel or anything in between: 7720s running attach_disconnected 7720s Fatal Error (unix_fd_server): Unable to run test sub-executable ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: apparmor (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Medium Status: Confirmed ** Tags: kernel-adt-failure ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Medium Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2038443 Title: mantic:linux: ubuntu_qrt_apparmor: ApparmorTestsuites.test_regression_testsuiteattach_disconnected. Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in apparmor source package in Mantic: New Status in linux source package in Mantic: Confirmed Bug description: This might be apparmor, the test case, kernel or anything in between: 7720s running attach_disconnected 7720s Fatal Error (unix_fd_server): Unable to run test sub-executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2038443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038439] [NEW] Update network-manager to 1.44.2
Public bug reported: New upstream bugfix release in the stable 1.44 series https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/compare/1.44.0...1.44.2 ** Affects: network-manager (Ubuntu) Importance: Undecided Assignee: Jeremy Bícha (jbicha) Status: In Progress ** Tags: mantic upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2038439 Title: Update network-manager to 1.44.2 Status in network-manager package in Ubuntu: In Progress Bug description: New upstream bugfix release in the stable 1.44 series https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/compare/1.44.0...1.44.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2038439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic
Taking a quick look at the logs for arm64, https://autopkgtest.ubuntu.com/packages/systemd/mantic/arm64, I only see this specific failure for newer kernels. Have you tried to reproduce this locally to see if it is in fact introduced by a kernel change? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2038433 Title: systemd autopkgtest regression on arm64 and s390x on mantic Status in systemd package in Ubuntu: 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/systemd/+bug/2038433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038436] [NEW] System doesnt recognize second monitor
Public bug reported: I am using an old monitor which using a DVI connectors but I used a DVI to HDMI adapter which works fine on Windows operating system... My monitor is HP W2072a... I hope with the information provided helps... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 21:17:37 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Device [1b50:1018] InstallationDate: Installed on 2023-09-30 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ILLEGEAR SDN BHD ATOMIC 16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=e60cc65c-b597-415b-b294-3cb6a76ecbd0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2022 dmi.bios.release: 0.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q3AIL.02 dmi.board.asset.tag: Default string be filled by O.E.M dmi.board.name: ATOMIC dmi.board.vendor: ILLEGEAR SDN BHD dmi.board.version: Default string be filled by O.E.M dmi.chassis.asset.tag: Default string be filled by O.E.M dmi.chassis.type: 9 dmi.chassis.vendor: Default string be filled by O.E.M dmi.chassis.version: Default string be filled by O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ3AIL.02:bd07/26/2022:br0.2:svnILLEGEARSDNBHD:pnATOMIC16:pvrDefaultstringbefilledbyO.E.M:rvnILLEGEARSDNBHD:rnATOMIC:rvrDefaultstringbefilledbyO.E.M:cvnDefaultstringbefilledbyO.E.M:ct9:cvrDefaultstringbefilledbyO.E.M:skuATOMIC16-ADL1: dmi.product.family: ATOMIC dmi.product.name: ATOMIC 16 dmi.product.sku: ATOMIC16-ADL1 dmi.product.version: Default string be filled by O.E.M dmi.sys.vendor: ILLEGEAR SDN BHD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2038436 Title: System doesnt recognize second monitor Status in xorg package in Ubuntu: New Bug description: I am using an old monitor which using a DVI connectors but I used a DVI to HDMI adapter which works fine on Windows operating system... My monitor is HP W2072a... I hope with the information provided helps... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 21:17:37 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Device [1b50:1018] InstallationDate: Installed on 2023-09-30 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ILLEGEAR SDN BHD ATOMIC 16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=e60cc65c-b597-415b-b294-3cb6a76ecbd0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2022 dmi.bios.release: 0.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q3AIL.02 dmi.board.asset.tag: Default string be filled by O.E.M dmi.board.name: ATOMIC dmi.board.vendor: ILLEGEAR SDN BHD dmi.board.version: Default string be filled by O.E.M dmi.chassis.asset.tag: Default string be filled by O.E.M dmi.chassis.type: 9 dmi.chassis.vendor:
[Touch-packages] [Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
FYI, ran into this same issue with Debian bookworm's apt-get (2.6.1) hanging indefinitely talking to an apt-cacher-ng 3.7.x instance, easily reproducible by having ansible run an `apt-get update` on ~20-25 machines simultaneously. Problem disappears when switching back to apt- cacher-ng 3.6.x, so +1 for the apt-cacher-ng bug linked above. Still, the problem persists even when invoking apt-get with `-o Acquire::http::Timeout=120`, so presumably there must still be something bugged on the side of apt itself not properly adhering to the configured timeout. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2003851 Title: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04 Status in apt package in Ubuntu: Confirmed Bug description: Hi! Yesterday I spotted several machines of ours where a period `apt-get update` was stalled. The `http` children were hanging in `WaitFd` (waiting for parent instructions/queue). The parent was looping in `AcquireUpdate` every 500ms. We have a cronjob that runs every few hours which calls `apt-get update` and does some post-processing. We noticed that several of them had stalled at some point in time. Killing the parent (apt-get) got it unstuck, removing the locks. Example: ``` # apt-get update Reading package lists... Done E: Could not get lock /var/lib/apt/lists/lock. It is held by process 154026 (apt-get) N: Be aware that removing the lock file is not a solution and may break your system. E: Unable to lock directory /var/lib/apt/lists/ ``` Task listing: ``` root 153929 \_ /usr/sbin/CRON -f -P root 153942 \_ /bin/sh -c [ -x /etc/zabbix/scripts/dpkg.updates ] && /etc/zabbix/scripts/dpkg.updates --cron root 153943 \_ /bin/sh /etc/zabbix/scripts/dpkg.updates --cron root 154026 \_ apt-get update _apt 154029 \_ /usr/lib/apt/methods/http _apt 154030 \_ /usr/lib/apt/methods/http _apt 154031 \_ /usr/lib/apt/methods/http _apt 154033 \_ /usr/lib/apt/methods/gpgv ``` Open (TCP) sockets. All have 1 item in the Recv-Q (probably a FIN or RST?): ``` # netstat -apn | grep -E '154026|154029|154030|154031|154033' tcp 1 0 10.x.x.x:60868 217.x.x.x:80 CLOSE_WAIT 154030/http tcp 1 0 10.x.x.x:40756 178.x.x.x:80 CLOSE_WAIT 154029/http tcp 1 0 10.x.x.x:56818 185.x.x.x:80 CLOSE_WAIT 154031/http ``` All children (including gpgv) were waiting using pselect6(1, [0], NULL, NULL, NULL, NULL). The parent (apt-get) was waiting using pselect6(10, [5 6 7 9], [], NULL, {tv_sec=0, tv_nsec=5}, NULL). The http sockets in the children were at fd=3. Parent lsof: ``` # lsof -p 154026 +E ... apt-get 154026 root4uW REG8,10 262281 /var/lib/apt/lists/lock apt-get 154026 root5r FIFO 0,13 0t0 4015176 pipe 154029,http,1w apt-get 154026 root6r FIFO 0,13 0t0 4012448 pipe 154030,http,1w apt-get 154026 root7r FIFO 0,13 0t0 4015192 pipe 154031,http,1w apt-get 154026 root8w FIFO 0,13 0t0 4015177 pipe 154029,http,0r apt-get 154026 root9r FIFO 0,13 0t0 4015233 pipe 154033,gpgv,1w apt-get 154026 root 10w FIFO 0,13 0t0 4012449 pipe 154030,http,0r apt-get 154026 root 12w FIFO 0,13 0t0 4015193 pipe 154031,http,0r apt-get 154026 root 14w FIFO 0,13 0t0 4015234 pipe 154033,gpgv,0r http 154029 _apt0r FIFO 0,13 0t0 4015177 pipe 154026,apt-get,8w http 154029 _apt1w FIFO 0,13 0t0 4015176 pipe 154026,apt-get,5r http 154030 _apt0r FIFO 0,13 0t0 4012449 pipe 154026,apt-get,10w http 154030 _apt1w FIFO 0,13 0t0 4012448 pipe 154026,apt-get,6r http 154031 _apt0r FIFO 0,13 0t0 4015193 pipe 154026,apt-get,12w http 154031 _apt1w FIFO 0,13 0t0 4015192 pipe 154026,apt-get,7r gpgv 154033 _apt0r FIFO 0,13 0t0 4015234 pipe 154026,apt-get,14w gpgv 154033 _apt1w FIFO 0,13 0t0 4015233 pipe 154026,apt-get,9r ``` So: - apt-get is waiting for any data written by any of its four children (at fd 5/6/7/9) - http and gpgv are waiting for any data written by their parent (at their respective fd 0) Parent backtrace: ``` #0 0x7f420116a74d in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f420153fb5d in pkgAcquire::Run(int) () from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 #2 0x7f420161d535 in AcquireUpdate(pkgAcquire&, int, bool, bool) () from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 #3 0x7f420161d986 in ListUpdate(pkgAcquireStatus&, pkgSourceList&, int) () from
[Touch-packages] [Bug 2033949] Re: Does not work with Ubuntu sources in deb822 format
Well the bug remains nonetheless, just the importance gets lower ** Changed in: software-properties (Ubuntu Mantic) Importance: High => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2033949 Title: Does not work with Ubuntu sources in deb822 format Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Mantic: In Progress Bug description: On my Mantic I have sources in new deb822 format. Starting software-properties-gtk seems my server is Main server, but from /etc/apt/sources.list.d/ubuntu.sources I see server from Italy and I software-properties-gtk seems unable to change. corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/ubuntu.sources Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic mantic-updates mantic-backports Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg corrado@corrado-n16-mm-0901:~$ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-gtk 0.99.39 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 2 10:33:12 2023 InstallationDate: Installed on 2023-09-01 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2033949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by
Thank you for the additional context! That seems like it will solve the problem on newer releases of ubuntu; am I right in thinking that older releases would still suffer from the gap between python-apt and sources.list? We encountered the issue on focal (20.04). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1862764 Title: add-apt-repository should use signed-by Status in python-apt package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Fix Released Status in software-properties package in Debian: New Bug description: add-apt-repository should use signed-by apt sources.list syntax supports limiting which keys are used to sign a given repo. It would be nice for add-apt-repository to import the key somewhere else but trusted.gpg.d and then specify path to it, using the "signed- by" field. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 12:01:49 2020 InstallationDate: Installed on 2016-01-26 (1477 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2019-01-15 (391 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-01-10T16:24:15.968394 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1862764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038433] [NEW] systemd autopkgtest regression on arm64 and s390x on mantic
Public bug reported: 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 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Mantic) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Also affects: systemd (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2038433 Title: systemd autopkgtest regression on arm64 and s390x on mantic Status in systemd package in Ubuntu: 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:
[Touch-packages] [Bug 2037497]
*** Bug 2241332 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in Mutter: Fix Released Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in mesa package in Fedora: Confirmed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
I'd say that's very likely. That mesa upgrade just landed in the archive a few days ago and the trace you reported looks more like how a mesa bug manifests. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0:
[Touch-packages] [Bug 2037569] Re: udev issues with mantic beta
Hi Dan, I've took the manytic daily from yesterday (Oct 3rd) and checked if the updated udisks2 package is in - which is the case - and gave it a try. I did multiple different installations - all with DASDs, on LPAR and on z/VM. Installations with a single DASD or with multiple DASDs (even combining them to a bigger disk using LVM), and I didn't faced udev issues anymore. I checked with top during the installation as well as after the post-install reboot was completed -- all good. So many thanks for your fix and upload on this (and Seb's review) ! ** Changed in: ubuntu-z-systems Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Fix Released Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Fix Released Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037569] Re: udev issues with mantic beta
** Tags added: architecture-s39064 bugnameltc-203787 severity-high targetmilestone-inin--- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Fix Released Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Fix Released Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Thanks Mario! I checked, and I have the newest mesa: ``` $ apt search mesa-vdpau Sorting... Done Full Text Search... Done mesa-vdpau-drivers/mantic,now 23.2.1-1ubuntu2 amd64 [installed,automatic] Mesa VDPAU video acceleration drivers ``` Funny thing is that the bug is no longer reproducible - everything is working properly, yay! Could it be that mesa was upgraded a couple of days ago, resolving the issue? Anyways, the issue looks to be fixed now. Thanks again! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [
[Touch-packages] [Bug 2037205] Re: setuptools: FTBFS in mantic
** Changed in: setuptools (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2037205 Title: setuptools: FTBFS in mantic Status in dh-python package in Ubuntu: New Status in setuptools package in Ubuntu: Fix Committed Status in dh-python package in Debian: New Status in setuptools package in Debian: New Bug description: As seen in the mantic test rebuild [1], setuptools 68.1.2-1 currently FTBFS: Traceback (most recent call last): File "/<>/setuptools/config/setupcfg.py", line 284, in __setitem__ current_value = getattr(target_obj, option_name) AttributeError: 'MinimalDistribution' object has no attribute 'entry_points' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/<>/setup.py", line 92, in dist = setuptools.setup(**setup_params) File "/<>/setuptools/__init__.py", line 106, in setup _install_setup_requires(attrs) File "/<>/setuptools/__init__.py", line 77, in _install_setup_requires dist.parse_config_files(ignore_option_errors=True) File "/<>/setuptools/dist.py", line 895, in parse_config_files setupcfg.parse_configuration( File "/<>/setuptools/config/setupcfg.py", line 177, in parse_configuration options.parse() File "/<>/setuptools/config/setupcfg.py", line 500, in parse section_parser_method(section_options) File "/<>/setuptools/config/setupcfg.py", line 727, in parse_section_entry_points self['entry_points'] = parsed File "/<>/setuptools/config/setupcfg.py", line 286, in __setitem__ raise KeyError(option_name) KeyError: 'entry_points' E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: python3.11 setup.py clean [1] https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2037205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
This bug was fixed in the package initramfs-tools - 0.142ubuntu15 --- initramfs-tools (0.142ubuntu15) mantic; urgency=medium * scripts/functions: do not fail to configure networking too quickly. In particular make sure an unsuccessful attempt to run DHCP takes at least $ROUNDTTT seconds. (LP: #2037202) -- Michael Hudson-Doyle Wed, 04 Oct 2023 12:02:13 +1300 ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: Fix Released Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026757] Re: dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates
@Sergio so i still see[1][2] those segfaults with those new packages:- ii dnsmasq-base 2.86-1.1ubuntu0.4~ppa1 amd64Small caching DNS proxy and DHCP/TFTP server ii dnsmasq-utils 2.86-1.1ubuntu0.4~ppa1 amd64Utilities for manipulating DHCP leases Can you check if that patch is really applied on those packages? [1] https://dcd105b404f93fc08fa3-82141499a48343cfb1270dc186f5ec2f.ssl.cf5.rackcdn.com/897277/1/check/ironic-standalone/1d6d1a0/controller/logs/syslog.txt [2] Oct 04 06:53:17 np0035409761 kernel: dnsmasq[67022]: segfault at 80c8 ip 7f4ef40ce3fe sp 7fff2346dab0 error 4 in libc.so.6[7f4ef4051000+195000] Oct 04 06:53:17 np0035409761 kernel: Code: 99 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 12 3a 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 98 39 17 00 64 48 83 3a Oct 04 06:53:53 np0035409761 kernel: dnsmasq[77967]: segfault at d118 ip 7f31c3b403fe sp 7ffe7ed6cc40 error 4 in libc.so.6[7f31c3ac3000+195000] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2026757 Title: dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates Status in Ironic: New Status in neutron: New Status in dnsmasq package in Ubuntu: Invalid Status in dnsmasq source package in Jammy: Incomplete Status in dnsmasq source package in Kinetic: Won't Fix Status in dnsmasq source package in Lunar: Invalid Status in dnsmasq source package in Mantic: Invalid Bug description: The Ironic project's CI has been having major blocking issues moving to utilizing Ubuntu Jammy and with some investigation we were able to isolate the issues down to the dhcp updates causing dnsmasq to crash on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds similar to an issue known about to the dnsmasq maintainers, where dnsmasq would crash with updates occurring due to configuration refresh[0]. This resulted in us upgrading dnsmasq to the version which ships with Ubuntu Lunar. Which was no better. Dnsmasq still crashed upon record updates for addresses and ports getting configuration added/changed/removed. We later downgraded to the version of dnsmasq shipped in Ubuntu Focal, and dnsmasq stopped crashing and appeared stable enough to utilize for CI purposes. ** Kernel log from Ubuntu Jammy Package ** [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000] [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000] [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000] [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000] [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000] [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000] [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000] [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00
Re: [Touch-packages] [Bug 2038313] Re: upscayl software do not work
Hi, error message in picture attached. Best regards, Anders bodin On Wed, 4 Oct 2023 at 07:40, Daniel van Vugt <2038...@bugs.launchpad.net> wrote: > I don't know if this counts as "do not work", but it seems clear that > Mesa's Vulkan driver for Haswell is incomplete and it's fallen back to > LLVM (software rendering). That should "work" very slowly still. Was > there actually any error? > > Also this change to your system is not supported by Ubuntu: > > libvulkan1 1.3.261.0~rc1-1lunarg22.04-1 [origin: vulkan.lunarg.com] > > > ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) > > ** Changed in: mesa (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2038313 > > Title: > upscayl software do not work > > Status in mesa package in Ubuntu: > Incomplete > > Bug description: > upscayl software do not work > > BACKEND REPORTED: Selected File Path: > /home/anders/Downloads/1695568515335.png > Selected Image Path: /home/anders/Downloads/1695568515335.png > Selected Image Directory: /home/anders/Downloads > imagePath: /home/anders/Downloads/1695568515335.png > Extension: png > Resetting Upscaled Image Path > UPSCAYL > BACKEND REPORTED: Updating Overwrite: false > BACKEND REPORTED: ✅ Upscayl Variables: [object Object] > BACKEND REPORTED: Upscayl Command: > -i,/home/anders/Downloads/1695568515335.png,-o,/home/anders/Downloads/1695568515335_upscayl_4x_ultrasharp.png,-s,4,-m,/tmp/.mount_upscaygPuzIl/resources/models,-n,ultrasharp,,,-f,png > BACKEND REPORTED: Updating Child Processes: [object Object] > BACKEND REPORTED: Updating Stopped: false > BACKEND REPORTED: image upscayl: MESA-INTEL: warning: Haswell > Vulkan support is incomplete > > UPSCAYL_PROGRESS: MESA-INTEL: warning: Haswell Vulkan support is > incomplete > > BACKEND REPORTED: image upscayl: [0 Intel(R) HD Graphics 4600 (HSW > GT2)] queueC=0[1] queueG=0[1] queueT=0[1] > [0 Intel(R) HD Graphics 4600 (HSW GT2)] bugsbn1=0 bugbilz=0 > bugcopc=0 bugihfa=0 > [0 Intel(R) HD Graphics 4600 (HSW GT2)] fp16-p/s/a=1/0/0 > int8-p/s/a=1/0/0 > [0 Intel(R) HD Graphics 4600 (HSW GT2)] subgroup=32 basic=1 vote=1 > ballot=1 shuffle=1 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] queueC=0[1] queueG=0[1] > queueT=0[1] > [1 llvmpipe (LLVM 15.0.7, 256 bits)] bugsbn1=0 bugbilz=0 bugcopc=0 > bugihfa=0 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] fp16-p/s/a=1/1/1 int8-p/s/a=1/1/1 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] subgroup=8 basic=1 vote=1 > ballot=1 shuffle=1 > > UPSCAYL_PROGRESS: [0 Intel(R) HD Graphics 4600 (HSW GT2)] > queueC=0[1] queueG=0[1] queueT=0[1] > [0 Intel(R) HD Graphics 4600 (HSW GT2)] bugsbn1=0 bugbilz=0 > bugcopc=0 bugihfa=0 > [0 Intel(R) HD Graphics 4600 (HSW GT2)] fp16-p/s/a=1/0/0 > int8-p/s/a=1/0/0 > [0 Intel(R) HD Graphics 4600 (HSW GT2)] subgroup=32 basic=1 vote=1 > ballot=1 shuffle=1 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] queueC=0[1] queueG=0[1] > queueT=0[1] > [1 llvmpipe (LLVM 15.0.7, 256 bits)] bugsbn1=0 bugbilz=0 bugcopc=0 > bugihfa=0 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] fp16-p/s/a=1/1/1 int8-p/s/a=1/1/1 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] subgroup=8 basic=1 vote=1 > ballot=1 shuffle=1 > > ProblemType: Bug > DistroRelease: Ubuntu 23.04 > Package: xorg 1:7.7+23ubuntu2 > ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 > Uname: Linux 6.2.0-33-generic x86_64 > ApportVersion: 2.26.1-0ubuntu2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: unknown > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Tue Oct 3 14:45:19 2023 > DistUpgraded: Fresh install > DistroCodename: lunar > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation 4th Gen Core Processor Integrated Graphics Controller > [8086:0416] (rev 06) (prog-if 00 [VGA controller]) > Subsystem: Fujitsu Limited. 4th Gen Core Processor Integrated > Graphics Controller [10cf:17af] > InstallationDate: Installed on 2023-09-06 (26 days ago) > InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 > (20230418) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 005: ID 1c4f:0034 SiGma Micro XM102K Optical Wheel Mouse >Bus 001 Device 002: ID 8087:07dc Intel Corp. Bluetooth wireless > interface >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=xhci_hcd/4p, 5000M >/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M >|__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M >|__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M >|__ Port 9: Dev 5, If 0, Class=Human Interface
[Touch-packages] [Bug 2033949] Re: Does not work with Ubuntu sources in deb822 format
Installing from Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) I see the sources.list in the old format and /etc/apt/sources.list.d/ubuntu.sources no longer exist, so I think this bug is to be changed to Invalid? or Fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2033949 Title: Does not work with Ubuntu sources in deb822 format Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Mantic: In Progress Bug description: On my Mantic I have sources in new deb822 format. Starting software-properties-gtk seems my server is Main server, but from /etc/apt/sources.list.d/ubuntu.sources I see server from Italy and I software-properties-gtk seems unable to change. corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/ubuntu.sources Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic mantic-updates mantic-backports Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://it.archive.ubuntu.com/ubuntu Suites: mantic-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg corrado@corrado-n16-mm-0901:~$ ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-gtk 0.99.39 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 2 10:33:12 2023 InstallationDate: Installed on 2023-09-01 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2033949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by
Note that as we move towards deb822 everywhere there will be less issues of that sort, as the deb822 backend recognizes every option (even unknown ones) and software-properties allows you to edit all of them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1862764 Title: add-apt-repository should use signed-by Status in python-apt package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Fix Released Status in software-properties package in Debian: New Bug description: add-apt-repository should use signed-by apt sources.list syntax supports limiting which keys are used to sign a given repo. It would be nice for add-apt-repository to import the key somewhere else but trusted.gpg.d and then specify path to it, using the "signed- by" field. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 12:01:49 2020 InstallationDate: Installed on 2016-01-26 (1477 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2019-01-15 (391 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-01-10T16:24:15.968394 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1862764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by
This has been fixed a couple of months ago for PPAs and I think other shortcuts; they now use deb822 .sources files with Signed-By parameter. ** Changed in: software-properties (Ubuntu) Status: Confirmed => Fix Released ** Changed in: python-apt (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1862764 Title: add-apt-repository should use signed-by Status in python-apt package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Fix Released Status in software-properties package in Debian: New Bug description: add-apt-repository should use signed-by apt sources.list syntax supports limiting which keys are used to sign a given repo. It would be nice for add-apt-repository to import the key somewhere else but trusted.gpg.d and then specify path to it, using the "signed- by" field. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 12:01:49 2020 InstallationDate: Installed on 2016-01-26 (1477 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2019-01-15 (391 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-01-10T16:24:15.968394 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1862764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online
I have also successfully verified that -proposed amd64 kernel `6.5.0-7-generic` results in successful network configuration when tested using qemu on an amd64 host with older hardware (ThinkPad T460 with 6th gen intel i5 which is the same hardware which we were able to reproduce the issue on previously). See https://people.canonical.com/~philroche/20231003-mantic-minimal- proposed-kernel/amd64/ for cloud-init logs, some debug output and test image. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862764] Re: add-apt-repository should use signed-by
We encountered this with an ubuntu system using salt, which uses the python-apt package. We have sent a report and patch to python-apt upstream. The package is maintained by debian, and we are uncertain whether debian will consider it a bug, if these options are only used by ubuntu. There wasn't any better place we could find to send a patch, though. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051852 ** Bug watch added: Debian Bug tracker #1051852 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051852 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1862764 Title: add-apt-repository should use signed-by Status in python-apt package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in software-properties package in Debian: New Bug description: add-apt-repository should use signed-by apt sources.list syntax supports limiting which keys are used to sign a given repo. It would be nice for add-apt-repository to import the key somewhere else but trusted.gpg.d and then specify path to it, using the "signed- by" field. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 12:01:49 2020 InstallationDate: Installed on 2016-01-26 (1477 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2019-01-15 (391 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-01-10T16:24:15.968394 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1862764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online
@xnox I have successfully verified that -proposed arm64 kernel `6.5.0-7-generic` results in successful network configuration when tested using qemu on an amd64 host. See https://people.canonical.com/~philroche/20231003-mantic-minimal- proposed-kernel/ for cloud-init logs, some debug output and test image. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028082] Re: Update glib to 2.76.4
Hello Jeremy, or anyone else affected, Accepted glib2.0 into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.76.4-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glib2.0 (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2028082 Title: Update glib to 2.76.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706618/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706617/+files/rfkill.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706616/+files/getfacl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706614/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706613/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706612/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706611/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706610/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706609/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706608/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706607/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706606/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706605/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706604/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706603/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706602/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB 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.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
apport information ** Tags added: apport-collected ** Description changed: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i + --- + ProblemType: Bug + ApportVersion: 2.27.0-0ubuntu4 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 23.10 + InstallationDate: Installed on 2022-05-28 (494 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + InterestingModules: rfcomm bnep btusb bluetooth + MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} + Package: linux + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 + RebootRequiredPkgs: Error: path contained symlinks. + Tags: mantic + Uname: Linux 6.5.0-5-generic x86_64 + UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) + UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/10/2023 + dmi.bios.release: 1.56 + dmi.bios.vendor: LENOVO + dmi.bios.version: N34ET56W (1.56 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20W000AMPB + 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.42 + dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: + dmi.product.family: ThinkPad T14 Gen 2i + dmi.product.name: 20W000AMPB + dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i + dmi.product.version: ThinkPad T14 Gen 2i + dmi.sys.vendor: LENOVO + hciconfig: + hci0:Type: Primary Bus: USB + BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING + RX bytes:22183 acl:0 sco:0 events:3531 errors:0 + TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706601/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs
[Touch-packages] [Bug 2026757] Re: dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates
Thanks @Sergio, i missed those ppa links earlier, pushed test patch[1] to validate it. [1] https://review.opendev.org/c/openstack/ironic/+/897277 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2026757 Title: dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates Status in Ironic: New Status in neutron: New Status in dnsmasq package in Ubuntu: Invalid Status in dnsmasq source package in Jammy: Incomplete Status in dnsmasq source package in Kinetic: Won't Fix Status in dnsmasq source package in Lunar: Invalid Status in dnsmasq source package in Mantic: Invalid Bug description: The Ironic project's CI has been having major blocking issues moving to utilizing Ubuntu Jammy and with some investigation we were able to isolate the issues down to the dhcp updates causing dnsmasq to crash on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds similar to an issue known about to the dnsmasq maintainers, where dnsmasq would crash with updates occurring due to configuration refresh[0]. This resulted in us upgrading dnsmasq to the version which ships with Ubuntu Lunar. Which was no better. Dnsmasq still crashed upon record updates for addresses and ports getting configuration added/changed/removed. We later downgraded to the version of dnsmasq shipped in Ubuntu Focal, and dnsmasq stopped crashing and appeared stable enough to utilize for CI purposes. ** Kernel log from Ubuntu Jammy Package ** [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000] [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000] [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000] [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000] [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000] [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000] [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000] [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a ** Kernel log entries from Ubuntu Lunar package ** [234724.842339] dnsmasq[409843]: segfault at fffd ip 7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000] [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [234784.918116] dnsmasq[410019]: segfault at fffd ip 7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000] [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a [235022.163339] dnsmasq[410151]: segfault at fffd ip 7f21dd37f47e sp 7fff9bf416d0 error 5 in