[13:23] <leitao> rtg, Hello. Regarding to #1546159, the patch is having a hard time to get upstreamed. 
[13:23] <leitao> Is it possible to keep it until we have a final solution?
[13:24] <apw> bug #1546159
[13:25] <apw> rtg, ^
[13:25] <rtg> leitao, I assume you are comfortable that it has been tested and works well ? I likely need to get kamal to look it over as well.
[15:12] <rtg> jsalisbury, I don't think bug #1576222 is a kernel problem
[15:19] <apw> rtg, right ... that isn't a kernel issue, that is a general distro issue
[15:20] <apw> rtg, move it to the ubuntu project with no package i recon
[15:20] <ogra_> until tzdata becomes a module ... just wait :P
[15:20] <apw> then someone else can figure out where it goes :)
[15:20] <rtg> apw, yeah, Jeff admitted as much - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576222/comments/4
[17:04] <jsalisbury> rtg, ack.  Still trying to get used to irc notifications in weechat
[17:05] <rtg> jsalisbury, it doesn't seem like you have any notifications :)
[17:05] <jsalisbury> rtg, crap, did  I miss a message from you earlier?
[17:06] <rtg> jsalisbury, just the one about a bug not being a kernel problem.
[17:07] <jsalisbury> rtg, ack, I just saw that.  I'll try to get it figured out.
[17:08] <apw> jsalisbury, the highlight thing is pretty odd looking at first
[17:08] <apw> jsalisbury, the keybinding alt-A takes you to a buffer that is asking for attention
[17:09] <apw> jsalisbury, and alt-P in that buffer will take you to a highlight in your name
[17:09] <jsalisbury> apw, yeah, I'm used to it being a big red backgrounded line.
[17:09] <apw> jsalisbury, does it make your nick yellow ?
[17:09] <apw> mine does that
[17:09] <apw> i mean my nick yellow when i highlight you ... jsalisbury 
[17:09] <jsalisbury> No.  It makes your's yellow with a purple background.
[17:09] <apw> ok thats what mine does
[17:10] <jsalisbury> apw, I just started using it today, so getting used to it still.
[17:10] <apw> and do you get the gobbledgook next to the buffer name to tell you which buffers want you ?
[17:10] <apw> alt-A shows the buffers in that order
[17:10] <apw> also you can change the criteria on a per-channel basis
[17:10] <apw> so i ahve like this one and the stable one appear on the active list every time there is any message
[17:11] <jsalisbury> apw, hmm not when I'm on the current buffer that needs my attention.  THe current buffer is highlighted red
[17:12] <apw> right if you are on the buffer its not going to add it to your list
[17:12] <apw> because it is showing
[17:12] <jsalisbury> apw, gotcha.  
[17:12] <apw> then you cna hit alt-P to see it
[17:12] <jsalisbury> apw, there are so many cool options to play with :-)
[17:13] <apw> jsalisbury, so like in your weechat buffers (normally /b 1) you can use: /set weechat.notify.irc.freenode.#ubuntu-kernel message
[17:13] <apw> to tell it that a channel is internesting when anything is said, rather than just your name
[17:15] <jsalisbury> apw, ahh, nice
[17:15] <jsalisbury> apw, I really like the split screen options too
[17:15] <apw> yeha they are good, and alt-X spins you round them
[22:10] <DalekSec> apw: Did you happen to see my ping about postinst/preinst scripts?
[22:12] <apw> DalekSec: no, missed it i assume ...
[22:15] <DalekSec> apw: I had noticed Debian updated their scripts a bit, rely more on triggers and seems to be some nice fixes there, fwiw.
[22:16] <apw> ahhh, that is on my list somewhere to investigate
[22:16] <DalekSec> \o/
[22:17] <DalekSec> I had also pinged you about a newer cryptsetup, basically merged it and updated to latest upstream if you wanted to review (better support for newer kernals, iirc) but let it go because too close to FF.
[22:52] <esanchma> I updated a Sony Vaio laptop from willy to xenial and now suspend hangs. resume-trace points to memory48. It seems to be a known regression for 4.4.0-21  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125) so, does the 4.4.0-22 kernel in xenial-proposed solve that? 
[22:57] <esanchma> 4.5.2 is known to work and it affects a ton of people.