"Discord installation is corrupt" and stuck on RTC Connecting

[ghost]

I installed Discord today on my openSUSE Aeon (formerly MicroOS Desktop) install and I was greeted with this red banner above the app. No matter what I did, like deleting the folder from .var/app or updating my host system, nothing works. I cannot connect to any voice chat and at times when I launch the app, I get logged out and have to re-enter my credentials. It also seems like it has trouble recognizing my Input and Output devices, but it does play notification sounds.

[JoshTrono]

I am also having this issue. A fresh install of Opensuse aeon (MicroOs). Running it from the command line gives this multiple times

[5:0716/202616.554434:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

I tried all the workaround (that I found) with dbus but nothing seem to be working on Opensuse Aeon

[JoshTrono]

I got discord to work on my side. Had to reinstall openSuse Aeon/MicroOs through the tumbleweed installer and selecting transactional server then add microOs gnome desktop inside the software section. Once I booted it up I was able to install discord flatpak and run it. All I had to do was manually install distrobox.

This seems like OpenSuse microOs installer issue not a flatpak issue and since it's still in RC which is the reason I tried it through the Tumbleweed installer

[DarielVR]

This happens because of SELinux policies on Aeon/Kalpa. If you do ausearch -m AVC,USER_AVC,SELINUX_ERR,USER_SELINUX_ERR | grep Discord with sudo, you will get an output like this type=AVC msg=audit(1689654119.769:130): avc: denied { execstack } for pid=4319 comm="Discord" scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=process permissive=0. So executing setsebool selinuxuser_execstack 1 with sudo fixes the problem. However, this is considered insecure and the default policy won't be changed; in theory, it can be fixed on the application side, but I'm not sure if something can be done for the discord flatpak and doing a rollback to a previous snapshot doesn't seem to fix the problem.

[grisu48]

I filed https://bugzilla.opensuse.org/show_bug.cgi?id=1216237 for this.

[guihkx]

Looks like this is not our bug. Closing.