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

Element stuck loading when opening #2018

Open
lautriva opened this issue Nov 26, 2024 · 8 comments
Open

Element stuck loading when opening #2018

lautriva opened this issue Nov 26, 2024 · 8 comments
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-Needs-Info This issue is blocked awaiting information from the reporter

Comments

@lautriva
Copy link

lautriva commented Nov 26, 2024

Steps to reproduce

  1. Update element from apt to 1.11.86
  2. Run element-desktop

Outcome

What did you expect?

Be in main element interface with rooms, friends list, etc...

What happened instead?

White screen with a loader and the "logout" button

image

launch logs:

$ element-desktop 
/home/my_username/.config/Element exists: yes
/home/my_username/.config/Riot exists: no
Starting auto update with base URL: https://packages.element.io/desktop/update/
Auto update not supported on this platform
Fetching translation json for locale: en_EN
Changing application language to fr
Fetching translation json for locale: fr
Resetting the UI components after locale change
Resetting the UI components after locale change
Changing application language to fr
Fetching translation json for locale: fr
Resetting the UI components after locale change

Operating system

Linux Mint 21.3

Application version

1.11.86

How did you install the app?

packages.element.io via apt

Homeserver

Synapse (I don't know the version, its private server run by a friend)

Will you send logs?

No

@dosubot dosubot bot added 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 labels Nov 26, 2024
@t3chguy
Copy link
Member

t3chguy commented Nov 26, 2024

Application version
1.11.83

Please try a newer version, you're 3 versions out of date

@t3chguy t3chguy added the X-Needs-Info This issue is blocked awaiting information from the reporter label Nov 26, 2024
@lautriva
Copy link
Author

Sorry it was a typo, I'm on 1.11.86

@lautriva
Copy link
Author

Update :

When showing electron devtools, I got a bunch of errors like this:

Uncaught (in promise) ReferenceError: Cannot access 'V' before initialization
    at Object.J (init.js:1:82257)
    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:1409348)
    at u (bootstrap:19:32)
    at ./src/stores/ActiveWidgetStore.ts (init.js:1:1195811)
    at u (bootstrap:19:32)
    at ./src/stores/WidgetStore.ts (init.js:1:1222544)

@lautriva
Copy link
Author

Tried to disconnect and then reconnect, now it works

@Viehlieb
Copy link

Tried to disconnect and then reconnect, now it works

could you maybe expand on that? I got the same problem on Ubuntu 20 and element-desktop 1.11.86

@Viehlieb
Copy link

Tried to disconnect and then reconnect, now it works

could you maybe expand on that? I got the same problem on Ubuntu 20 and element-desktop 1.11.86

ah okay, got it myself. "logout" and then it works again.

@jahway603
Copy link

I was experiencing the same issue but downgrading to 1.11.85 fixed it for me.

Is there any way to further explore why this is happening to have a better solution than to logout and then login again (which creates another session that needs to be verified)?

@jahway603
Copy link

I was experiencing the same issue but downgrading to 1.11.85 fixed it for me.

Is there any way to further explore why this is happening to have a better solution than to logout and then login again (which creates another session that needs to be verified)?

I spoke too soon - Element Desktop v 1.11.85 has issues with messages not being sent in certain rooms.

Any suggestions on how to troubleshoot this? I am stuck either never logging in with v 1.11.86 or stuck with not being able write messages in certain rooms with v 1.11.85.

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-Needs-Info This issue is blocked awaiting information from the reporter
Projects
None yet
Development

No branches or pull requests

4 participants