Your message dated Fri, 19 Sep 2025 19:24:29 +0200 with message-id <20250919192429.04f5ad76@elisabeth> and subject line Re: Bug#1115397: passt: Segmentation fault when running pasta has caused the Debian Bug report #1115397, regarding passt: Segmentation fault when running pasta to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1115397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115397 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: passt Version: 0.0~git20250911.6cbcccc-1 Severity: grave Justification: renders package unusable Hi, I cannot run pasta command because it always crashes with segmentation fault. at 2025-09-17T00:27:04+08:00 ❯ pasta [1] 2824607 segmentation fault pasta -- System Information: Debian Release: forky/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.16.7+deb14-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages passt depends on: ii libc6 2.41-12 passt recommends no packages. Versions of packages passt suggests: ii apparmor 4.1.0-1 -- no debconf information -- ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---On Wed, 17 Sep 2025 14:14:45 +0200 Stefano Brivio <[email protected]> wrote: > On Wed, 17 Sep 2025 20:10:35 +0800 > ChangZhuo Chen (陳昌倬) <[email protected]> wrote: > > > On Wed, Sep 17, 2025 at 02:00:31PM +0200, Stefano Brivio wrote: > > > > > ...oops, sorry, I meant to ask if you could try with > > > 'aa-complain pasta' instead of aa-enforce (also as root or with sudo, > > > I forgot to mention). > > > > $ sudo aa-complain pasta > > Setting /usr/bin/pasta to complain mode. > > Warning: profile pasta represents multiple programs > > Warning: profile pasta represents multiple programs > > ...and, sorry, I took it for granted: try to run pasta after 'sudo > aa-complain pasta'? As I didn't get an answer here, I tried several upgrade paths: 1. removing the passt package altogether, manually removing all matching entries under /etc/apparmor.d/, then reinstalling the package with a 'dpkg --force-confmiss' command 2. reverting to the previous version (0.0~git20250503.587980c-2), and then upgrading back to 0.0~git20230309.7c7625d-1 3. reverting to a much older version without downstream commit 5bb812e79143 ("debian/rules: Override pasta symbolic links with hard links"), and then upgrading back to 0.0~git20230309.7c7625d-1 in all cases, pasta(1) can start regularly, with its profile in enforcing mode. The reporter seems to claim that the issue vanished now, but I'm not quite sure. However, I can't find a way to reproduce this, so my suspicion is that some AppArmor policy file wasn't installed properly because of some unexpected event during package installation or upgrade. For that reason, I'm closing this for the moment being. If anybody can reproduce this, please reopen this. I would need the following information, in case: a. after the failure, the last few lines from /var/log/audit/audit.log, if they report any related denial b. switch pasta to complain mode with 'aa-complain pasta' as root, (or with 'sudo aa-complain pasta'), *and then try to start it*. If it fails to start, matching lines from /var/log/audit/audit.log c. what was the upgrade or installation path that led to this situation Thanks in advance. -- Stefano
--- End Message ---
