Skip to content
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

CURLCode 35 #170

Open
bjoli opened this issue Mar 2, 2025 · 6 comments
Open

CURLCode 35 #170

bjoli opened this issue Mar 2, 2025 · 6 comments

Comments

@bjoli
Copy link

bjoli commented Mar 2, 2025

Hi!

Suddenly my install v1.2.0 (build 87) stopped working.

This is the error message I get:

The Launcher failed to sign you in
Please login again
Failed to perform http request to https://android.clients.google.com/auth 👍
CURLcode 35 Details: TLS connect error:
error:80000002:system library::No such file or directory

I tried logging in and out again, to no avail. This is the errors I get running it in verbose mode:

~> flatpak run io.mrarm.mcpelauncher --verbose
Downloading Versionsdb "https://raw.githubusercontent.com/minecraft-linux/mcpelauncher-versiondb/v1.2.x/versions.armeabi-v7a.json.min"
QQmlExpression: Expression qrc:/qml/HomeScreen.qml:155:13 depends on non-NOTIFYable properties:
    LauncherSettings::gameDataDir
qml: Bug: No version
Loading gamepad mappings: /app/share/mcpelauncher/gamecontrollerdb.txt
Loading gamepad mappings: /app/share/mcpelauncher/gamecontrollerdb.txt
Downloading Versionsdb "https://raw.githubusercontent.com/minecraft-linux/mcpelauncher-versiondb/v1.2.x/versions.arm64-v8a.json.min"
Downloading Versionsdb "https://raw.githubusercontent.com/minecraft-linux/mcpelauncher-versiondb/v1.2.x/versions.x86.json.min"
Downloading Versionsdb "https://raw.githubusercontent.com/minecraft-linux/mcpelauncher-versiondb/v1.2.x/versions.x86_64.json.min"
Version list loaded, entry count: 1692
qml: Versionslist initialized
qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0
js: Error with Permissions-Policy header: Unrecognized feature: 'ch-ua-form-factors'.
js: Error with Permissions-Policy header: Unrecognized feature: 'ch-ua-form-factors'.
xkbcommon: ERROR: /usr/share/X11/locale/en_US.UTF-8/Compose:1661:1: unrecognized keysym "dead_hamza" on left-hand side
xkbcommon: ERROR: /usr/share/X11/locale/en_US.UTF-8/Compose:1662:1: unrecognized keysym "dead_hamza" on left-hand side
xkbcommon: ERROR: /usr/share/X11/locale/en_US.UTF-8/Compose:1663:1: unrecognized keysym "dead_hamza" on left-hand side
xkbcommon: ERROR: /usr/share/X11/locale/en_US.UTF-8/Compose:1664:1: unrecognized keysym "dead_hamza" on left-hand side
xkbcommon: ERROR: /usr/share/X11/locale/en_US.UTF-8/Compose:1665:1: unrecognized keysym "dead_hamza" on left-hand side
js: [DOM] Found 2 elements with non-unique id #ca: (More info: https://goo.gl/9p2vKq) %o %o
js: [DOM] Found 2 elements with non-unique id #ct: (More info: https://goo.gl/9p2vKq) %o %o
js: [DOM] Found 2 elements with non-unique id #identifierId: (More info: https://goo.gl/9p2vKq) %o %o
js: Error with Permissions-Policy header: Unrecognized feature: 'ch-ua-form-factors'.
qt.qpa.wayland.textinput: virtual void QtWaylandClient::QWaylandTextInputv3::zwp_text_input_v3_leave(wl_surface*) Got leave event for surface 0x0 focused surface 0x55ab14fd3bf0

Best regards
Linus

@bjoli
Copy link
Author

bjoli commented Mar 3, 2025

I downgraded the package to the one released in november, and I hit the same issue. I also updated a bunch of runtimes, and I wonder if it is there the problem lies.

@bjoli
Copy link
Author

bjoli commented Mar 5, 2025

So I did something I should have done earlier: I installed it as a different user and now it works.

Is there any way I can wipe my install, but save the data?

/Linus

@bjoli
Copy link
Author

bjoli commented Mar 5, 2025

I wiped the install (but saved the world), but it still does not work. I think it is related to me using guix as well as my system package manager and that there is some weird business going on, either with regards to shared libraries or cert stores. That would at least explain why it works with a new, clean user.

What I am trying moving forward, in ascending levels of work effort:

  1. Checking if I am running the system flatpaks or if I accidentally installed the guix one. (I am not at my computer now)
  2. doing a guix GC to make sure I don't have any incompatibilities in the package store.
  3. Checking if flatpak tries to load any guix library.
  4. Checking whether there is some certificate stuff going on.

This could be closed as a PEBKAC, but if I am allowed I will do it myself after posting if any of the above things solved my issue.

Best regards
Linus

@ChristopherHX
Copy link
Collaborator

I wiped the install (but saved the world)

I don't think uninstalling only this package is enough, because the error is more likely in package org.kde.platform (a dependency).

Did you reinstall it as well?

If another user used a flatpak user (not system) setup, then yes it has an independent org.kde.platform possible not corrupted version

@bjoli
Copy link
Author

bjoli commented Mar 5, 2025

I think I know what the issue is. Guix sets SSL_CERT_DIR and SSL_CERT_FILE to a directory flatpak doesn't have access to.

I will investigate that and come back to you. It should probably be enough to give mcpelauncher access to all system files.

I will try your solution as well if my fix doesn't work. Thank you for your reply.

I wiped the install (but saved the world)

I don't think uninstalling only this package is enough, because the error is more likely in package org.kde.platform (a dependency).

Did you reinstall it as well?

If another user used a flatpak user (not system) setup, then yes it has an independent org.kde.platform possible not corrupted version

@ChristopherHX
Copy link
Collaborator

I actually cannot believe what I read here flatpak/flatpak#4280 (comment)

imo there a more reasons to pass no env variable from the system, this confirms how broken flatpaks are by design.

flatpak run --env=SSL_CERT_DIR= --env=SSL_CERT_FILE= io.mrarm.mcpelauncher should opt out passing them as non empty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants