Skip to content

Google sign-in fails on old Linux distribution (flatpak) #1107

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
anszom opened this issue Apr 2, 2025 · 4 comments
Open

Google sign-in fails on old Linux distribution (flatpak) #1107

anszom opened this issue Apr 2, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@anszom
Copy link

anszom commented Apr 2, 2025

Describe the bug

I have a somewhat ancient Linux installation - Linux Mint 19.3 based on ubuntu bionic. I've been using the appimages for a while but now I need to switch to flatpak.

When I'm trying to log in to google account immediately crashes the launcher. If launched from console, the following error is shown:

Fontconfig error: Cannot load config file "/run/host/font-dirs.xml": No such file: /run/host/font-dirs.xml
Qt: Session management error: Could not open network socket
Loading gamepad mappings: /app/share/mcpelauncher/gamecontrollerdb.txt
Loading gamepad mappings: /app/share/mcpelauncher/gamecontrollerdb.txt
[2:19:0402/191931.820101:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/Flatpak: org.freedesktop.DBus.Error.InvalidArgs: No such property 'supports'

To Reproduce
Steps to reproduce the behavior:

  1. Start the launcher on an old Linux system
  2. Click on 'Sign in with google'
  3. See the launcher window disappear

Expected behavior
The log-in process should continue. If this is not feasible, then the minimum requirements for the launcher should be better documented.

Desktop (please complete the following information):

Additional context
When I copied the configuration file from the AppImage version, so that my login credentials are already in place, the launcher worked correctly (although it failed to log in to MS account, which may be an unrelated problem).

@anszom anszom added the bug Something isn't working label Apr 2, 2025
@ChristopherHX
Copy link
Member

You could try to disable the "easy" webview login

e.g.

flatpak run --env=USE_WEBENGINE=0 io.mrarm.mcpelauncher

@ChristopherHX
Copy link
Member

the minimum requirements for the launcher should be better documented.

This is error probably out of scope and caused by https://github.com/flathub/io.qt.qtwebengine.BaseApp

IMHO, why does qtwebengine insist to crash my application? I don't like this feature.

I have not been aware of any minimum requirements, only that flatpak has poor stability

@anszom
Copy link
Author

anszom commented Apr 3, 2025

With USE_WEBENGINE=0 it works just fine. I guess that the MS account login issue could be related to this after all, but I've managed to bypass it with the "remote connect" (or something like this) option.

I have not been aware of any minimum requirements, only that flatpak has poor stability

Oh my.. If this wasn't the one thing that flatpak was supposed to solve...

@ChristopherHX
Copy link
Member

I guess that the MS account login issue could be related to this after all, but I've managed to bypass it with the "remote connect

Yes exactly, this is the way for everyone having issues to do the ms login.

Given mojang provided this workaround, nothing has been added from my side

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants