Thank you for the info! The problem appears to be that when snapd starts up, it records a notice for *every* existing rule. Recording each notice (currently) requires acquiring the state lock, adding the notice, and releasing the state lock separately for each notice, resulting in the snapd state being re-marshalled and written to disk for every existing notice.
We don't need to be recording a new notice for every rule on snapd startup. Instead, we should only record notices for rules which have expired or been merged or modified. I've opened a PR to make this change: https://github.com/canonical/snapd/pull/16127 I have another PR to batch adding rule notices so they're only written to disk once at the end: https://github.com/canonical/snapd/pull/16128 This work is tracked internally by https://warthogs.atlassian.net/browse/SNAPDENG-35748 -- 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/ubuntu/+source/snapd/+bug/2127189/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
