[09:04] <tjaalton> RAOF: hi, my unity8 session still just shows a blank screen, so can't test my mir egl patch refresh on new mesa.. any ideas how to get it work?
[09:05] <tjaalton> jcastro: yeah, it doesn't need much actually. with some packaging changes it can use older llvm and libclc, but backporting those too isn't hard
[09:05] <tjaalton> jcastro: and then there's libdrm of course
[09:05] <tjaalton> jcastro: 16.10 has all that's needed though, backports needed only for 1604
[11:33] <tseliot> mamarley: hi. Today I am going to fix up the nvidia drivers in zesty so that they build with the new kernel.
[11:34] <mamarley> tseliot: Cool, thanks!  I already have 367 and 370 patched in the graphics-drivers PPA if you want to use those, and 375 doesn't need a patch.
[11:34] <tseliot> mamarley: great, I'll have a look at those patches :)
[11:34] <tseliot> and focus on 340
[11:34] <mamarley> They are both exactly the same :)
[11:34] <tseliot> good
[14:13] <tseliot> mamarley: can you point me to the error you faced with 304, please? It might save some time
[14:14] <mamarley> One sec…
[14:15] <mamarley> tseliot: It is the same issue experienced by "ejmarkow" in https://devtalk.nvidia.com/default/topic/973807/linux/nvidia-linux-x86_64-340-98-driver-not-building-with-kernel-4-9-0-rc2-/ .
[14:16] <tseliot> mamarley: ok, thanks
[14:17] <ricotz> 304 or 340
[14:18] <mamarley> ricotz: 340, though I haven't tested 304 so it may have the same problem too.
[14:19] <mamarley> It looked like it might be trying to initialize the driver twice so I checked to see why that might be happening, but I don't know enough about kernel module programming so I couldn't figure anything out.
[16:57] <mamarley> I have found that the Mesa 13.0.1 from the xorg-edgers PPA fixes the resource leaks and subsequent lagging caused by animated tray icons in KDE Plasma 5 while using the modesetting driver and Glamor.  This is nice, now I don't have to restart Plasma a bunch anymore!