| lamont` | jsalisbury: updated 1543683 with a zomfg what have they done comment | 00:47 |
|---|---|---|
| lamont` | because, no, randomly shoving all my windows around just because I locked the screen is not acceptable at all | 00:47 |
| * lamont` will be downgrading again | 00:48 | |
| === lamont` is now known as lamont | ||
| === dax is now known as daxcat | ||
| === mamarley_ is now known as mamarley | ||
| === _ruben_ is now known as _ruben | ||
| marlinc | Test | 13:27 |
| apw | marlinc, works | 13:27 |
| lamont | jsalisbury: I hate your kernel | 14:37 |
| * lamont downgrades so that X doesn't decide to randomly move windows around everytime he locks the screen. Or at least to confirm that it's because of the kernel | 14:38 | |
| apw | lamont, the kernel moves your windows, that seems unexpected, especially on a lock of the screen | 14:40 |
| apw | its not like the kernle has any concept of windows at all | 14:40 |
| apw | so it'd have to turning an output off or something on lock | 14:40 |
| lamont | apw: I believe it's deciding that I'm single-headed | 14:42 |
| lamont | OTOH, I propose to test that theory momentarily | 14:42 |
| apw | lamont, does the external display turn actually off when you hit lock | 14:42 |
| apw | that seems wrong to me, you could try xset dpms force on or something | 14:42 |
| lamont | apw: the bug in question relates to the second display being not detected, and a patch to make it maybe work better | 14:43 |
| lamont | and yeah, with 4.4.0-6.21~lp1543683Commit237ed86cReverted, the windows stay on the correct displays. | 14:45 |
| lamont | apw: I'll make some time later today to test that theory better. | 14:45 |
| lamont | jsalisbury: can I also get a 4.4.0-9.24~lp1543683Commit8d409cb minus the cherrypick and 237ed86c reverted to confirm it's truly just the display patches? | 14:46 |
| apw | lamont, there is um HEAP of change on the -12 in DRM so it is also worth testing that if you have a window | 14:47 |
| apw | especially if you have broadwell or later | 14:47 |
| lamont | this is i915 | 14:47 |
| apw | right, but what serie,s i have i915 broadwell which is meant to be better with -12 | 14:48 |
| apw | not that i have it yet :) | 14:48 |
| lamont | where would I see that? | 14:48 |
| lamont | 00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) | 14:48 |
| apw | erm :) | 14:48 |
| apw | 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) | 14:49 |
| apw | ok apparently you have something else | 14:49 |
| lamont | agreed | 14:49 |
| jsalisbury | lamont, I'll review the latest updates to the bug | 15:05 |
| jsalisbury | lamont, and I'll build the kernel you asked for in the scroll back | 15:08 |
| lamont | jsalisbury: woot | 15:09 |
| lamont | known is 4.4.0-6-reverted: windows stay on the right display. 4.4.0-9-patched: windows migrate on lock | 15:10 |
| lamont | I'd like to isolate that better | 15:10 |
| jsalisbury | lamont, ack | 15:11 |
| === daxcat is now known as ezri | ||
| === ezri is now known as daxcat | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!