=== tmpRAOF is now known as RAOF
=== tmpRAOF is now known as RAOF
[03:28] <furkan> tjaalton: confirmed that it's not a radeon bug... same issue with fglrx, and the checkerboarding doesn't happen in kubuntu
[03:29] <furkan> i posted another comment on the bug report again a few hours ago, saying that i had tested it in kubuntu
[03:30] <furkan> so it's probably not Xorg (since it doesn't happen on KDE), and almost definitely not the open-source radeon driver (since i don't think it shares any code with fglrx), so i think that probably leaves Unity/compiz
[03:31] <furkan> tjaalton: when you get the opportunity, would you mind testing again with both screens not aligned at the top, i.e. with y > 0 for the landscape monitor
[03:33] <furkan> but how could it be unity/compiz... because it first started happening when i upgraded to xserver-xorg-lts-vivid from the x staging ppa when i was running trusty
[03:33] <furkan> so then maybe it *is* an xorg bug
[03:35] <furkan> well at least i have dpms back, after switching to fglrx
[03:40] <furkan> (but i did lose my virtual terminals)
[03:40] <furkan> with an AMD card on linux i guess there's no winning combination
[04:36] <tjaalton> kde uses qt, not gtk
[04:37] <tjaalton> and use xterm or such ;)
[07:37] <ricotz> tseliot, jfyi pushing blob 346.59 tarballs to xorg-edgers
[07:37] <tseliot> ricotz: ok, I'll use your tarballs then
[07:37] <tseliot> so that you don't have to re-upload them
[07:37] <ricotz> tseliot, thanks, i hope it didnt already clash with your work
[07:38] <tseliot> ricotz: no problem, I'll delete mine and download yours. I'm still testing the packages
=== soee_ is now known as soee
=== soee_ is now known as soee
[20:50] <tjaalton> furkan: you'll get your dpms back in the next vivid kernel update
[20:50] <tjaalton> oh it got tagged, 3.19.0-13.13
[21:37] <furkan> tjaalton: ah, great news, thanks :D
[21:38] <furkan> i hope it continues to work after suspend/resume as well!
[21:39] <furkan> and.. i've been playing around with kde (i installed the kubuntu-desktop package)
[21:39] <furkan> i'm finding it really strange that kde doesn't crash after changing my display settings, but unity does
[21:40] <furkan> the display corruption happens in both, but kde recovers whereas unity doesn't
[21:40] <furkan> and the totally crazy thing about the display corruption is that it shows parts of the screen buffer from the previous boot
[21:41] <furkan> like first when i booted up into a kubuntu live usb, and changed the monitor configuration, when it was switching resolutions you could see portions of what i had open on my screen before rebooting
[21:42] <furkan> and likewise when i rebooted back into my ubuntu install, when changing resolutions i would see portions of the wallpaper from the kubuntu live cd
[21:42] <furkan> if it's on a fresh boot, i see white rectangles instead
[21:43] <furkan> so it's as if there are portions of old stuff that's left over in the VRAM
[21:44] <furkan> so if you shut down the PC, it gets cleared, but if you do a reboot, those contents are still in the VRAM and they get "leaked"
[21:44] <furkan> i'm sure that's an upstream issue, as it doesn't happen with fglrx
[21:45] <furkan> but somehow kde manages to handle the situation anyway
[21:46] <furkan> so that's why i installed kde, but i can't stand it, gonna nuke it now and go back to unity
[22:31] <furkan> tjaalton: i just added the kernel testing ppa and installed 3.19.0-13, and also did an apt-get upgrade and noticed that my libdrm* packages got upgraded... now dpms is back (even after suspend/resume) and my desktop no longer crashes after a resolution change... so i will close that bug
[22:32] <furkan> i still get the checkerboard corruption after suspend/resume... but, not the worst out of those bugs
[22:43] <furkan> tjaalton: never mind... resolution change causes a black screen (it used to show corruption, now just black) - it was only changing the screen's vertical position which no longer triggered screen corruption + crash