=== _unixpro1970 is now known as unixpro1970 === unixpro1970 is now known as _unixpro1970 === _unixpro1970 is now known as unixpro1970 === unixpro1970 is now known as _unixpro1970 === _unixpro1970 is now known as unixpro1970 === unixpro1970 is now known as _unixpro1970 === _unixpro1970 is now known as unixpro1970 === ghostcube_ is now known as ghostcube [13:23] rtg, Hello. Regarding to #1546159, the patch is having a hard time to get upstreamed. [13:23] Is it possible to keep it until we have a final solution? [13:24] bug #1546159 [13:25] bug 1546159 in linux (Ubuntu Xenial) "ISST-LTE: high cpus number need a high crashkernel value in kdump" [High,In progress] https://launchpad.net/bugs/1546159 [13:25] rtg, ^ [13:25] 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. === ghostcube_ is now known as ghostcube [15:12] jsalisbury, I don't think bug #1576222 is a kernel problem [15:12] bug 1576222 in linux (Ubuntu) "Clock does not update TZ based on location" [Medium,Confirmed] https://launchpad.net/bugs/1576222 [15:19] rtg, right ... that isn't a kernel issue, that is a general distro issue [15:20] rtg, move it to the ubuntu project with no package i recon [15:20] until tzdata becomes a module ... just wait :P [15:20] then someone else can figure out where it goes :) [15:20] apw, yeah, Jeff admitted as much - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576222/comments/4 [15:20] Ubuntu bug 1576222 in linux (Ubuntu) "Clock does not update TZ based on location" [Medium,Confirmed] [17:04] rtg, ack. Still trying to get used to irc notifications in weechat [17:05] jsalisbury, it doesn't seem like you have any notifications :) [17:05] rtg, crap, did I miss a message from you earlier? [17:06] jsalisbury, just the one about a bug not being a kernel problem. [17:07] rtg, ack, I just saw that. I'll try to get it figured out. [17:08] jsalisbury, the highlight thing is pretty odd looking at first [17:08] jsalisbury, the keybinding alt-A takes you to a buffer that is asking for attention [17:09] jsalisbury, and alt-P in that buffer will take you to a highlight in your name [17:09] apw, yeah, I'm used to it being a big red backgrounded line. [17:09] jsalisbury, does it make your nick yellow ? [17:09] mine does that [17:09] i mean my nick yellow when i highlight you ... jsalisbury [17:09] No. It makes your's yellow with a purple background. [17:09] ok thats what mine does [17:10] apw, I just started using it today, so getting used to it still. [17:10] and do you get the gobbledgook next to the buffer name to tell you which buffers want you ? [17:10] alt-A shows the buffers in that order [17:10] also you can change the criteria on a per-channel basis [17:10] so i ahve like this one and the stable one appear on the active list every time there is any message [17:11] apw, hmm not when I'm on the current buffer that needs my attention. THe current buffer is highlighted red [17:12] right if you are on the buffer its not going to add it to your list [17:12] because it is showing [17:12] apw, gotcha. [17:12] then you cna hit alt-P to see it [17:12] apw, there are so many cool options to play with :-) [17:13] jsalisbury, so like in your weechat buffers (normally /b 1) you can use: /set weechat.notify.irc.freenode.#ubuntu-kernel message [17:13] to tell it that a channel is internesting when anything is said, rather than just your name [17:15] apw, ahh, nice [17:15] apw, I really like the split screen options too [17:15] yeha they are good, and alt-X spins you round them === ghostcube_ is now known as ghostcube [22:10] apw: Did you happen to see my ping about postinst/preinst scripts? [22:12] DalekSec: no, missed it i assume ... [22:15] 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] ahhh, that is on my list somewhere to investigate [22:16] \o/ [22:17] 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] 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:52] Ubuntu bug 1566302 in linux (Ubuntu) "duplicate for #1574125 Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16" [Medium,Incomplete] [22:57] 4.5.2 is known to work and it affects a ton of people.