Testing for plucky-proposed: ============================== 1. Reproduced error on plucky deb snapd 2.72+ubuntu25.04 (on plucky): ---------------------------------------------------------------------------
Created request-rules.json file with 10002 rules using the following python script: https://gist.github.com/olivercalder/ab99293cd888b231871d6b0fd51fa5c1 Ensure the prompting-client snap is installed. Confirm the snapd version: ``` $ snap version snap 2.72+ubuntu25.04 snapd 2.72+ubuntu25.04 series 16 ubuntu 25.04 kernel 6.14.0-36-generic architecture amd64 ``` Ensure prompting is initially disabled: ``` sudo snap set system experimental.apparmor-prompting=false ``` Copy the request rules file to the location: ``` sudo mkdir -p /var/lib/snapd/interfaces-requests sudo cp request-rules.json /var/lib/snapd/interfaces-requests/request-rules.json ``` Enable prompting: ``` sudo snap set system experimental.apparmor-prompting=true ``` Observe that snapd sits at 100% CPU usage and future snap commands (e.g. `snap list`) hang for several minutes, then error: ``` $ snap list error: cannot list snaps: cannot communicate with server: timeout exceeded while waiting for response ``` Thus, this bug is confirmed to occur with snapd 2.72+ubuntu25.04. 2. Update to plucky-proposed deb snapd 2.73+ubuntu25.04 (on plucky): -------------------------------------------------------------------------- Created request-rules.json file with 10002 rules using the following python script: https://gist.github.com/olivercalder/ab99293cd888b231871d6b0fd51fa5c1 Ensure the prompting-client snap is installed. Confirm the snapd version: ``` $ snap version snap 2.73+ubuntu25.04 snapd 2.73+ubuntu25.04 series 16 ubuntu 25.04 kernel 6.14.0-36-generic architecture amd64 ``` Ensure prompting is initially disabled: ``` sudo snap set system experimental.apparmor-prompting=false ``` Copy the request rules file to the location: ``` sudo mkdir -p /var/lib/snapd/interfaces-requests sudo cp request-rules.json /var/lib/snapd/interfaces-requests/request-rules.json ``` Enable prompting: ``` sudo snap set system experimental.apparmor-prompting=true ``` Observe that snapd restarts as usual, and after a few seconds, snapd is running again and subsequent snap commands (e.g. `snap list`) display their expected outputs immediately: ``` $ snap list Name Version Rev Tracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core22 20251009 2163 latest/stable canonical✓ base gnome-42-2204 0+git.837775c-sdk0+git.7b07595 226 latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable canonical✓ - prompting-client 0+git.d542a5d 104 latest/stable canonical✓ - snapd 2.72 25577 latest/stable canonical✓ snapd ``` Therefore, I can confirm that the bug is resolved with snapd 2.73+ubuntu25.04 on plucky. ** Tags removed: verification-needed-plucky ** Tags added: verification-done-plucky -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127189 Title: Too many permission prompting rules can prevent snapd to start To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2127189/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
