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-desktop does not start; only showing spinning wheel #15807

Closed
br-olf opened this issue Nov 24, 2020 · 2 comments
Closed

element-desktop does not start; only showing spinning wheel #15807

br-olf opened this issue Nov 24, 2020 · 2 comments
Labels
A-Storage Storage layer of the app, including IndexedDB, local storage, etc. T-Other Questions, user support, anything else

Comments

@br-olf
Copy link

br-olf commented Nov 24, 2020

Description

Since my last reboot, when I'm starting element-desktop I only see a spinning wheel.
This is maybe a duplicate of #7730 but because this ticket is very old I don't want to resurrect it.

Steps to reproduce

  • start element-desktop

Sry, I don't have an idea how to reproduce this bug. I'll probably start over with a new profile, this seems to work.

Logs are attached:
The web-console log: Element-electron__vector.log
Command line output when started with --enable-logging: Element-console.log

Maybe the reboot corrupted my profiles?
This would be a very bad bug in my opinion but I admit I don't understand JavaScript and this is only based on Failed to open log database: UnknownError.

Version information

  • Platform: desktop app

  • OS: Linux M09998 5.9.10-1-MANJARO #1 SMP PREEMPT Sun Nov 22 11:25:19 UTC 2020 x86_64 GNU/Linux

  • Version: element-desktop 1.7.13-1 (AUR package)

@jryans jryans added T-Other Questions, user support, anything else A-Storage Storage layer of the app, including IndexedDB, local storage, etc. and removed T-Defect labels Nov 24, 2020
@jryans
Copy link
Collaborator

jryans commented Nov 24, 2020

From the logs, it looks like the data in the profile directory believe it is locked for some reason, and so it gives up on trying to use it. You could try quitting Element, then removing /home/myname/.config/Element-profilename/IndexedDB/vector_vector_0.indexeddb.leveldb/LOCK and starting Element again.

If that does not work, then I would recommend a fresh profile indeed, which you've mentioned does seem to work.

@br-olf
Copy link
Author

br-olf commented Nov 24, 2020

Thank you very much, this worked 👍

Also, I had to force close all electron processes in addition to the element-desktop processes:

killall -9 element-desktop
killall -9 electron
rm ~/.config/Element-$PROFILE/IndexedDB/vector_vector_0.indexeddb.leveldb/LOCK

element-desktop --profile $PROFILE

@br-olf br-olf closed this as completed Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Storage Storage layer of the app, including IndexedDB, local storage, etc. T-Other Questions, user support, anything else
Projects
None yet
Development

No branches or pull requests

2 participants