Some flatpak apps crash due to a D-Bus issue

I’m not sure if this was a software update or not but suddenly some apps I used to use on a regular basis don’t launch. when I try running them via the terminal, it shows an error message regarding D-Bus, but I clearly can see the D-Bus file installed correctly on my system. also, I did not change or uninstalled anything lately.

I’m not quite sure what I’m doing but I tried force-enabling everything with D-Bus on Flatseal for one of the apps that won’t launch, and the error in terminal has changed:

any idea if it’s a problem on my system or maybe an app or system update?

1 Like

Please do not post screen shots of text post as pre-formatted text.
I cannot read the images or quote from them.

You can use the </> or type the markup:

```
pre formatted text here
```
1 Like

sorry.

this is the text from the first attempt:

flatpak run io.anytype.anytype
[2:0304/173513.237913:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Checking for beta autoupdate feature for deb/rpm distributions
Found package-type: deb
LaunchProcess: failed to execvp:
xdg-settings
[2:0304/173513.557555:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0304/173513.557598:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0304/173513.557621:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0304/173513.557646:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0304/173513.557665:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[ConfigManager].init: {
  channel: 'latest',
  theme: 'system',
  debug: {},
  flagsMw: {},
  systemInfo: true
}
[Server] start /app/Anytype/resources/app.asar.unpacked/dist/anytypeHelper /home/yotamguttman/.var/app/io.anytype.anytype/config/anytype
mw grpc: build on 2025-02-17 15:22:27 +0000 UTC at #f1ceda0a1457dbf982d8b3fd8479ccdcb95df6d3 (dirty)

gRPC server started at: 127.0.0.1:41803
gRPC Web proxy started at: 127.0.0.1:43067

[UpdateManager].init, channel:  latest
[InstallNativeMessaging] Manifest skipped: Chrome
[InstallNativeMessaging] Manifest skipped: Chromium
[InstallNativeMessaging] Manifest skipped: Brave
[InstallNativeMessaging] Manifest skipped: BraveFlatpak
[2:0304/173513.817973:ERROR:browser_main_loop.cc(279)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
[2:0304/173513.829845:ERROR:wayland_event_watcher.cc(47)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Could not bind the given EGLImage to a CoglTexture2D



this is from the second photo (second attempt after I enabled D-BUS):

yotamguttman@yotis-pc ~> flatpak run io.anytype.anytype
[2 zypak-helper] Wait found events, but sd-event found none
Checking for beta autoupdate feature for deb/rpm distributions
Found package-type: deb
LaunchProcess: failed to execvp:
xdg-settings
[ConfigManager].init: {
  channel: 'latest',
  theme: 'system',
  debug: {},
  flagsMw: {},
  systemInfo: true
}
[Server] start /app/Anytype/resources/app.asar.unpacked/dist/anytypeHelper /home/yotamguttman/.var/app/io.anytype.anytype/config/anytype
mw grpc: build on 2025-02-17 15:22:27 +0000 UTC at #f1ceda0a1457dbf982d8b3fd8479ccdcb95df6d3 (dirty)

gRPC server started at: 127.0.0.1:37283
gRPC Web proxy started at: 127.0.0.1:36525

[UpdateManager].init, channel:  latest
[InstallNativeMessaging] Manifest skipped: Chrome
[InstallNativeMessaging] Manifest skipped: Chromium
[InstallNativeMessaging] Manifest skipped: Brave
[InstallNativeMessaging] Manifest skipped: BraveFlatpak
[2:0304/173346.088254:ERROR:browser_main_loop.cc(279)] Gtk: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
[2:0304/173346.101619:ERROR:wayland_event_watcher.cc(47)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Could not bind the given EGLImage to a CoglTexture2D

yotamguttman@yotis-pc ~ [SIGILL]> 


edit:
I published this as an issue on Anytype a couple days ago and so far the only respond I received is from someone who fed the terminal content into chatgpt trying to solve the problem… the proposed solutions didn’t help. so I didn’t get the impression that know what causes it.

1 Like

It appears that the flatpak is not mapping this file/folder into the app’s sand box.

You need a flatpak expert to help. Maybe change the title to make it clear this is a flatpak issue.

There is a report on the Fedora page for AnyType of problems with autoupdate. Your snippet has:

Checking for beta autoupdate feature for deb/rpm distributions
Found package-type: deb

Looks like autoupdate is not handling Flatpak installations.

This message is normal for Electron Flatpak apps. Electron is trying to access something on the system bus but is blocked by the sandbox. This doesn’t break anything important, AFAIK.

This appears to be the issue. Searching that turns up a lot of references to nvidia. If you’re using the nvidia driver, try flatpak update.

1 Like

I update flatpak every day (via the software manager). didn’t seem to solve the problem.

yotamguttman@yotis-pc ~> flatpak update
Looking for updates…

Info: runtime org.gnome.FontManager.Locale branch stable is end-of-life, with reason:
   Application no longer supported due to changing Flathub policies.
Info: applications using this extension:
   org.gnome.FontManager

Info: app org.gnome.FontManager branch stable is end-of-life, with reason:
   Application no longer supported due to changing Flathub policies.

Nothing to do.

if the D-Bus is blocked by the sandbox, why did me enabling the D-Bus session an system in flatseal solve the problem?

But you already said it didn’t solve the problem?

Those messages will go away, but they’re inconsequential. Full session or system bus access is very insecure, BTW.

First check your kernel version using uname -a. Current version is 6.13.5-200.fc41.x86_64, which was a quick fix for a major issue in a previous version of the 6.13 series with flatpaks, and all containerized applications. So I advise checking your kernel version to rule this out as a possibility of your current issue.

1 Like

seems to be identical to the version you have mentioned. Linux yotis-pc 6.13.5-200.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Feb 27 15:07:31 UTC 2025 x86_64 GNU/Linux

what are the consequence of this?
I mentioned in my post that while I couldn’t say for sure, this issue seems to have appeared after the latest software update.

Then it is fine. I just mentioned this so you could exclude that the issue was due to that kernel problem. This indeed excludes that possibility.

so what do you suggest?
any idea what causes the issue? it used to work just fine, up until recently, and I never enabled it any D-Bus access manually before.

I do not have other suggestions myself. I just thought it useful to check whether your issue also could be related with that kernel issue. It isn’t.