Hello Epic Games team,
I’m reporting an authentication issue with the new Epic Games Launcher Linux Preview on Fedora 44. After extensive troubleshooting, I found a workaround that successfully completes authentication.
System information
-
OS: Fedora Linux 44
-
Kernel: 7.2.9-200.fc44.x86_64
-
Desktop: GNOME (Wayland)
-
GPU: AMD Radeon RX 580 2048SP
-
Browser: Google Chrome 155 (Flatpak)
-
Launcher: 0.95.2 (Linux AppImage)
Problem
When launching EpicGamesLauncher-x86_64.AppImage directly, the application starts normally. However, when attempting to sign in, it displays:
“Continue in your browser”
The system browser never opens, and the launcher remains indefinitely waiting for authentication.
The application successfully creates a localhost OAuth callback listener, but the authentication process does not complete.
Relevant logs
Auth.BrowserSignInRequested
Auth.Sisu.BrowserOpened
Auth.Sisu.AwaitingCallback
AUTH_ERROR: Not authenticated
Troubleshooting performed
I verified the default browser configuration, confirmed that Chrome opens successfully through both Flatpak and xdg-open, checked the GNOME desktop portal services, and tested a clean launcher startup.
The issue persisted.
Working workaround
I extracted the AppImage and launched its internal executable:
./EpicGamesLauncher-x86_64.AppImage --appimage-extract
./squashfs-root/AppRun
This worked successfully. Chrome opened, OAuth authentication completed, and my Epic Games library loaded correctly.
The logs confirmed:
Auth.Token.ExchangeSucceeded
Auth.SignInTokensReceived
Additional issue: Updates
When running the extracted application, the launcher reports:
SelfUpdate.LinuxFlavorUnsupported
It appears the extracted installation is no longer recognized as a supported Linux package, potentially preventing automatic launcher updates.
Expected behavior
The packaged AppImage should automatically open the default browser and complete authentication without requiring extraction.
Request
Could the Epic Games Launcher team investigate the difference between executing the AppImage directly and running the extracted AppRun executable?
This workaround may also help other Linux users experiencing the same authentication issue.
Thank you for supporting Linux and for your work on the new launcher!