-
Notifications
You must be signed in to change notification settings - Fork 284
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
1.11.90 won't start (Devuan Excalibur/Debian Sid, kernel 6.12) #2083
Comments
I found that I can still access the settings and the developer tools, and in the dev tools console I see: init.js:1 Uncaught (in promise) ReferenceError: Cannot access 'F' before initialization
at Object.J (init.js:1:81211)
at b.start (ReadyWatchingStore.ts:30:30)
at get instance (WidgetLayoutStore.ts:63:35)
at ./src/stores/widgets/WidgetLayoutStore.ts (WidgetLayoutStore.ts:518:48)
at u (bootstrap:19:32)
at ./src/utils/WidgetUtils.ts (init.js:1:1394917)
at u (bootstrap:19:32)
at ./src/stores/ActiveWidgetStore.ts (init.js:1:1187187)
at u (bootstrap:19:32)
at ./src/stores/WidgetStore.ts (init.js:1:1213920)
init.js:1 Uncaught (in promise) ReferenceError: Cannot access 'F' before initialization
at Object.J (init.js:1:81211)
at l.start (ReadyWatchingStore.ts:30:30)
at d.start (AsyncStoreWithClient.ts:40:31)
at WidgetMessagingStore.ts:30:18
at ./src/stores/widgets/WidgetMessagingStore.ts (WidgetMessagingStore.ts:28:48)
at u (bootstrap:19:32)
at ./src/stores/ActiveWidgetStore.ts (init.js:1:1187221)
at u (bootstrap:19:32)
at ./src/stores/WidgetStore.ts (init.js:1:1213920)
at u (bootstrap:19:32)
init.js:1 Uncaught (in promise) ReferenceError: Cannot access 'F' before initialization
at Object.J (init.js:1:81211)
at l.start (ReadyWatchingStore.ts:30:30)
at p.start (AsyncStoreWithClient.ts:40:31)
at WidgetStore.ts:42:18
at ./src/stores/WidgetStore.ts (WidgetStore.ts:40:48)
at u (bootstrap:19:32)
at ./src/modules/ModuleRunner.ts (init.js:1:1101386)
at u (bootstrap:19:32)
at ./src/SecurityManager.ts (init.js:1:139915)
at u (bootstrap:19:32)
rageshake.ts:69 emojibase MAX_EMOJI_VERSION 15
rageshake.ts:69 DEPRECATED CONFIG OPTION: In the future, default_server_name will not be accepted. Please use default_server_config instead.
Object.keys.forEach.e.<computed> @ rageshake.ts:69
matrix-client.matrix.org/_matrix/client/unstable/org.matrix.msc2965/auth_issuer:1
Failed to load resource: the server responded with a status of 404 ()
rageshake.ts:69 checkSessionLockFree No other session has the lock
rageshake.ts:69 getSessionLock[cbcbccd1-09b4-41c2-81ee-8fbb2b4b53af] No other session has the lock: proceeding with startup
rageshake.ts:69 Default empty persistCredentials() => void
matrix-client.matrix.org/_matrix/client/unstable/org.matrix.msc2965/auth_issuer:1
Failed to load resource: the server responded with a status of 404 ()
rageshake.ts:69 Auth issuer not found M_UNRECOGNIZED: MatrixError: [404] Unrecognized request (https://matrix-client.matrix.org/_matrix/client/unstable/org.matrix.msc2965/auth_issuer)
at h (vector://vector/webapp/bundles/b970cc80953f1c145ccb/2178.js:2:397153)
at A.requestOtherUrl (vector://vector/webapp/bundles/b970cc80953f1c145ccb/2178.js:2:401701)
at async te.init (vector://vector/webapp/bundles/b970cc80953f1c145ccb/init.js:1:967342)
matrix-client.matrix.org/_matrix/client/unstable/org.matrix.msc2965/auth_issuer:1
Failed to load resource: the server responded with a status of 404 ()
rageshake.ts:69 Failed to discover OIDC metadata M_UNRECOGNIZED: MatrixError: [404] Unrecognized request (https://matrix-client.matrix.org/_matrix/client/unstable/org.matrix.msc2965/auth_issuer)
at h (vector://vector/webapp/bundles/b970cc80953f1c145ccb/2178.js:2:397153)
at A.requestOtherUrl (vector://vector/webapp/bundles/b970cc80953f1c145ccb/2178.js:2:401701)
at async vector://vector/webapp/bundles/b970cc80953f1c145ccb/element-web-app.js:1:1013548 |
@clickworkorange you might need to turn on Bundled Emoji Font in Settings > Appearance, or turn it off & on as there's a bug where it sometimes resets. Or install an emoji font on your OS. |
Turning it off, and on again, fixed it. Happy to see that this ancient IT troubleshooting method still remains useful. |
Steps to reproduce
After upgrading to latest Devuan/Debian (with kernel 6.12.9) element-desktop 1.11.90 gets stuck on the loading screen (spinner). Launching from console shows
I don't think the
libva
error has anything to do with it becauseNor do I think the
nss_util
error is related either, since I get the same error when launching the Chromium browser from the console and it works absolutely fine.Outcome
What did you expect?
I expected element-desktop to load my contacts and show the message history.
What happened instead?
It got stuck on the loading screen indefinitely.
Operating system
Devuan Excalibur / Debian Sid
Application version
1.11.90
How did you install the app?
Installed from Element apt repository
Homeserver
matrix.org
Will you send logs?
No
The text was updated successfully, but these errors were encountered: