Download Dolphin Linux
Scarlett Gehle
My dolphin-emu was working fine last night, but I updated arch today and now everything has stopped functioning. I am unsure of what to do. Whenever I launch a game through this application, the game will just sit there with a black screen and nothing initiates. After a few seconds pass by, the application will crash and my terminal output gives me this message:
EDIT: Furthermore, whenever I try and delete both configuration folders (dolphin-emu in .config (folder for application settings) & dolphin-emu in .share (folder for saved games and memory cards) and attempt to revert the application to its default state, it doesn't function correctly. Whenever I click on 'set game directory/double click' in the center of the screen and navigate to the folder with my games, it doesn't add them despite listing the directory paths in the games folder when I open the configuration panel up and look under 'paths'.
As it turns out, something broke with the package, dolphin-emu. After doing a bit of searching and testing on another machine, I found the same results. So that tells me that the maintainer or developer of this particular package could have changed something vital for the emulator to actually run.
I've just recompiled dolphin-emu-git and didn't get any errors. However one of the dependencies, libspng, requires manually importing the GPG key (linked in its PKGBUILD) or forcing a gpg check skip on it, otherwise the whole installation will fail.
I did try the regular dolphin-emu from the Arch's repo just now as well and it still segfaults as before so I'll keep sticking with the AUR git version. I don't quite understand why fixing the official package is taking so long, I thought it was built from the AUR package anyway?
Optionally you can change the install prefix by adding "-DCMAKE_INSTALL_PREFIX=/new/path". Note that this path does not need to be absolute. cmake will complete it to its absolute equivalent. The default prefix is "/usr". This means that the executable will be installed as "/usr/bin/dolphin-emu", the plugins will be installed into "/usr/lib/dolphin-emu", and the shared data files will be installed into "/usr/share/dolphin-emu".
Put this script in any directory, preferably a subdirectory of the Home directory, such as /.scripts/dolphin
Within this directory, the script will create two subdirectories, dolphin-emu and build. It must remain in this directory to work.
Execute the script from anywhere, by running sh /path/to/the/script.sh, where /path/to/the/script.sh is replaced with the actual path to the script.
The script will download Dolphin's source, or update it if it has already been downloaded once. After building it, the script will install it. This requires root privileges. After the installation, the script exits, and Dolphin can be used. Note that the process is very fast and simple after the first time. Using a bash alias to execute the script by running a custom command such as dolphin-update is recommended.
I don't know what happened that the dolphin stopped working, everything was fine yesterday. and today the meatball. Doesn't this sometimes have something to do with today's Qt5 update? I just rebuilt the dolphin-emu package and it does nothing, same thing with dolphin-emu-git. When I run it from terminal there is only this
Hi, for some reason dolphin emulator will not recognise any controls (gamepad or keyboard) when trying to play Gamecube. Ive tried to configure them manually using the Dolphin application (using the F1 key to access), but still cannot get it to recognise anything.
Why do you open dolphin emulator within Applications?
You should just open the games via gameslist in Emulation Station and your controller should then work out-of-the-box (except, there is a compatability issue with Gamesir GS3 bluetooth controller, then this has to be investigated)
i know that there are some pads, that have issues, especially with dolphin (and Dreamcast (reicast or flycast) i believe).
at least i remember some users reporting issues with certain pads (xbox 360 clones for example).
maybe the GameSir GS3 (wirelessly) and that unbranded generic Bluetooth USB controller are also pads, that have some issues/incompatability with dolphin also?
best is to come to the discord and ask there under #support
I have been distrohopping for last month or so trying to find something that will suit me and will work on my laptop and with my printer and scanner without problems. So far Garduda works great apart from root access in Dolphin.
I'm trying to access boot/efi in Dolphin. When I open efi I end up in empty folder with "cannot access /boot/efi/" message. I also tried using Dolphin right-click menu -> Administrator actions -> Open in file manager, but after typing root password in popup window it just closes with no effect.
Also tried adding new entry in app launcher "Dolphin (root)" with dbus-launch dolphin -qwindowtitle "%c" "%u" command (works in openSUSE and endeavouros). It opens Dolphin, but still no root access and same unable to access message.
Is there any way to give Dolphin root access in Garuda?
Thanks for quick reply.
I know it's KDE, but on other OS 's dbus-launch works and on Garuda not.
Just tried pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY KDE_SESSION_VERSION=5 KDE_FULL_SESSION=true dolphin
No. I had kde-servicemenus-rootactions installed already. I use Polish language so I translated "Działania administratora" to "Administartor actions", which was incorrect as it is "Root actions"
Also tried kdesu dbus-launch dolphin
Same - asks for su password and nothing happens.
When I open dolphin and try navigating to some directory in my $HOME while the NFS server is unreachable (for example when I managed to put my laptop to sleep [not easy on linux] and opened it somewhere else) it just hangs indefinetly. CLI utilities, my poorly written go/ts/java/rust applications, even chrome, none of them have any issues.
df19127ead