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

„Missing session data“ with fresh session #26339

Closed
weeman1337 opened this issue Oct 9, 2023 · 8 comments
Closed

„Missing session data“ with fresh session #26339

weeman1337 opened this issue Oct 9, 2023 · 8 comments
Assignees
Labels
O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect X-Cannot-Reproduce

Comments

@weeman1337
Copy link
Contributor

weeman1337 commented Oct 9, 2023

Steps to reproduce

  1. Log in to Element Web
  2. Verify your session
  3. Close the browser window
  4. Reopen the window

Outcome

What did you expect?

Still be logged in

What happened instead?

„Missing session data“

Operating system

No response

Browser information

Chromium 117.0.5938.132

Ubuntu 22.04.3 LTS

URL for webapp

https://app.element.io/

Application version

No response

Homeserver

element.io

Will you send logs?

No

@weeman1337
Copy link
Contributor Author

Unfortunately Element refuses to send logs 😐 „Failed to send logs: No connected database“

Here is what I got in console:

Fetch event handler is recognized as no-op. No-op fetch handler may bring overhead during navigation. Consider removing the handler if possible.
/config.app.element.io.json?cachebuster=1696839431786:1     Failed to load resource: the server responded with a status of 404 ()
rageshake.ts:74 Failed to open log database: UnknownError
e.<computed> @ rageshake.ts:74
rageshake.ts:74 Error: Failed to open log database: UnknownError
    at e.onerror (rageshake.ts:158:24)
e.<computed> @ rageshake.ts:74
rageshake.ts:74 startUpdater, current version is 1.11.45
rageshake.ts:74 DEPRECATED CONFIG OPTION: In the future, default_server_name will not be accepted. Please use default_server_config instead.
e.<computed> @ rageshake.ts:74
rageshake.ts:74 No update available, already on 1.11.45
rageshake.ts:74 StorageManager.idbLoad failed for account:mx_access_token Event {isTrusted: true, type: 'error', target: IDBOpenDBRequest, currentTarget: IDBOpenDBRequest, eventPhase: 2, …}
e.<computed> @ rageshake.ts:74
overrideMethod @ console.js:213
(anonymous) @ logger.ts:48
be @ Lifecycle.ts:525
await in be (async)
ue @ Lifecycle.ts:243
C @ app.tsx:84
Show 1 more frame
Show less
rageshake.ts:74 getSessionLock[613e1481-15c3-4d4d-87c3-95b2b69730b9] No other session has the lock: proceeding with startup
rageshake.ts:74 StorageManager.idbLoad failed for account:mx_access_token Event {isTrusted: true, type: 'error', target: IDBOpenDBRequest, currentTarget: IDBOpenDBRequest, eventPhase: 2, …}
e.<computed> @ rageshake.ts:74
overrideMethod @ console.js:213
(anonymous) @ logger.ts:48
be @ Lifecycle.ts:525
await in be (async)
ye @ Lifecycle.ts:609
de @ Lifecycle.ts:202
(anonymous) @ MatrixChat.tsx:550
Promise.then (async)
loadSession @ MatrixChat.tsx:549
initSession @ MatrixChat.tsx:393
await in initSession (async)
(anonymous) @ MatrixChat.tsx:325
Xe @ MatrixChat.tsx:317
vo @ react-dom.production.min.js:135
qa @ react-dom.production.min.js:181
Ws @ react-dom.production.min.js:269
Dl @ react-dom.production.min.js:250
Rl @ react-dom.production.min.js:250
Fl @ react-dom.production.min.js:250
vl @ react-dom.production.min.js:243
ml @ react-dom.production.min.js:237
Jl @ react-dom.production.min.js:285
(anonymous) @ react-dom.production.min.js:289
El @ react-dom.production.min.js:244
oc @ react-dom.production.min.js:289
t.render @ react-dom.production.min.js:296
se @ init.tsx:150
error (async)
m @ StorageManager.ts:190
g @ StorageManager.ts:188
f @ StorageManager.ts:204
be @ Lifecycle.ts:523
ue @ Lifecycle.ts:243
C @ app.tsx:84
Show 1 more frame
Show less

@weeman1337
Copy link
Contributor Author

I am getting the same with Element Desktop:

rageshake.ts:74 Failed to open log database: UnknownError
consoleObj.<computed> @ rageshake.ts:74
rageshake.ts:74 Error: Failed to open log database: UnknownError
    at req.onerror (rageshake.ts:158:24)
consoleObj.<computed> @ rageshake.ts:74
rageshake.ts:74 DEPRECATED CONFIG OPTION: In the future, default_server_name will not be accepted. Please use default_server_config instead.
consoleObj.<computed> @ rageshake.ts:74
rageshake.ts:74 StorageManager.idbLoad failed for account:mx_access_token Event
consoleObj.<computed> @ rageshake.ts:74
rageshake.ts:74 StorageManager.idbLoad failed for account:mx_refresh_token Event
consoleObj.<computed> @ rageshake.ts:74
rageshake.ts:74 getSessionLock[dbc6f150-f9dc-4566-9e3f-14270b0678f5] No other session has the lock: proceeding with startup
rageshake.ts:74 StorageManager.idbLoad failed for account:mx_access_token Event
consoleObj.<computed> @ rageshake.ts:74
rageshake.ts:74 StorageManager.idbLoad failed for account:mx_refresh_token Event
consoleObj.<computed> @ rageshake.ts:74

@robintown
Copy link
Member

@weeman1337 Can you check whether you accepted the 'store data in persistent storage' permission in the browser? (Not sure what the exact message is on Chromium…)

@robintown robintown added the S-Critical Prevents work, causes data loss and/or has no workaround label Oct 13, 2023
@robintown
Copy link
Member

Unable to reproduce on Firefox

@robintown robintown added O-Occasional Affects or can be seen by some users regularly or most users rarely X-Cannot-Reproduce labels Oct 13, 2023
@weeman1337
Copy link
Contributor Author

@weeman1337 Can you check whether you accepted the 'store data in persistent storage' permission in the browser? (Not sure what the exact message is on Chromium…)

Unfortunately I cannot find such a permission 🤷

@weeman1337
Copy link
Contributor Author

I will add a „Send logs“ button to the dialog. We are then going to close this issue and hope, that we get better debug data in the future.

@weeman1337 weeman1337 self-assigned this Oct 19, 2023
@weeman1337
Copy link
Contributor Author

Closing in favour of https://github.com/vector-im/element-web/issues/26464 with logs

@weeman1337 weeman1337 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2023
@weeman1337
Copy link
Contributor Author

I will add a „Send logs“ button to the dialog. We are then going to close this issue and hope, that we get better debug data in the future.

The button is already there if a URL is configured

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect X-Cannot-Reproduce
Projects
None yet
Development

No branches or pull requests

2 participants