[00:00] <furkan> but on 3.19.0-12 it doesn't work at all
[00:00] <furkan> so, still a difference
[14:31] <tjaalton> furkan: can't reproduce the checkerboarding bug or the corruption. the dpms issue is real, testing a commit now
[17:17] <furkan> tjaalton: this is interesting... i unplugged my secondary monitor, and everything works much, much better
[17:18] <tjaalton> is the other monitor a 4k one?
[17:19] <furkan> no checkerboarding, no "snow" in the virtual terminal, no delay when switching between virtual terminals (with 2 monitors, it takes a few seconds), and no graphics corruption when initially logging in (i didn't mention that in the bug report because i thought that was "normal", i'll take a vid for you if you want)
[17:19] <furkan> i have just my 27" 2560x1440 monitor connected now
[17:20] <tjaalton> and the other one?
[17:20] <furkan> i unplugged it.. i'll plug it in and try it in landscape mode first
[17:20] <furkan> before switching to portrait, which is how i originally had it
[17:20] <tjaalton> the resolution?
[17:20] <furkan> oh right
[17:20]  * furkan tests
[17:24] <tjaalton> tried rotating the other one, still nothing
[17:24] <furkan> nope... killed my desktop
[17:24] <furkan> i took a pic
[17:24] <furkan> https://www.dropbox.com/s/fd1tdi67og8iz91/IMG_20150408_132316.jpg?dl=0
[17:24] <furkan> that's what happened when i tried to change from 2560x1440 to 1920x1080
[17:25] <furkan> so you have a dual-monitor setup too?
[17:25] <furkan> what are your resolutions?
[17:25] <tjaalton> 25x14, 19x10
[17:25] <furkan> oh, so almost the same
[17:26] <tjaalton> hooked to the same monitor via dvi & hdmi
[17:26] <furkan> and you tried rotating the 19x10 monitor?
[17:26] <tjaalton> yes
[17:26] <furkan> wait, hooked to the same monitor? you mean 1 screen connected with 2 cables?
[17:26] <tjaalton> yup
[17:26] <tjaalton> i only have one
[17:26] <furkan> hmm
[17:27] <furkan> ok i will try connecting it again in landscape
[17:33] <furkan> ok so i have the monitor in landscape now
[17:33] <furkan> switching between vts is no longer instantaneous
[17:33] <furkan> but no checkerboarding/snow
[17:33] <furkan> after suspend/resume
[17:34] <furkan> changing resolution still trips it up, i need to switch into a VT and service lightdm restart
[17:36] <furkan> so i made the switch to portrait, right now i have checkerboarding, but no "snow"
[17:37] <furkan> even after 2 suspend/resume cycles (1 when i had the monitor in landscape, and 1 after i switched to portrait)
[17:38] <furkan> i bet it'll be back after i restart though
[17:38] <tjaalton> so which one is in portrait?
[17:43] <furkan> yeah so i restarted, at first no snow, then suspend/resume and the snow is back... so it seems to reproduce that bug i need to boot directly into that display configuration
[17:43] <furkan> i have 27" 2560x1440 in landscape mode
[17:43] <furkan> and 24" 1920x1200 in portrait mode, on the left-hand side
[17:43] <furkan> i suppose i could also try putting it on the right-hand side as a final test
[17:44] <furkan> interesting, this time my screen didn't become garbled after changing resolution
[17:45] <furkan> and VT switches are instantaneous
[17:49] <furkan> ok well after restarting, no difference
[17:50] <furkan> but at that moment, just after switching the screen from one side to the other, i was getting instantaneous VT switches, now i'm not
[17:50] <furkan> but snow/checkerboarding still there
[17:50] <tjaalton> have you tried 4.0?
[17:51] <furkan> https://www.dropbox.com/s/4koy953b7faj095/VID_20150408_134129.mp4?dl=0
[17:51] <furkan> that's the corruption when initially logging in.. pretty minor so i hadn't thought much of it before, but it doesn't happen with a single monitor connected
[17:51] <furkan> and yeah i was using 4.0 for a while, and same issues
[17:52] <tjaalton> try #radeon then, and file a bug on bugs.freedesktop.org
[17:53] <furkan> but i didn't have the issue with Xorg 1.16, so what if it's an Xorg bug and not a kernel bug?
[17:53] <furkan> and when i downgrade to 3.16 i still have the issue
[17:53] <furkan> whereas before upgrading to 15.04, i didn't
[17:53] <furkan> so i think that rules out the kernel, no?
[17:53] <tjaalton> same devs
[17:53] <furkan> ah
[17:53] <tjaalton> pretty much
[17:54] <furkan> ok will do, then
[17:54] <furkan> thanks for the pointer
[17:56] <furkan> btw, another regression, unrelated to X: after rebooting or suspend/resume, i need to unplug my headphone and plug it back in for it to be recognized again
[17:57] <furkan> if i submit too many bug reports i feel like i'll become the "boy who cried wolf", but right about now i'm wishing that i stayed with 14.04 :P
[18:00] <tjaalton> well, can't reproduce that either, something wrong with jack detection I guess
[18:00] <tjaalton> file that against pulseaudio
[18:00] <tjaalton> for starters
[19:54] <furkan> tjaalton: i guess i understand the "snow" thing now
[19:55] <furkan> when on a VT, it sets the same resolution on both monitors
[19:55] <furkan> so since my smaller monitor is 1920x1200, it sets that resolution on both
[19:56] <furkan> and before suspending, it's scaled to full screen
[19:56] <furkan> after suspend/resume, you get the 1920x1200 terminal drawn on the top left corner of the screen, and the blank areas are white
[19:58] <furkan> in 4.0, the terminal isn't scaled to full screen but the blank areas are black (then after suspend/resume it turns white)
[20:02] <furkan> really not the worst out of the bugs i've seen so far, but something is really broken w/ dual monitor support on a radeon card
[20:19] <tjaalton> furkan: yep, saw the same, no corruption though, just white borders
[21:00] <furkan> tjaalton: i know this must be an upstream bug, but just to share the hilarity https://www.dropbox.com/s/caawhzn8zfycc00/VID_20150408_165520.mp4?dl=0
[21:01] <furkan> the time difference between switching, where the secondary monitor is on the left vs. the right
[21:01] <furkan> *switching to a VT
[21:03] <tjaalton> it is what it is.
[21:04] <furkan> well with the open-source drivers w/ kernel modesetting, it's supposed to be instantaneous
[21:04] <furkan> whereas with the proprietary drivers it's not
[21:04] <furkan> so while the bug itself is no big deal, i think it's indicative that something is going wrong
[22:37] <furkan> tjaalton: do you use vanilla Ubuntu, or one of the derivatives?