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

Cannot login when the keyring is locked (Ubuntu Mate 22.04) #878

Open
JokerGermany opened this issue Apr 22, 2022 · 12 comments
Open

Cannot login when the keyring is locked (Ubuntu Mate 22.04) #878

JokerGermany opened this issue Apr 22, 2022 · 12 comments
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect Z-Linux

Comments

@JokerGermany
Copy link

Steps to reproduce

I logged in with google Account.
After this i only get a loading screen.

Outcome

What did you expect?

beeing logged in

What happened instead?

loading screen

Operating system

Ubuntu Mate 22.04

Application version

can't see, should be the newest

How did you install the app?

https://packages.element.io/debian/

Homeserver

matrix.org

Will you send logs?

Yes

@JokerGermany
Copy link
Author

This is the console output:

vector/:59          GET vector://vector/fonts/Inter/Inter-BoldItalic.2129bd0.woff2 net::ERR_FILE_NOT_FOUND
vector/:61          GET vector://vector/fonts/Inter/Inter-Bold.fc28dff.woff2 net::ERR_FILE_NOT_FOUND
vector/:63          GET vector://vector/fonts/Inter/Inter-SemiBoldItalic.10a60d8.woff2 net::ERR_FILE_NOT_FOUND
vector/:65          GET vector://vector/fonts/Inter/Inter-SemiBold.0802d48.woff2 net::ERR_FILE_NOT_FOUND
vector/:67          GET vector://vector/fonts/Inter/Inter-MediumItalic.8154ac2.woff2 net::ERR_FILE_NOT_FOUND
vector/:69          GET vector://vector/fonts/Inter/Inter-Italic.b791861.woff2 net::ERR_FILE_NOT_FOUND
vector/:71          GET vector://vector/fonts/Inter/Inter-Medium.027d14e.woff2 net::ERR_FILE_NOT_FOUND
vector/:73          GET vector://vector/fonts/Inter/Inter-Regular.4232a67.woff2 net::ERR_FILE_NOT_FOUND
rageshake.ts:72 Initialised rageshake.
rageshake.ts:72 To fix line numbers in Chrome: Meatball menu → Settings → Ignore list → Add /rageshake\.js$
rageshake.ts:72 Using Electron platform
rageshake.ts:72 Using WebAssembly Olm
rageshake.ts:72 Configuring rageshake persistence...
rageshake.ts:72 Loading skin...
rageshake.ts:72 Skin loaded!
rageshake.ts:72 set language to de
rageshake.ts:72 Application is running in production mode
rageshake.ts:72 Vector starting at vector://vector/webapp/
rageshake.ts:72 Verifying homeserver configuration
rageshake.ts:72 Config uses a default_server_name - doing .well-known lookup
rageshake.ts:72 DEPRECATED CONFIG OPTION: In the future, default_server_name will not be accepted. Please use default_server_config instead.
e.<computed> @ rageshake.ts:72
(anonymous) @ logger.ts:50
(anonymous) @ app.tsx:210
m @ app.tsx:105
ne @ init.tsx:161
await in ne (async)
(anonymous) @ index.ts:225
await in (anonymous) (async)
61 @ index.ts:236
l @ bootstrap:68
(anonymous) @ bootstrap:272
(anonymous) @ bundle.js:2
rageshake.ts:72 Using homeserver config: h {hsUrl: 'https://matrix-client.matrix.org', hsName: 'matrix.org', hsNameIsDifferent: true, isUrl: 'https://vector.im', isDefault: true, …}
rageshake.ts:72 Updating SdkConfig with validated discovery information
rageshake.ts:72 Overrode homeserver setting with https://matrix-client.matrix.org/ from login response
rageshake.ts:72 Logged in with token
rageshake.ts:72 EventIndex: Deleting event index.
rageshake.ts:72 Removing indexeddb instance: matrix-js-sdk:crypto
rageshake.ts:72 Removed indexeddb instance: matrix-js-sdk:crypto
rageshake.ts:72 IndexedDB worker is ready
logger.ts:52 Removing indexeddb instance: matrix-js-sdk:riot-web-sync
logger.ts:52 Removed indexeddb instance: matrix-js-sdk:riot-web-sync
rageshake.ts:72 Deleted indexeddb data.
rageshake.ts:72 Session persisted for @xxx.xxx:matrix.org
rageshake.ts:72 Redirecting to vector://vector/webapp/?element-desktop-ssoid=GAtzay5ARtgQcqayFdrxaxCHTuRyjbpE#/ to drop loginToken from queryparams
rageshake.ts:72 No pickle key available
rageshake.ts:72 Restoring session for @xxx.xxx:matrix.org
rageshake.ts:72 setLoggedIn: mxid: @xxx.xxx:matrix.org deviceId: XMSRBCORXB guest: false hs: https://matrix-client.matrix.org/ softLogout: false  freshLogin: true
rageshake.ts:72 StorageManager: Checking storage consistency
rageshake.ts:72 StorageManager: Local storage supported? true
rageshake.ts:72 StorageManager: IndexedDB supported? true
rageshake.ts:72 StorageManager: Local storage contains data? true
rageshake.ts:72 StorageManager: Crypto initialised? false
rageshake.ts:72 StorageManager: Sync store using IndexedDB contains data? false
rageshake.ts:72 StorageManager: Crypto store using IndexedDB contains data? false
rageshake.ts:72 StorageManager: Storage consistency checks passed
rageshake.ts:72 Session persisted for @xxx.xxx:matrix.org
rageshake.ts:72 Lifecycle: Starting MatrixClient
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
The resource <URL> was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.

