Emulator

Game Name?

No game needed

Game ID? (right click the game in the game list, Properties, Info tab)

N/A

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

N/A

What's the problem? Describe what went wrong.

When using the Flatpak on Fedora Linux 42 (the official dolphin flatpak, I have verified that I am NOT using the Fedora flatpak), when closing Dolphin from the GUI, Fedora believes the program is crashing and sends an abrt alert. Running the flatpak from the terminal elucidates that something is wrong with how the dbus system is handled. Here is the full output when I run and close the emulator from terminal.

/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=/app/bin/dolphin-emu-wrapper org.DolphinEmu.dolphin-emu
F: Not sharing "/usr/share/themes" with sandbox: Path "/usr" is reserved by Flatpak
GameMode ERROR: D-Bus error: Could not call method 'RegisterGame' on 'org.freedesktop.portal.Desktop': Portal operation not allowed: Could not parse '/run/user/1000/.flatpak/4131777256/bwrapinfo.json': empty file
gamemodeauto: D-Bus error: Could not call method 'RegisterGame' on 'org.freedesktop.portal.Desktop': Portal operation not allowed: Could not parse '/run/user/1000/.flatpak/4131777256/bwrapinfo.json': empty file
Qt: Session management error: Could not open network socket
GameMode ERROR: D-Bus error: Could not call method 'UnregisterGame' on 'org.freedesktop.portal.Desktop': Portal operation not allowed: Could not to open '/proc/pid/35823': No such file or directory
gamemodeauto: D-Bus error: Could not call method 'UnregisterGame' on 'org.freedesktop.portal.Desktop': Portal operation not allowed: Could not to open '/proc/pid/35823': No such file or directory
dbus[35819]: arguments to dbus_pending_call_block() were incorrect, assertion "pending != NULL" failed in file ../dbus/dbus-pending-call.c line 768.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace

What steps will reproduce the problem?

1. Open the Dolphin flatpak
2. Attempt to close it
3. A crash is thrown

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

Unknown

Is the issue present in the latest release? For future reference, please also write down the version number of the latest release.

Yes, 2506

If the issue isn't present in the latest release, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
2506

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

N/A

What are your PC specifications? (CPU, GPU, Operating System, more)
kinfo
Operating System: Fedora Linux 42
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.9-300.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 7800 XT

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

See above for terminal output.