[00:42] <pabelanger> Good evening, any advice on which IRC channel I would use to help triage a backport request?
[00:51] <trinikrono> pabelanger: this is the place
[00:51] <trinikrono> a idea would be to post the bug report itself though so other people can look at it
[00:51] <trinikrono> * a good
[01:03] <AddJim> Could someone triage this to kernel-team? Pretty sure this is where it needs to go https://bugs.launchpad.net/ubuntu/+source/linux/+bug/824304
[01:03] <AddJim> Unless it's considered okay for me to dole it out myself
[03:35] <hggdh> AddJim: there is no need to triage it, it is already on the kernel team's radar; also, we do not assign buhs to other people/teams
[03:36] <hggdh> AddJim: one place to go to try a response is #ubuntu-kernel (but this is weekend, so the response time may be, ah, lacking a bit
[03:38]  * hggdh goes AFK now
[03:41] <AddJim> Thank you hggdh =)
[03:53] <pabelanger> trinikrono: Thanks, I'll follow up in the morning
[20:46] <Cheesehead> Event: Wisconsin LoCo is running an IRC Bug Jam, Sunday 1700 UTC, #ubuntu-us-wi. Great training opportunity for people new to bugs.
[23:30]  * penguin42 wonders - are there bots that trawl dmesg's etc attached to logs for signs that the victims machine has some form of malware on?
[23:35] <jtaylor> why would malware write to logs that its there?
[23:35] <penguin42> jtaylor: Well they don't - but sometimes they end up causing particular symptoms
[23:36] <jtaylor> its bad malware then
[23:36] <jtaylor> which you can probably detect by other means
[23:37] <penguin42> well most malware is bad; but it's not unusual to trigger odd messages etc