@JokerGermany
Copy link
Author

¯_(ツ)_/¯ I set up another pc with ubuntu mate 22.04 and used a old element-desktop profile from ubuntu mate 20.04 and it just worked like i only restarted the system...

@SimonBrandner SimonBrandner added the S-Critical Prevents work, causes data loss and/or has no workaround label Apr 23, 2022
@andybalaam andybalaam added the O-Occasional Affects or can be seen by some users regularly or most users rarely label Apr 25, 2022
@novocaine novocaine added O-Uncommon Most users are unlikely to come across this or unexpected workflow X-Cannot-Reproduce and removed O-Occasional Affects or can be seen by some users regularly or most users rarely labels Apr 27, 2022
@novocaine
Copy link
Contributor

novocaine commented Apr 27, 2022

This isn't apparently happening to many others so -

  • Does it happen after restarting Element?
  • If you open developer tools (ctrl+shift+I) can you see failed network requests?

@JokerGermany
Copy link
Author

Yes it happens even after restarting.
Where can I see failed network requests?
I posted the console output of the developer console above.

As long as the person, which own the computer, is on vacation i can give you more informations about this.

@JokerGermany
Copy link
Author

I have 4 other PCs which can use Element-Desktop on the matrix.org homeserver.
And 4 android devices.

@novocaine
Copy link
Contributor

If you are able to open developer tools (ctrl+shift+I) there is a network tab you can inspect.

@JokerGermany
Copy link
Author

JokerGermany commented Apr 28, 2022

If found this
network-element
€dit:
Okay looks the same on my own pc.
No i didn't found anything

@JokerGermany
Copy link
Author

JokerGermany commented Apr 29, 2022

Okay it looks like the problem is related to the keyring, which wasn't unlocked, because i don't know the password.
When i gave the PC to the person today and it unlocked the keyring, everything works.

I didn't know that element desktop access the keyring.

It would be nice to get an info that you have to unlock your keyring first, before he can login.
That even the console didn't give a hint about this...

To be clear what happens even when you have logged in before:
It is stucked on the rotating login screen and you can only sign out.
when you sign out then and sign in again (via google authentication) you are stuck again in the login screen before it looks like element is waiting for unlocking the keyring.

A Message like "Waiting for unlocking the keyring" would be nice.

@JokerGermany JokerGermany changed the title Can't login with fresh installed Element-Desktop on Ubuntu Mate 22.04 No Login and hint when keyring is locked Apr 29, 2022
@JokerGermany JokerGermany changed the title No Login and hint when keyring is locked No Login and hint when keyring is locked (Ubuntu Mate 22.04) Apr 29, 2022
@JokerGermany JokerGermany changed the title No Login and hint when keyring is locked (Ubuntu Mate 22.04) No hint when keyring is locked (Ubuntu Mate 22.04) Apr 29, 2022
@JokerGermany
Copy link
Author

How to reproduce:
close element
lock the keyring
start element

@novocaine novocaine changed the title No hint when keyring is locked (Ubuntu Mate 22.04) Cannot login when the keyring is locked (Ubuntu Mate 22.04) May 5, 2022
@novocaine novocaine added S-Minor Impairs non-critical functionality or suitable workarounds exist and removed X-Cannot-Reproduce S-Critical Prevents work, causes data loss and/or has no workaround labels May 5, 2022
@ara4n
Copy link
Member

ara4n commented Nov 29, 2022

We should surely fail hard if the keychain isn't available.

@t3chguy
Copy link
Member

t3chguy commented Nov 29, 2022

But we don't store whether it wasn't available in the first place, so it not being available may be expected, not all systems have keyrings enabled

@JokerGermany
Copy link
Author

JokerGermany commented Nov 29, 2022

Just another add to this because i suppose this i related. (I think i will open an seperate issue to that)
It looks like this problem ocours for me (and some of which computer i installed) on startup very often!
Element is added to autostart and often just a plain white windows appears. You need to close the Element then and start it manual. I suppose it's because the keychain haven't already startet. (It didn't recover when the keychain is there) The thing is, that it overlaps everything and is forecfully in the foreground else and if you don't know that you can "kill" this window by closing element, then you can't do anything^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect Z-Linux
Projects
None yet
Development

No branches or pull requests

6 participants