=== _leftyfb is now known as leftyfb === beisner- is now known as beisner === ogasawara is now known as Guest30473 === mukhbiir is now known as neoark [10:11] infinity, Holy grep it's crap! I mean the other way round (my build failures of Xen seem to be caused by grep in the sbuild environment deciding in the middle of a file to switch from text to binary mode) [10:51] smb, in the middle of a file ? [10:52] apw, yep [10:52] well not middle but after around 43 lines [10:57] smb, could you just switch to grep --text, or something [10:57] apw, as a work around, yes [10:57] oh its "text" is it, like utf8 or something, sigh [13:18] rtg: hey, curious, looking at the 4.4.0-7.22 changelog, I see 'rebase to v4.4.2' and 'Miscellaneous upstream changes'. does the latter include all of the changes that went into 4.4.2 over 4.4.1? [13:19] rtg: talking about the upstream changes [13:19] I've got an external displayport issue that I've been meaning to report that downgrading to 4.3 fixes [13:20] so I keep looking at 4.4 kernel changes. I don' [13:20] t see anything related to this, so curious if the list of upstream changes is complete [13:20] (it is something I've always wondered about) [13:21] jdstrand, The patches included in v4.4.2 are not listed in the changelog. That seems like an oversight. [13:21] is that what you are asking ? [13:22] I was asking about all the upstream changes whenever you rebase, in this base, 4.4.1 to 4.4.2, but more just generally [13:22] s/this base/this case/ [13:23] jdstrand, during the dev cycle the changes introduced by a rebase are not listed, though they are easy ebough to find (if you know what you're doing) [13:23] or more simply, can I rely on Ubuntu's changelog to list all changes from one release to the next, upstream and Ubuntu, or just the Ubuntu changes [13:23] ok, that's fine [13:23] I imagine the changelog would be rather long [13:24] jdstrand, post dev, all commits are applied on top (modulo CVE rebases) [13:24] so they'll all get listed in the changelog [13:24] cool, thanks [13:25] all that is going through my mind is "So your saying there's hope" :) [13:26] jdstrand, for a display issue ? don't get too wound up :) [13:26] jdstrand, if you have a bisectable range, then you could work with jsalisbury [13:27] * jdstrand nods [13:27] I wanted to try the next one from you guys before reporting [13:27] I can say for sure that wily's kernel doesn't have this bug [13:28] jdstrand, that bodes well for bisectability [13:28] I was then going to (re)try the earliest 4.4 kernel in the archive, then report [13:28] jsalisbury is a wizard [13:28] yeah [13:29] jdstrand, plus, I'm about to be on vacation :) [13:29] this bug is rather annoying-- the screen just goes blank for 1 second or 2, then comes back, at totally random times, but only on the external monitor [13:29] never seen anything quite like it [13:29] rtg: nice! enjoy :) [13:29] jdstrand, Intel I assume ? [13:30] yes [13:31] it seems like the it goes blank at all the wrong times too. almost like its sentient [13:31] jdstrand, I've got Intel on my laptop connected to HDMI 4K monitor. its got some quirks but overall seems to work OK [13:31] I may have not gotten inough sleep last night :P [13:31] rtg: yeah, this is displayport (mini) 4K [13:31] has it started to talk to you ? maybe you _shoud_ sleep. [13:32] should* [13:32] rtg: like you said, some quirks, mostly ok. The biggest quirk is hotplugging the monitor [13:32] (other than this bug) [13:33] jdstrand, I have to turn mine completely off once in awhile after resume from suspend. that is about the worst of the quirks [13:33] but a dialog comes up that says it couldn't xrandr or something (and the display is all stretched out), but if I tap 'Enter' to dismiss the dialog, it rights itself [13:33] rtg: yes, I used to see that more, but see it less often now [13:34] it does this whole dance when hotplugging-- the laptop and the display flash, the monitor goes blank, it comes back, it might do it again, etc [13:34] * jdstrand shrugs [13:34] I'll file a bug for that another day [13:35] jdstrand, slacker. I'm sure jsalisbury would love to have you test about a dozen kernels :) [13:35] hey, well, that never worked right so... [13:36] actually, the not being able to randr might've worked on wily... [13:36] anyhoo, another day. I want to get this odd blanking bug reported === bladernr_ is now known as bladernr === ogasawara is now known as Guest54574 [16:22] jsalisbury: good kernel! next rock? (bug updated) [16:31] lamont, I'll build it now [16:36] ta [18:19] jsalisbury (fyi, rtg and ogasawara_): the external monitor screen blinking bug is bug #1547619 [18:19] bug 1547619 in linux (Ubuntu) "Intermittent screen blinking with 4k external mini display port with 4.4 kernels" [Undecided,New] https://launchpad.net/bugs/1547619 [18:20] jdstrand, ok, thanks. we'll probably have to bisect it. Are you able to test some kernels? [18:22] jsalisbury: yes. will they be Ubuntu kernels? (ie, with apparmor compat, etc) [18:23] jdstrand, sure I can build Ubuntu kernels instead of upstream ones. I'll post an update to the bug. [18:23] jsalisbury: thanks! :) [18:28] jdstrand, Can you first test 4.4.0-1.15 to see if we can narrow the bisect window. I post a link to it in the bug. [18:35] jsalisbury: sure [18:35] jdstrand, thanks. Then I'll start the bisect and post a test kernel. [18:37] hmm, I do have secure boot enabled... I guess I'll need to fiddle with my configuration [18:37] oh now, it'll fallback [18:49] jsalisbury: fyi, I'm in 4.4.0-1.15-generic. it hasn't happened yet, but that doesn't mean anything. I'll report back in the bug [19:01] jdstrand, thanks [19:12] jsalisbury: hah [19:12] jsalisbury: the *moment* I started to do real work in a terminal, it happened [19:13] I swear this thing is here to annoy the *&%^ out of me [19:13] jdstrand, thanks for testing. I'll start the bisect with that being the first bad kernel [19:14] jsalisbury: thank you for helping resolve this. I can't tell you how annoying this bug is [19:15] jdstrand, np. [19:15] I mean it isn't data loss or anything, but it really takes you out of the moment [19:15] jdstrand, I'm sure it does === ogasawara is now known as Guest15552