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.

Sign up for GitHub

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

Jump to bottom

Local message search event index failed to initialise #21158

Closed
germain-gg opened this issue Feb 22, 2022 · 12 comments
Closed

Local message search event index failed to initialise #21158

germain-gg opened this issue Feb 22, 2022 · 12 comments
Labels
A-E2EE A-Electron A-Indexing Indexing messages via Seshat A-Timeline-Search O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Team: Crypto

Comments

@germain-gg
Copy link
Contributor

germain-gg commented Feb 22, 2022 •
edited by pmaier1
Loading

Steps to reproduce

  1. My local event index got corrupted on Element Desktop
  2. Try to follow the options to recover
  3. That didn't work, disable search altogether
  4. Try to re-enable it

Outcome

What did you expect?

For the event crawler to do it's job

What happened instead?

Screen Shot 2022-02-22 at 11 43 24

The above will spin forever...
Looking at the console I can see

Uncaught (in promise) TypeError: Cannot read properties of null (reading 'addInitialCheckpoints')
    at EventIndexPanel.tsx:129:15

Screen Shot 2022-02-22 at 11 44 04

Operating system

macOS

Application version

No response

How did you install the app?

No response

Homeserver

No response

Will you send logs?

No
@germain-gg germain-gg added T-Defect S-Major Severely degrades major functionality or product features, with no satisfactory workaround A-Electron A-Indexing Indexing messages via Seshat O-Occasional Affects or can be seen by some users regularly or most users rarely labels Feb 22, 2022
@novocaine novocaine changed the title Event index failed to initialise Local message search event index failed to initialise Feb 22, 2022
@turt2live
Copy link
Member

How did it end up getting corrupted?

@turt2live turt2live added the X-Needs-Info This issue is blocked awaiting information from the reporter label May 17, 2022
@germain-gg
Copy link
Contributor Author

I don't know. I just know it ended up being corrupted one day.

@germain-gg germain-gg removed the X-Needs-Info This issue is blocked awaiting information from the reporter label May 17, 2022
@turt2live
Copy link
Member

hmm, alright. Without knowing what caused it to become corrupted I don't think we can reasonably look into this. Practically speaking, we could simulate various types of corruption however I don't believe that would actually fix any realistic problems.

Closing for now. If it happens again, please open a new issue with modern information.

@germain-gg germain-gg reopened this May 18, 2022
@germain-gg germain-gg reopened this May 18, 2022
@germain-gg
Copy link
Contributor Author

@turt2live the issue still happens on my install of Element Nightly
Would be happy to add any info you need. Just not entirely sure how to get my hands on the the ipc logs of the packaged application.

@germain-gg
Copy link
Contributor Author

I did look into my logs a bit further and you find that the event index failed to initialise because of an invalid passphrase.
What's weird is that the event index is completely disable as I've tried to reset it in the past.

Somehow ended up in this limbo state. There's probably a way to remove some files on disk to fix that, but I don't think that's a satisfactory workaround to resolve this issue

@turt2live
Copy link
Member

Can we get those logs uploaded to a rageshake?

@germain-gg
Copy link
Contributor Author

germain-gg commented May 18, 2022 •
edited
Loading

@turt2live done

Relevant log line,

2022-05-18T09:22:32.016Z I EventIndex: Error initializing the event index {"message":"Error opening the database: DatabaseUnlockError(\"Invalid passphrase\")"}```

@lampholder
Copy link
Member

Seems related - I just got this:

image

It feels frustrating to rely on me to click the "unbreak my software" button when Element could have elected to rebuild the index upon discovering that it is (presumably irretrievably) corrupted?

@lampholder
Copy link
Member

I've rage shook

@lampholder
Copy link
Member

Also, the only way to fix this is hidden in an "advanced" dropdown.

@duxovni duxovni mentioned this issue Jul 1, 2022
Closed
@turt2live
Copy link
Member

sending this to the crypto team for now as I think it's their domain. Alternatively, the rust team.

@t3chguy t3chguy mentioned this issue Mar 13, 2023
Closed
@t3chguy
Copy link
Member

t3chguy commented Mar 13, 2023

Duplicate of element-hq/element-desktop#904

@t3chguy t3chguy closed this as completed Mar 13, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-E2EE A-Electron A-Indexing Indexing messages via Seshat A-Timeline-Search O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Team: Crypto
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@MadLittleMods @germain-gg @turt2live @lampholder @t3chguy