2

I'm using transmission-gtk 4.1.0-beta.2 on Devuan GNU/Linux Excalibur. My dmesg log is spammed with the following kind of message:

[Jul 4 14:47] audit: type=1400 audit(1751629628.491:75895): apparmor="ALLOWED" operation="open" class="file" profile="transmission-gtk" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=20126 comm="transmission-gt" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

(originally all in one line, I broke it here for readability.)

My network connection does have an IPv6 address (along with IPv4), even though I'm not intentionally making use of it. Anyway, I would like to have transmission-gtk stop trying to mess with it.

Is that possible? If not, can I at least silence the repeating log message? Or get to only show up just once?

FYI, on my system, I have:

# ls -la /proc/sys/net/ipv6/conf/all/disable_ipv6 -rw-r--r-- 1 root root 0 Jul 4 13:59 /proc/sys/net/ipv6/conf/all/disable_ipv6
Improve this question

1 Answer 1

Reset to default
5

To help your understanding what's happening: it's not transmission-gtk that generates these log messages – it's apparmor, the Linux security module that your devuan installation uses. Its job is to make sure programs that you run are only doing the things they should. If, say, your browser started to read your personal documents or to launch daemon processes, you would want to know and would want your system to intercept the attempt to do so. That's what apparmor was designed for. It has profiles for different applications, and when an application tries to act outside that profile, it just can't and things get logged.

In this case, it seems that transmission-gtk, for whatever reason the graphical frontend wants to do that, tries to open (for reading) /proc/…/disable_ipv6, which triggers the log entry. Interestingly, apparmor said it then was ALLOWED, which comes as a surprise. Did you perhaps experiment with apparmor and put it into a non-enforcing state? That would explain the repeated attempts, maybe. If that's the case, try setting apparmor back into its original enforcing state.

If you're sure you've never worked on your apparmor settings before, file a bug with devuan (not debian, this might very well be distro-specific).

If that doesn't help, you will need to generate your own apparmor profile, using aa-genprof transmission-gtk; the debian handbook on apparmor might be of help there.

Improve this answer
1
  • I did not experiment with apparmor. How do I put apparmor in the enforming state? Also, can I get transmission to not try to disable IPv6? Commented Sep 26 at 18:03

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.