Fri, Aug 4
I'm going to call this closed because I see the same behavior on the previous build. (testbuild2)
I also tried Xorg vs. Wayland. The issue is not reproducible under Xorg, only under Wayland.
Wed, Aug 2
Jul 18 2017
Jul 15 2017
Okay! Thank you. I didn't know that there was a new version out already!
Jul 14 2017
This was fixed earlier today on b48694639af. There are new builds on builder.blender.org with this fixed.
Jul 13 2017
It's like this in previous versions too.
Jul 11 2017
Jul 9 2017
That's strange. I swear I have a reflection plane right by the front of the building, right by the trees. I tried to point it out in this one as the plane is a bit hidden. I also have it selected so that it can be more easily found.
Jul 7 2017
This should have been fixed on: 6eea22b2b7027658813d841391b36c7e50b3f54c, so closing for now.
That said I think you send the wrong sample. I couldn't find a single probe in the .blend file, so I couldn't reproduce the issue.
Jul 4 2017
We do not have to "support" Wayland afaik, this is low level compositor API that is hidden to most applications behind higher level APIs…
Jun 25 2017
Jun 6 2017
May 28 2017
If Blender works properly with Window Draw Method set to Full, then this is not a bug. That is simply the setting that plays nicely with your particular graphics card + driver.
Apr 22 2017
Arch have now fixed this. pacman -Syy blender to reinstall.
Apr 21 2017
Apr 20 2017
I've filed a bug on Archlinux for this, but as this page is currently the top search result for the error I'm posting here to let other Arch folks know that using makepkg to compile with the official PKGBUILD works as a workaround.
Apr 19 2017
Apr 6 2017
Mar 30 2017
Mar 28 2017
Can confirm with 32bit builds on my laptop.
Mar 26 2017
Operator requires an execution override to work properly:
When called from the Dynamic Context Menu (spacebar), it works just fine
Mar 19 2017
Yes, that's exactly what I said --
Mar 18 2017
@Ian Bruce (ian_bruce), i'm not sure what we can do with that knowledge. We are not drivers developers and are not involved into any distro development process. Guess this info better be directed to distro maintainers to ensure they ship proper drivers for OpenCL support (Blender is not the only program on planet which will benefit from that ;)
It turns out that these compiler warnings --
Mar 13 2017
The two separate compiler errors involved here (neither is actually a Blender issue) are now the subject of two Debian bug reports. Patches are available upstream for both problems, as mentioned above.
It turns out that the "invalid argument type 'X *' to unary expression" compile errors are the result of a known bug in LLVM. It is said to be fixed in LLVM-v5; see here:
I've applied the patch at rB8794a43 just because i prefer explicit NULL comparisons my self.
This same problem (actually, several problems) has been reported here; it's not distribution- or hardware-specific:
Mar 6 2017
Can confirm, this is a quite specific issue though, windowing is a bit complex so i don't know if this will be a trivial fix.
Feb 9 2017
I am also experiencing a similar error with my R9 280X running opencl-mesa 13.0.4-1 and ocl-icd 2.2.10-1 on Arch Linux x86_64 4.9.8-1 (Blender version 2.78.a).
Feb 2 2017
Thanks for the report, but we do not maintain any of the builds apart from the ones you can get from blender.org sites.