# Not starting since wayland switch

**URL:** <https://forum.delta.chat/t/not-starting-since-wayland-switch/3676>\
**Category:** Mutual Help\
**Tags:** desktop\
**Created:** [April 2, 2025, 10:04am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676 "2025-04-02T10:04:12Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![mray](https://forum.delta.chat/user_avatar/forum.delta.chat/mray/32/10_2.png) [@mray](https://forum.delta.chat/u/mray)\
**Post date:** [April 2, 2025, 10:04am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/1 "2025-04-02T10:04:12Z")

</div>

**Delta Chat version**

**Delta Chat Desktop** 1.56.0 (git: flathub)

After a Manjaro update to finally use Wayland + nvidia + Gnome DeltaChat is among the few apps (all electron based) that don’t start anymore.

I did manage to get it running only with this command:

> flatpak run chat.delta.desktop --disable-gpu &

it spits out this, but starts:

> [2:0402/120544.826254: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  
> Logfile: /home/mray/.var/app/chat.delta.desktop/config/DeltaChat/logs/2025-04-02-12-05-44.log  
> [2:0402/120544.987896: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:0402/120544.987937: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:0402/120545.131981: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:0402/120545.132055: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:0402/120545.132097: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  
> init: 332.167ms  
> [2:0402/120545.256764:ERROR:browser\_main\_loop.cc(278)] Gtk: gtk\_widget\_get\_scale\_factor: assertion ‘GTK\_IS\_WIDGET (widget)’ failed  
> [2:0402/120545.691967:ERROR:browser\_main\_loop.cc(278)] Gtk: gtk\_widget\_get\_scale\_factor: assertion ‘GTK\_IS\_WIDGET (widget)’ failed

This is a crutch, as it requires an open terminal all the time.  
What is wrong? I’d like to keep using DeltaChat like before 😥

---

<div class="post-metadata">

**Author:** ![mray](https://forum.delta.chat/user_avatar/forum.delta.chat/mray/32/10_2.png) [@mray](https://forum.delta.chat/u/mray)\
**Post date:** [April 2, 2025, 10:05am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/2 "2025-04-02T10:05:49Z")

</div>

trying to run it without the extra arguments looks like this:

> flatpak run chat.delta.desktop  
> [2:0402/121411.433253: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  
> Logfile: /home/mray/.var/app/chat.delta.desktop/config/DeltaChat/logs/2025-04-02-12-14-11.log  
> [2:0402/121411.600787: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:0402/121411.600828: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:0402/121411.755514: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:0402/121411.755561: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:0402/121411.755584: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:0402/121411.771291: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

---

<div class="post-metadata">

**Author:** ![link2xt](https://forum.delta.chat/user_avatar/forum.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://forum.delta.chat/u/link2xt)\
**Post date:** [April 2, 2025, 1:29pm UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/3 "2025-04-02T13:29:35Z")

</div>

Do you have `XDG_SESSION_TYPE=wayland` set?

---

<div class="post-metadata">

**Author:** ![mray](https://forum.delta.chat/user_avatar/forum.delta.chat/mray/32/10_2.png) [@mray](https://forum.delta.chat/u/mray)\
**Post date:** [April 2, 2025, 1:39pm UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/4 "2025-04-02T13:39:37Z")

</div>

> [@link2xt](#):
>
> XDG\_SESSION\_TYPE=wayland

set where?

---

<div class="post-metadata">

**Author:** ![cyrneko](https://forum.delta.chat/user_avatar/forum.delta.chat/cyrneko/32/2621_2.png) [@cyrneko](https://forum.delta.chat/u/cyrneko)\
**Post date:** [April 4, 2025, 6:36am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/5 "2025-04-04T06:36:21Z")

</div>

The above mentioned variable generally shouldn’t be set by the user. The desktop does that already in 99,9% of cases.

it seems you got it from Flathub and recently updated, it _may_ be missing permissions to access either X11 or Wayland sockets so that it can actually show a window.

You can edit app permissions with [Flatseal](https://flathub.org/apps/com.github.tchx84.Flatseal) and double-check it has access

For reference, this is what it _should_ look like:

 ![image](https://support.delta.chat/uploads/default/original/2X/9/9269440d0593d9fbd2ce1b758143df5029f0a895.png)

* * *

The above however only applies if the issue is actually related to Wayland. It seems to me however that the issue may be in something else, namely something that Manjaro might have broke with dbus, as indicated by `dbus` seemingly being unreachable:

```auto
Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

```

Make sure Dbus is actually running, I believe that would be `systemctl status dbus` and `systemctl status --user dbus` for the system and session bus respectively; Don’t quote me on that though, just working from memory

---

<div class="post-metadata">

**Author:** ![mray](https://forum.delta.chat/user_avatar/forum.delta.chat/mray/32/10_2.png) [@mray](https://forum.delta.chat/u/mray)\
**Post date:** [April 4, 2025, 9:31am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/6 "2025-04-04T09:31:57Z")

</div>

Flatseal:

 ![image](https://support.delta.chat/uploads/default/original/2X/5/5c914ba20f85f06586b8aefe0a8c5bcab7b52787.png)

dbus (whatever that is) seems to be running:

> pc% systemctl status dbus  
> ● dbus-broker.service - D-Bus System Message Bus  
> Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; disabled; preset: disabled)  
> Active: active (running) since Thu 2025-04-03 20:52:08 CEST; 14h ago  
> Invocation: 1307b991cc0e46fc968f6cb059a0b5a4  
> TriggeredBy: ● dbus.socket  
> Docs: man:dbus-broker-launch(1)  
> Main PID: 881 (dbus-broker-lau)  
> Tasks: 2 (limit: 38030)  
> Memory: 7.5M (peak: 9.2M)  
> CPU: 270ms  
> CGroup: /system.slice/dbus-broker.service  
> ├─881 /usr/bin/dbus-broker-launch --scope system --audit  
> └─882 dbus-broker --log 4 --controller 9 --machine-id e877267b5f484426bad73d98be406f97 --max-bytes 536870912 --max-fds 4\>
> 
> Apr 03 20:52:08 pc systemd[1]: Starting D-Bus System Message Bus…  
> Apr 03 20:52:08 pc systemd[1]: Started D-Bus System Message Bus.  
> Apr 03 20:52:08 pc dbus-broker-launch[881]: Ready  
> Apr 03 20:52:09 pc dbus-broker-launch[881]: Activation request for ‘org.freedesktop.Avahi’ failed: The systemd unit 'dbus-org.freedes\>  
> Apr 03 20:52:12 pc dbus-broker-launch[881]: Activation request for ‘org.freedesktop.resolve1’ failed: The systemd unit 'dbus-org.free\>  
> Apr 03 20:52:13 pc dbus-broker-launch[881]: Activation request for ‘org.freedesktop.home1’ failed: The systemd unit 'dbus-org.freedes\>

🤔

what really makes me wonder is that manjaro on another machine here, that also switched to wayland seems to run DeltaChat just fine.

---

<div class="post-metadata">

**Author:** ![cyrneko](https://forum.delta.chat/user_avatar/forum.delta.chat/cyrneko/32/2621_2.png) [@cyrneko](https://forum.delta.chat/u/cyrneko)\
**Post date:** [April 4, 2025, 9:59am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/7 "2025-04-04T09:59:29Z")

</div>

Dbus, very much simplified, allows programs to exchange data. It is required for Flatpaks to properly work as it is the primary way to get data in and out of the app with the permissions system.

Make sure other flatpaks are working, and if they aren’t, I’d consult the Manjaro forums

---

<div class="post-metadata">

**Author:** ![mray](https://forum.delta.chat/user_avatar/forum.delta.chat/mray/32/10_2.png) [@mray](https://forum.delta.chat/u/mray)\
**Post date:** [April 4, 2025, 10:02am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/8 "2025-04-04T10:02:24Z")

</div>

maybe a relevant note:  
I noticed starting with “flatpak run chat.delta.desktop --disable-gpu” gets it running, but I can not resize the window by clicking on the edges. (hold middle click+super works, too)

Almost all other flatpaks run fine.

---

<div class="post-metadata">

**Author:** ![cyrneko](https://forum.delta.chat/user_avatar/forum.delta.chat/cyrneko/32/2621_2.png) [@cyrneko](https://forum.delta.chat/u/cyrneko)\
**Post date:** [April 4, 2025, 10:06am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/9 "2025-04-04T10:06:31Z")

</div>

“almost all”?

Which other ones don’t run? I completely overlooked that `--disable-gpu` thing and am starting to suspect it may be an Nvidia Moment \[1\]

* * *

1. (it may help to do `flatpak update` to see if the drivers are up-to-date, mismatched drivers on the System and Flatpak does not end well)

---

<div class="post-metadata">

**Author:** ![mray](https://forum.delta.chat/user_avatar/forum.delta.chat/mray/32/10_2.png) [@mray](https://forum.delta.chat/u/mray)\
**Post date:** [April 4, 2025, 10:11am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/10 "2025-04-04T10:11:48Z")

</div>

element (also an electron app) only starts with the extra addition, too. I have a ton of other flatpaks installed, all of them start.

---

<div class="post-metadata">

**Author:** ![cyrneko](https://forum.delta.chat/user_avatar/forum.delta.chat/cyrneko/32/2621_2.png) [@cyrneko](https://forum.delta.chat/u/cyrneko)\
**Post date:** [April 4, 2025, 10:14am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/11 "2025-04-04T10:14:56Z")

</div>

well that gives us a common denominator for the affected applications, at least

I assume the `dbus` warning is a fluke then, and considering the Nvidia GPU it is likely troubles there

If there’s no Nvidia driver updates when running `flatpak update`, I would probably consult [the Manjaro Forums](https://forum.manjaro.org/) about this issue and see if somebody else can help out

Sadly I don’t have an Nvidia system to test with anymore, I only got this intel one where the latest Flatpak runs just fine `:/`

---

<div class="post-metadata">

**Author:** ![mray](https://forum.delta.chat/user_avatar/forum.delta.chat/mray/32/10_2.png) [@mray](https://forum.delta.chat/u/mray)\
**Post date:** [April 4, 2025, 10:18am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/12 "2025-04-04T10:18:58Z")

</div>

Thanks for your time and effort! 😀  
So there is something good about it after all: it seems like DeltaChat does not need to fix anything.

I’ll see if i can find possible solutions on Manjaros/Nvidias side then…

---

<div class="post-metadata">

**Author:** ![Bastian](https://forum.delta.chat/letter_avatar_proxy/v4/letter/b/779978/32.png) [@Bastian](https://forum.delta.chat/u/Bastian)\
**Post date:** [April 14, 2025, 8:45am UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/13 "2025-04-14T08:45:55Z")

</div>

> [@mray](#):
>
> I noticed starting with “flatpak run chat.delta.desktop --disable-gpu” gets it running, but I can not resize the window by clicking on the edges. (hold middle click+super works, too)

Funny, I’ve been running into that same problem for resizing for a few days now. I’ve also installed Delta via flatpak (on Ubuntu 24). Other flatpak apps I use do not exhibit the same behaviour from my brief tests.

Happy to help debug more if there’s anything I can do to help!

---

<div class="post-metadata">

**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\
**Post date:** [October 6, 2026, 3:19pm UTC](https://forum.delta.chat/t/not-starting-since-wayland-switch/3676/14 "2026-10-06T15:19:53Z")

</div>


