[Bug]: Flathub release does not launch properly on PopOS, Intel CPU + Integrated Graphics #2776

Closed
opened 2026-02-28 20:27:31 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @cgifford99 on GitHub (Jan 6, 2026).

Originally assigned to: @MikesGlitch on GitHub.

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I was just testing out the new Flathub release and after successfully installing it through the PopOS Pop Shop, I seem to be unable to successfully launch the app. The app will start, but only an empty window appears with no content; only a frame and a blank background.

I found some errors in the systemd journal that may be of use to you that I've attached at the bottom. I have already tried to resolve the issue via the "failed to create dri3 screen", "failed to load driver: iris" errors, but was not successful with the common solutions (i.e. reinstalling Mesa drivers + associated packages).

System details:

  • OS: PopOS 22.04
  • Kernel: 6.17.4-76061704-generic
  • CPU: Intel i5-12600K
  • GPU: Mesa Intel UHD Graphics 770

Please let me know if you need any more info from me. I'd be happy to help.

systemd journal (expand to see log)

Jan 05 22:41:38 dev-machine systemd[3385]: Started Application launched by gnome-shell.
Jan 05 22:41:38 dev-machine systemd[3385]: Started app-flatpak-com.actualbudget.actual-8005.scope.
Jan 05 22:41:38 dev-machine systemd[3385]: Started app-flatpak-com.actualbudget.actual-8029.scope.
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.358218: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
Jan 05 22:41:38 dev-machine actual[8015]: Failed to load module "canberra-gtk-module"
Jan 05 22:41:38 dev-machine actual[8015]: Failed to load module "canberra-gtk-module"
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.492991: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
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.493028: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
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.534293: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
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.534357: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
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.534391: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
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8065]: MESA: error: Failed to query drm device.
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8065]: glx: failed to create dri3 screen
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8065]: failed to load driver: iris
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8065]: [43:0105/224138.565327:ERROR:components/viz/service/main/viz_main_impl.cc:189] Exiting GPU process due to errors during initialization
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8152]: MESA: error: Failed to query drm device.
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8152]: glx: failed to create dri3 screen
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8152]: failed to load driver: iris
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8152]: [129:0105/224138.675214:ERROR:components/viz/service/main/viz_main_impl.cc:189] Exiting GPU process due to errors during initialization
Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8195]: MESA: error: Failed to query drm device.

How can we reproduce the issue?

  1. Install Actual desktop via any Flathub manager on PopOS/Ubuntu 22.04 (Intel integrated graphics may also be required)
  2. Open application
  3. ---> See no content appears and see errors in systemd journal

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Linux

Originally created by @cgifford99 on GitHub (Jan 6, 2026). Originally assigned to: @MikesGlitch on GitHub. ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I was just testing out the new Flathub release and after successfully installing it through the PopOS Pop Shop, I seem to be unable to successfully launch the app. The app will start, but only an empty window appears with no content; only a frame and a blank background. I found some errors in the systemd journal that may be of use to you that I've attached at the bottom. I have already tried to resolve the issue via the "failed to create dri3 screen", "failed to load driver: iris" errors, but was not successful with the common solutions (i.e. reinstalling Mesa drivers + associated packages). System details: * OS: PopOS 22.04 * Kernel: 6.17.4-76061704-generic * CPU: Intel i5-12600K * GPU: Mesa Intel UHD Graphics 770 Please let me know if you need any more info from me. I'd be happy to help. <details><summary>systemd journal (expand to see log)</summary> <p> ``` Jan 05 22:41:38 dev-machine systemd[3385]: Started Application launched by gnome-shell. Jan 05 22:41:38 dev-machine systemd[3385]: Started app-flatpak-com.actualbudget.actual-8005.scope. Jan 05 22:41:38 dev-machine systemd[3385]: Started app-flatpak-com.actualbudget.actual-8029.scope. Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.358218: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 Jan 05 22:41:38 dev-machine actual[8015]: Failed to load module "canberra-gtk-module" Jan 05 22:41:38 dev-machine actual[8015]: Failed to load module "canberra-gtk-module" Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.492991: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 Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.493028: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 Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.534293: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 Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.534357: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 Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8015]: [2:0105/224138.534391: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 Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8065]: MESA: error: Failed to query drm device. Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8065]: glx: failed to create dri3 screen Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8065]: failed to load driver: iris Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8065]: [43:0105/224138.565327:ERROR:components/viz/service/main/viz_main_impl.cc:189] Exiting GPU process due to errors during initialization Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8152]: MESA: error: Failed to query drm device. Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8152]: glx: failed to create dri3 screen Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8152]: failed to load driver: iris Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8152]: [129:0105/224138.675214:ERROR:components/viz/service/main/viz_main_impl.cc:189] Exiting GPU process due to errors during initialization Jan 05 22:41:38 dev-machine com.actualbudget.actual.desktop[8195]: MESA: error: Failed to query drm device. ``` </p> </details> ### How can we reproduce the issue? 1. Install Actual desktop via any Flathub manager on PopOS/Ubuntu 22.04 (Intel integrated graphics may also be required) 2. Open application 3. ---> See no content appears and see errors in systemd journal ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Desktop App (Electron) ### Operating System Linux
GiteaMirror added the electronbug labels 2026-02-28 20:27:31 -06:00
Author
Owner

@youngcw commented on GitHub (Jan 6, 2026):

@MikesGlitch

@youngcw commented on GitHub (Jan 6, 2026): @MikesGlitch
Author
Owner

@MikesGlitch commented on GitHub (Jan 6, 2026):

That's a weird one, I also run POPOS 22.04 and it's working for me 🤔 I have an nvidia graphics card tho.

I asked ChatGPT, can you try running this?

flatpak update

Pay attention to updates for:

org.freedesktop.Platform
org.freedesktop.Platform.GL.default
org.freedesktop.Platform.GL32.default

If these are out of sync, Mesa inside the sandbox breaks.

Let me know if that works. If it doesn't can you try running this:

flatpak run --device=dri com.actualbudget.actual

That should hopefully give permission to dri explicitly, which should allow access to the graphics

@MikesGlitch commented on GitHub (Jan 6, 2026): That's a weird one, I also run POPOS 22.04 and it's working for me 🤔 I have an nvidia graphics card tho. I asked ChatGPT, can you try running this? ```flatpak update``` Pay attention to updates for: org.freedesktop.Platform org.freedesktop.Platform.GL.default org.freedesktop.Platform.GL32.default If these are out of sync, Mesa inside the sandbox breaks. Let me know if that works. If it doesn't can you try running this: ```flatpak run --device=dri com.actualbudget.actual``` That should hopefully give permission to dri explicitly, which should allow access to the graphics
Author
Owner

@MikesGlitch commented on GitHub (Jan 6, 2026):

This was also reported on Discord and running via flatpak run --device=dri com.actualbudget.actual worked for them.

I'm going to update the default permission set to include device=dri to resolve this issue.

@MikesGlitch commented on GitHub (Jan 6, 2026): This was also reported on Discord and running via ```flatpak run --device=dri com.actualbudget.actual``` worked for them. I'm going to update the default permission set to include `device=dri` to resolve this issue.
Author
Owner

@MikesGlitch commented on GitHub (Jan 6, 2026):

This should be published now, if you update to the latest version it should work.

Closing this

@MikesGlitch commented on GitHub (Jan 6, 2026): This should be published now, if you update to the latest version it should work. Closing this
Author
Owner

@cgifford99 commented on GitHub (Jan 6, 2026):

Works beautifully now, thanks!

@cgifford99 commented on GitHub (Jan 6, 2026): Works beautifully now, thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2776