Unable to sign in

[guillaumechauvat]

Application Version

4.10.0

Platform

Arch linux

Printer

Ultimaker 2

Reproduction steps

1. Launch Cura with no data saved
2. Click on "sign in" when the menu appears
3. Get redirected to Firefox with a login page and sign in there.

Actual results

The login appears successful in Firefox, but Cura doesn't see it.

Clicking on "sign in" again in Cura has no effect.

If I skip the login there, I can click on "Check for account updates" but it fails and looks like this:

Expected results

I can sign in and synchronise my account.

Checklist of files to include

• Log file
• Project file

Additional information & file uploads

Logs:
cura.log

[fvrmr]

Hi @guillaumechauvat did this happen with the AppImage of Cura?

[guillaumechauvat]

No, it's the Arch Linux package. I can try installing another way if you want.

[guillaumechauvat]

Okay, so I tried using the AppImage and it gave some clues about what is going on.

It started launching but crashed with

ModuleNotFoundError: No module named 'keyring.backends.null'

It turns out that I had a file $HOME/.config/python_keyring/keyringrc.cfg that contained:

[backend]
default-keyring=keyring.backends.null.Keyring

After removing that file, the AppImage launched. It failed in a different way when I clicked on "sign in":

/usr/bin/xdg-open: line 613: 595893 Segmentation fault      (core dumped) kde-open${KDE_SESSION_VERSION} "$1"

which seems to be the same as #10087 .

However now the Cura version installed from the Arch Linux package manager works fine!

Edit: Well, "works fine" as far as authentication goes, but I still can't see the materials I installed on my account, even though they are compatible with the printer I selected.

[fvrmr]

Thank you for taking a look at it. I will bring this up for discussion with the team. Keep you posted!

[konskarm]

That was a really helpful and detailed report @guillaumechauvat! We do not support the Keyring on Linux (since we'd have to ship a specific keyring package with it) and it wasn't explicitly ignoring local Keyring configs. I've fixed it now to make sure that it won't load any keyring backends on Linux #10302.

For our internal tracking, devs see ticket CURA-8490.

[Ghostkeeper]

This is fixed by #10302 for Cura 4.11.