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.

Arch have now fixed this. pacman -Syy blender to reinstall.

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.

Can confirm with 32bit builds on my laptop.

Operator requires an execution override to work properly:

When called from the Dynamic Context Menu (spacebar), it works just fine

Yes, that's exactly what I said --

@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 --

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:

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.

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).

In T50522#413817, @Sergey Sharybin (sergey) wrote:

Thanks for the report, but we simply don't officially support MESA OpenCL implementation yet.

Thanks for the report, but we do not maintain any of the builds apart from the ones you can get from blender.org sites.

Thanks for the report, but we simply don't officially support MESA OpenCL implementation yet.

Thanks, I checked it with the latest builds and it works.

Fix is commited, please check the buildbot soon to check if it solved your case.

Thanks in advance for fixing it.

Though netrender is currently unmaintained and removed for 2.8, this seems to be a simple fix.

Think so. Please correct me if i'm wrong :)

@Sergey Sharybin (sergey), so seems this patch can be closed?

In new bild the problem fixed

This is supposed to be fixed in current master, please check again.

This is an issue with .deb package provided by your distro, which we do not maintain in any sense.

Please do not assign bugs to random users.

Compiled from Master, it is working well now!

So, looks like it was indeed blender reading badly those valuators stuff in the end - at least not the same as xinput --test code does it. ;)

Hi.
I opened a report bugs.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=95459

Yeah, I know missing coordinates is perfectly valid, the problem is not there. The problem is that, when only Y coordinate change, the event reports two available valuators, starting from valuator 1 (that is, it reports Y data and pressure data, even though there is no pressure data and valuator is set to zero).

Hello.
I have contacted Nikolai Kondrashov, DIGImend founder and main developer. I shared with him the next file showing Evtest, Xinput and Blender output while drawing on Blender: