blockbench icon indicating copy to clipboard operation
blockbench copied to clipboard

Blockbench 5.0.3 doesn't start on wayland with flatpak

Open swip3798 opened this issue 2 months ago • 3 comments

What are you trying to do, and what do you expect to happen?

I have block bench installed via Flatpak. I updated it to the latest version. I tried to start it but it closed after a few seconds. I tried starting it via flatpak run net.blockbench.Blockbench.

What happens instead?

The following error comes up when starting blockbench via the flatpak run command.

[3:1026/154723.579584:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:1026/154723.776782:ERROR:ui/ozone/platform/wayland/host/wayland_connection.cc:197] Failed to connect to Wayland display: No such file or directory (2)
[3:1026/154723.776806:ERROR:ui/ozone/platform/wayland/ozone_platform_wayland.cc:282] Failed to initialize Wayland platform
[3:1026/154723.776853:ERROR:ui/aura/env.cc:257] The platform failed to initialize.  Exiting.

I found that when I changed the flatpak permissions with Flatseal and added the socket=wayland permission, blockbench starts. The dbus error can be removed with adding the socket=system-bus permission.

Model format in which the issue occurs

Blockbench variant

Program

Blockbench version

5.0.3

Operating System

Linux / CachyOS

Installed Blockbench plugins

No response

Are there any console errors?

No response

swip3798 avatar Oct 26 '25 14:10 swip3798

Experiencing the same issue on Bazzite 43.

Thank you for the workarounds.

For me, it also helped to add permissions for:

--socket=wayland
--socket=fallback-x11
--socket=system-bus

krakua0 avatar Nov 06 '25 20:11 krakua0

oh it's doing something, using up 100% of my steam deck's gpu upon opening then quitting manually in system monitor. 5.0.4 had to force quit (kill).

OrdinaryCloverOC avatar Nov 12 '25 01:11 OrdinaryCloverOC

For me at least worked enabling the system-bus and disabling the fallback-x11, with wayland and x11 permissions is fine.

In journalctl just appears as a simple core dumped with the next description: Stack trace of thread 3: #0 0x0000564852c45cde n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64

System specs: OS: Fedora Linux 43 (Workstation Edition) x86_64 Host: 20H1A073LM (ThinkPad E470) Kernel: Linux 6.17.7-300.fc43.x86_64 DE: GNOME 49.1 WM: Mutter (Wayland) CPU: Intel(R) Core(TM) i3-7100U (4) @ 2.40 GHz GPU: Intel HD Graphics 620 @ 1.00 GHz [Integrated]

LBY-L avatar Nov 19 '25 03:11 LBY-L