Update Runtime to 22.08, Blender to 3.4 and enable Wayland

[Pixelnarium]

Blender 3.4 is out and officially supports Wayland. For GNOME this requires libdecor to have a titlebar since GNOME does not support server side decoration. See https://code.blender.org/2022/10/wayland-support-on-linux/ for more details.

I also updated the runtime to 22.08 to have more up-to-date Mesa drivers.

It is "works for me" in Sway and GNOME.

fixes https://github.com/flathub/org.blender.Blender/issues/125

[flathubbot]

Started test build 10259

[flathubbot]

Build 10259 successful To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/122710/org.blender.Blender.flatpakref

[flathubbot]

Started test build 10260

[flathubbot]

Build 10260 successful To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/122711/org.blender.Blender.flatpakref

[Etaash-mathamsetty]

this is working for me as well on kde

[Beryesa]

Fine for me on Gnome Wayland with AMD card rendering the interface (nvidia can still render), But doesn't work yet on Nvidia card as the blog stated, Xwayland is still the way for Nvidia-only systems. Maybe block the Wayland permission temporarily by default until it's fixed and ones who want can enable themselves? You know what, the majority of Nvidia-only users don't use wayland anyway, ones do can toggle it off.

Edit: Also tested on sway!

[orowith2os]

Blender seems to work nicely over here, AMD.

Though, since I'm on GNOME, the CSD chosen by libdecor might seem a bit out of place; is it possible to bundle GTK with Blender, too, to use the GTK plugin, or does some more work need to be done on that front (namely, a new release for libdecor containing the plugin)?

[Pixelnarium]

As far as I can see the GTK plugin is not part of any stable libdecor version yet. I think it would be also possible to disable Wayland as a default to please GNOME and NVidia users and let everyone else just enable Wayland manually. It is just a matter of standard flatpak settings. It could be changed once libdecor gets a new stable release with the GTK plugin?

[orowith2os]

Yeah, the GTK plugin is still in -git.

But, as for GNOME and NVIDIA+Wayland users, it's not really an issue, imo. It would push for NVIDIA to fix their drivers, most NVIDIA users default to X anyways, and the CSD provided by libdecor isn't a big deal.

Edit: libdecor should be handled by the shared module if it gets accepted, so no issue.

[Pixelnarium]

Personally I am fine whatever the maintainer of this package wants since everyone can change the X11/Wayland settings via FlatSeal or CLI. :)

[orowith2os]

Libdecor was merged into shared-modules, could you look into updating the commit here and use that rather than bundling everything manually?

[flathubbot]

Started test build 10564

[flathubbot]

Build 10564 successful To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/123016/org.blender.Blender.flatpakref

[orowith2os]

@kevinsmia1939 could you please take a look at this? It seems to just work for everybody (save for NVIDIA users on Wayland, but that's a given).

[peterdk]

Works for me on Nvidia non wayland Ubuntu 22.10

[Mershl]

every startup places the window in the bottom right of the screen, with half of the window cut off. dragging it by the title bar after startup maximizes it and then minimizes it. The title bar also seems kinda strange. Is this expected? (Gnome 43.2 wayland)

[orowith2os]

@Mershl Blender having the new title bar is expected for now. Hopefully, soon, it'll be a GTK one, similar to what it was before.

Though it starting at the bottom of the screen is weird. AFAIK it should start in the center of the screen.

[Mershl]

Though it starting at the bottom of the screen is weird. AFAIK it should start in the center of the screen.

Tested this on a few machines (though all running Gnome 43 on wayland). The symptom is reproducible on all of them:

[orowith2os]

Interesting, I can reproduce it here as well; It starts at the bottom right corner of my primary monitor. I don't think it's a large issue, but definitely something that should be checked out.

[Pixelnarium]

For me it starts maxed / fullscreen on GNOME 43.2 with Wayland... strange.