Edit: I’m no longer looking for help with this. The issue seems to be with the app itself and I have submitted a bug report for the app on github.
Before you tell me I should try another n64 emulator, I have been using other emulators but I have a game that isn’t working and I’m trying to run it in other emulators.
Anyways, if I try to run simple64 through the terminal, I get the error message:
Failed to load module "xapp-gtk3-module"
I tried to look into this and it seems that I’m supposed to install “xapp” but I’m getting the error message:
The following packages have unmet dependencies: xapp : Depends: libxapp1 (= 2.2.8-1) but 2.8.2+virginia is to be installed E: Unable to correct problems, you have held broken packages.
I tried to fix it with sudo apt --fix-broken install xapp but it’s just giving me the same error message. Is there anything else I can try before I try another emulator?
The command shows you have version 2.8 installed from the Mint repositories, but whatever you’re trying to install through APT wants a much lower version (it appears to want the old version that ships with Ubuntu, 2.2). The software you’re trying to apt install isn’t designed to work with the library versions Mint comes with.
That said, as others have said before, installing through APT won’t fix your Flatpak issue. Your APT problem and your Flatpak problem are completely separate. I believe there is a conflict between libxapp1 (the package Mint uses) and xapp (the package Ubuntu uses). Trying to force the Ubuntu package will break your system updates and possibly programs that worked before.
As for the warning message: it’ shouldn’t be the cause for your Flatpaks to fail entirely. The xapp library required is supposed to be included in the Flatpak application itself, so no amount of installing APT software will clear up these warnings. Luckily, many of these warning messages can be safely ignored, unless they’re printed in bold red or start with “Error:”.
If you run an Nvidia card, you may be running into a quirk of their driver. For reasons presumably only clear to Nvidia, 3D acceleration tends to die after installing a driver update, but only in some cases. If you have an Nvidia card, try rebooting, updating, and rebooting again; this tends to fix weird issues for me. On other GPU platforms you can try to do the same, but in my experience neither AMD nor Intel require these reboots to maintain functionality.