In T53004#465803, @TravLR (TravLR) wrote:

(1) Using fly-mode in viewport (Shift+f) causes the camera to move drastically and sporadically when the mouse reaches the edge of the Viewport and wraps around it.

Back in April 20th, I reported a bug to the Wayland team regarding this issue (as instructed by the Ubuntu Google+ community -- long-time Ubuntu user). After the news of the switch to GNOME & Wayland session by default in their newest upcoming release and beyond, I immediately began testing Blender in the Ubuntu 17.10 default session. There were three major issues which made Blender rather unusable in many circumstances (See the bug I posted in Wayland bugtracker: https://bugs.freedesktop.org/show_bug.cgi?id=100740). The three issues are:

There's no un-merged patches on our side.

Well, that's exactly what I wrote.

Hi, original purpose of Blender was to produce images from 3D scene.
Historically, there was an audio sequencer decoupled from video sequencer. They were merged by 2.5 re-design.
If you take attention to Edit Strip panel in Metastrip properties, you can see that they are based on Scene, Movie, Image strips properties with a blend mode dedicated to image blending.

The back trace in report indicates crash somewhere inside of Mesa/LLVM. We can not fix that or patch from Blender side, the driver itself is to be brought to a state when it can handle complexity of Cycles kernels.

I understand this is not a Blender issue, however six months after the various bugs were filed, Blender 2.79 still crashes on compilation under Ubuntu 17.10 Beta 2 with LLVM 5.0 and Mesa 17.2.2, even though it appears to me that all reported bugs were fixed.

Long time blender cloud subscriber is quite disappointed by this resolution. ;)

For workable experience you can simply disable "Continuous Grab" in User Preferences -> Input on a systems which are running Wayland.

I agree that this is not really a Blender bug. This is rather a limitation of how much of X11's behavior we can emulate without turning X11 into too much of a a backdoor into a Wayland based desktop environment. For example, we can of course not make it possible to allow X11 clients to became global key loggers, and in the same way, we cannot just make it possible to allow X11 clients to completely take over your mouse cursor.

I do not see any issues in the continuous grab implementation in Blender, and fact that none of X11 servers showed the issue in the past decades backs up theory that we don't abuse anything.

Very sad to see this resolution without any further consideration. FWIW, Xwayland is an X11 server on its own, so clearly not all X11 servers work fine. Furthermore, it's becoming the de-facto X11 server as many distros are switching to Wayland sessions by default. Blender will look broken on all of them.

Thanks for the report, but this isn't a Blender bug, all the X11 servers are working fine. The issue is in Waylan'd emulation of X11 protocol, which we can not fix from our side.

@Javier Herrero (jubjub) Blender isn't aware of wayland, closing since this is a bug in xwayland.

I'm having the same issue with flickering under Wayland, regardless of the draw method used, although full does help a little bit, I also get black flickering of the 3d viewport when circle selecting vertices on wireframe view.
I've verified that this only happens under Wayland, the exact same setup, same drivers and kernel under X11 works just fine.
I'm using a RX 560 with the amdgpu drivers, kernel 4.13, although I tried 4.9 and 4.12 as well.

Just would like to add that I'm experiencing this issue under Wayland as well.
There's a discussion on the Wayland mailing list about this issue, which seems to be related to Blender's use of xwayland (perhaps through SDL? I'm not sure). https://bugs.freedesktop.org/show_bug.cgi?id=100740

@Bastien Montagne (mont29) we have a few reports about blender + wayland, AFAICS these are bugs in wayland/X11, we can't really resolve.

@Campbell Barton (campbellbarton), you tend to be on the cutting edge with arch, maybe you do use Wayland and can check that? ;)

You are right. With OpenGL installed, the problem does indeed not occur. That is the configuration I had earlier.

You could try installing the OpenGL libraries anyway, even if you don't actually configure the device to be used for display in X11, since this error could be related to them being missing. For viewport rendering we try to initialize the device with an OpenGL interoperability for faster viewport display, and if that fails initialize without, but it seems somehow things permanently break there.

Okay! I will check and let you know if it starts running faster!

Thank you for the report, but 2.8 is currently under heavy development, and we are not taking bugs from end users yet.
Keep watching for updates at https://builder.blender.org/download/ to see if your issue got resolved.

Thank you for the report, but 2.8 is currently under heavy development, and we are not taking bugs from end users yet.
Keep watching for updates at https://builder.blender.org/download/ to see if your issue got resolved.

Thank you for the report, but 2.8 is currently under heavy development, and we are not taking bugs from end users yet.
Keep watching for updates at https://builder.blender.org/download/ to see if your issue got resolved.

Thank you for the report, but 2.8 is currently under heavy development, and we are not taking bugs from end users yet.
Keep watching for updates at https://builder.blender.org/download/ to see if your issue got resolved.

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.

Okay! Thank you. I didn't know that there was a new version out already!

This was fixed earlier today on b48694639af. There are new builds on builder.blender.org with this fixed.

It's like this in previous versions too.

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.