Needs a hotfix, latest flatpk update is unable to launch

[Scotty-Trees]

The latest update from today via Flathub's flatpak no longer allows the app to launch, here's the error when running it from the terminal. Appreciate an update when you have the time of course, thank you.

scott@fedora:~$ flatpak run com.discordapp.Discord
2024/06/05 01:34:50 socat[3] E "/run/user/1000/app/com.discordapp.Discord/discord-ipc-0" exists
Disabling updates already done
[5:0605/013451.096262: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
Discord 0.0.55
Quitting secondary instance.
Gtk-Message: 01:34:51.465: Failed to load module "pk-gtk-module"
Gtk-Message: 01:34:51.466: Failed to load module "pk-gtk-module"
[5:0605/013451.485675: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
[5:0605/013451.485738: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
blackbox: 2024-06-05T05:34:51.574Z 0 

----------------------------------------------
blackbox: 2024-06-05T05:34:51.593Z 1 Discord starting: {"releaseChannel":"stable","version":"0.0.55"}, modulepath: /home/scott/.var/app/com.discordapp.Discord/config/discord/0.0.55/modules
/app/bin/com.discordapp.Discord: line 18: kill: (3) - No such process
scott@fedora:~$ 

[DaPigGuy]

Removing ~/.var/app/com.discordapp.Discord/config/discord solves this for whatever reason...

[benjamin051000]

Just to be clear, ~/.var/app/com.discordapp.Discord/config/discord/ is a directory, so rm -rf ~/.var/app/com.discordapp.Discord/config/discord/ will do the trick. It appears to fix the startup crash for me.

[hazepastel]

Can confirm removing the config fixes this. My fedora machine was affected by this bug but not arch.

[MaledictYtb]

Removing ~/.var/app/com.discordapp.Discord/config/discord solves this for whatever reason...

This fixed my issue, but the bug seems to be back after a few days.

[Allexio]

Personally removing the data did fix the issue... until my next restart and then I had the same problem again...

[guihkx]

Does anyone have any clue as to what might trigger this? Clear steps to reproduce the problem would be ideal, though.

[MaledictYtb]

This always happening after a discord update, but it only happened twice for me and I'm not sure how to reproduce this.