element-hq / element-web

A glossy Matrix collaboration client for the web.
https://element.io
GNU Affero General Public License v3.0
11k stars 1.95k forks source link

Cannot login #27869

Open qqubes opened 1 month ago

qqubes commented 1 month ago

Steps to reproduce

The sequence of screenshots demonstrates what happens when I try to log in. element_io-1_2024-07-29_10-46-06 element_io-2_2024-07-29_10-47-14 element_io-3_2024-07-29_10-58-49 element_io-4_2024-07-29_10-59-29 element_io-5_2024-07-29_10-59-58 element_io-6_2024-07-29_11-01-08

Afterwards, it gets stuck waiting endlessly for logout.

Outcome

What did you expect?

To login as usual.

What happened instead?

Cannot.

Operating system

qubes OS

Browser information

Chromium Version 120.0.6099.224 (Official Build) built on Debian 11.8, running on Debian 11.9 (64-bit)

URL for webapp

app.element.io

Application version

browser

Homeserver

matrix.org

Will you send logs?

Yes

qqubes commented 1 month ago

Worked after restarting the computer.

qqubes commented 1 month ago

The issue has recurred.

I cannot restart my computer everytime I want to log into Matrix.

t3chguy commented 1 month ago

Will you send logs? Yes

Not seeing any logs from you

qqubes commented 1 month ago

@t3chguy I did try but got an error.

I will try again when I have time later, and document what happens.

qqubes commented 1 month ago

I see what happens:

When I try to log in it gets stuck (see Screenshot 3 above). Then if I get tired of waiting an reload the page, I get to Screenshot 4.

But then when I choose Send Logs, it gives the error:

Failed to send logs: No connected database

Btw, I this is using a web browser. I can log in using my Android device.

richvdh commented 1 month ago

getting stuck during login sounds somewhat like https://github.com/element-hq/element-web/issues/25779. To work around, reload the tab before trying to log in.

If sending logs via the application doesn't work, could you reproduce the problem with the developer console open (ctrl-shift-i), then save the console logs to disk, and upload?

qqubes commented 1 month ago

Here is a copypasta from the console section of the developer console:

contentScript.js:187 [PHANTOM] error getting eth provider options contentScript.js:187 [PHANTOM] error updating cache Error: Something went wrong. at SS. (contentScript.js:187:84324) at Generator.next () at s (contentScript.js:187:83132) Markdown.ts:395 Uncaught (in promise) ReferenceError: Cannot access 'q' before initialization at Object.J (Markdown.ts:395:5) at _.start (ReadyWatchingStore.ts:38:30) at get instance [as instance] (WidgetLayoutStore.ts:71:35) at ./node_modules/matrix-react-sdk/src/stores/widgets/WidgetLayoutStore.ts (WidgetLayoutStore.ts:524:48) at u (bootstrap:19:32) at ./node_modules/matrix-react-sdk/src/modules/ModuleRunner.ts (ModuleUiDialog.tsx:86:5) at u (bootstrap:19:32) at ./node_modules/matrix-react-sdk/src/SecurityManager.ts (AccessSecretStorageDialog.tsx:454:5) at u (bootstrap:19:32) at ./node_modules/matrix-react-sdk/src/MatrixClientPeg.ts (MatrixActionCreators.ts:378:5) Markdown.ts:395 Uncaught (in promise) ReferenceError: Cannot access 'q' before initialization at Object.J (Markdown.ts:395:5) at l.start (ReadyWatchingStore.ts:38:30) at d.start (AsyncStoreWithClient.ts:48:31) at WidgetMessagingStore.ts:38:18 at ./node_modules/matrix-react-sdk/src/stores/widgets/WidgetMessagingStore.ts (WidgetMessagingStore.ts:36:48) at u (bootstrap:19:32) at ./node_modules/matrix-react-sdk/src/stores/ActiveWidgetStore.ts (shouldHideEvent.ts:83:1) at u (bootstrap:19:32) at ./node_modules/matrix-react-sdk/src/stores/WidgetStore.ts (WidgetEchoStore.ts:118:1) at u (bootstrap:19:32) Markdown.ts:395 Uncaught (in promise) ReferenceError: Cannot access 'q' before initialization at Object.J (Markdown.ts:395:5) at l.start (ReadyWatchingStore.ts:38:30) at p.start (AsyncStoreWithClient.ts:48:31) at WidgetStore.ts:56:18 at ./node_modules/matrix-react-sdk/src/stores/WidgetStore.ts (WidgetStore.ts:54:48) at u (bootstrap:19:32) at ./node_modules/matrix-react-sdk/src/modules/ModuleRunner.ts (ModuleUiDialog.tsx:86:5) at u (bootstrap:19:32) at ./node_modules/matrix-react-sdk/src/SecurityManager.ts (AccessSecretStorageDialog.tsx:454:5) at u (bootstrap:19:32) /config.app.element.…ter=1722259125267:1 Failed to load resource: the server responded with a status of 404 () rageshake.ts:77 Failed to open log database: UnknownError rageshake.ts:164 Uncaught (in promise) Error: Failed to open log database: UnknownError at e.onerror (rageshake.ts:164:24) rageshake.ts:77 Error: Failed to open log database: UnknownError at e.onerror (rageshake.ts:164:24) compat.ts:27 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu rageshake.ts:77 startUpdater, current version is 1.11.71 rageshake.ts:77 DEPRECATED CONFIG OPTION: In the future, default_server_name will not be accepted. Please use default_server_config instead. rageshake.ts:77 No update available, already on 1.11.71 matrix-client.matrix…c2965/auth_issuer:1 Failed to load resource: the server responded with a status of 404 () rageshake.ts:77 StorageManager.idbLoad failed for account:mx_access_token Event 

richvdh commented 1 month ago

ok well, that didn't help much. I'm out of ideas.

syserr0r commented 1 month ago

In my case I had this on the windows x64 client immediately after installing an update that the client prompted me for. To fix I re-installed the Windows client.

The console stack trace wasn't as long/detailed in my case - all I had at the top of the trace was Cannot access 'q' before initialization