> Many bugs reported to the Ubuntu bug database include dmesg, or filtered > dmesg, and it has proven very useful in determining to what extent > incorrect AppArmor policies can be blamed for specific problems, and > more importantly, what the solution may be. (It's also been very useful > for discovering which problems are likely hardware issues, e.g. due to > failing hard drives.)
please let's not diverge the topic of this report, and if you feel dmesg should be included in *each and every report*, then please bring that discussion on debian-devel for broader audience. > Including, or offering to include, some AppArmor log messages may be a > nice extension of this feature request. I think that poses some privacy concerns and that would have to be included in each report (of a system when apparmor is running) bloating them for little gain if the bug is not apparmor-related, so I want just to include a small not of a LSM running and what it is. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
