-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
snap: AppArmor spam in dmesg #115
Comments
Is there a way to fix this? |
Yes, but it seems nobody cares |
fanquake
added a commit
to fanquake/bitcoin
that referenced
this issue
Oct 25, 2024
The data we try and gather in this file is on a best-effort basis, however in this instance, for certain users, it's just producing spam. This could (possibly?) be solved with further snap/apparmor configuration, however given that no-one is actively working on packaging, it seems easier to drop this (one of many), sources of dynamic environment data. Closes bitcoin-core/packaging#115.
fanquake
added a commit
to fanquake/bitcoin
that referenced
this issue
Oct 25, 2024
The data we try and gather in this file is on a best-effort basis, however in this instance, for certain users, it's just producing spam. This could (possibly?) be solved with further snap/apparmor configuration, however given that no-one is actively working on packaging, we could instead drop this (one of many), sources of dynamic environment data. Closes bitcoin-core/packaging#115.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Each minute:
probably because of /src/randomenv.cpp
The text was updated successfully, but these errors were encountered: