On Mon, Mar 25, 2024 at 05:16:57AM -0000, John Johansen wrote: > Do we know if there is a difference in the kernel between the runs?
> The 2.0.0.0~0ubuntu3 autopackage run log I was pointed at was on a > Linux 5.4.0-170-generic #188-Ubuntu > Do we know what kernel that 2.0.0-0ubuntu7 is failing on? There was a > change to when security checks were made in on the exec path, this > particular denial makes me wonder if we are seeing an artifact of that > here. All logs on https://autopkgtest.ubuntu.com/packages/c/cups-browsed/noble/armhf should include kernel information. Latest 2.0.0-0ubuntu8 failure has: 211s autopkgtest [22:10:53]: testbed running kernel: Linux 5.15.0-101-generic #111-Ubuntu SMP Wed Mar 6 18:01:01 UTC 2024 Last successful 2.0.0-0ubuntu3 log has: 349s autopkgtest [18:43:33]: testbed running kernel: Linux 5.4.0-170-generic #188-Ubuntu SMP Wed Jan 10 09:51:10 UTC 2024 But that was a retry of the release version of the package AFTER things started failing; https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/c/cups-browsed/20240322_173402_07be9@/log.gz is earlier and has: 351s autopkgtest [17:30:50]: testbed running kernel: Linux 5.4.0-170-generic #188-Ubuntu SMP Wed Jan 10 09:51:10 UTC 2024 so it's not a kernel difference. It appears to be a genuine change in the binaries when built with new toolchain that causes them to have a new mmap that wasn't there before? If I aa-enforce and run strace, I see: execve("/usr/sbin/cups-browsed", ["cups-browsed"], 0xffa82a54 /* 12 vars */) = -1 EACCES (Permission denied) so this failure happens before we even reach the executable? -- 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/2058866 Title: proposed-migration for cups-browsed 2.0.0-0ubuntu8 Status in apparmor package in Ubuntu: New Status in cups-browsed package in Ubuntu: New Bug description: cups-browsed 2.0.0-0ubuntu8 on armhf segfaults on startup (detected via an autopkgtest), early enough that LD_DEBUG=all gives no output. A local no-change rebuild of 2.0.0-0ubuntu7 succeeded and the executable ran, so 8 was uploaded to try to fix this. But the executable somehow ONLY runs as ./debian/cups-browsed/usr/sbin/cups- browsed and segfaults when invoked as /usr/sbin/cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2058866/+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
