-
Notifications
You must be signed in to change notification settings - Fork 267
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
Crash (coredump) seemingly while rebuilding the messages index #932
Comments
This looks like a community package, i suggest seeking help from the packager. Official packages bake in with an electron rather than using a separate system executable. |
Distro bug opened at https://bugs.archlinux.org/task/78329; the issue seems to be closely related to messages index though, and it seems that once it finished rebuilding the index it stopped crashing (as it didn't crash before I reset the index). |
Yup, the arch package uses the wrong major version of sqlcipher, we build against the dependency available in Debian and Ubuntu which is 3.4, some packagers take our debs and repack them but depend on sqlcipher 4.3 Looks like the above is relevant to the AUR nightly, the mainline package builds it statically itself. It's possible the Seshat update in the next release may change things for it. |
@t3chguy Which build or AUR package should we be using instead? Even the Flatpak has this issue. |
You're welcome to use any you wish, but they're not provided by us, so you'll need to seek help from their maintainers. We only provide static tarball builds and an apt repo separate to that. |
@t3chguy Where do I find these static tarball builds and do they auto-update? |
Oh, by the way, no I'm not using an AUR package here, but the community stable one, https://archlinux.org/packages/community/x86_64/element-desktop/ |
https://packages.element.io/desktop/install/linux/glibc-x86-64/index.html they do not auto update. |
It seems like the latest version(s) of Element no longer has this issue on Arch. Can anyone confirm? I've deleted the ~/.config/Element folder entirely to check if it can rebuild the index from scratch and it seems to be happily chugging along. Is this due to the Seshat update that you mentioned, @t3chguy? |
@urbenlegend that depends entirely on how your Arch package is being built. I unfortunately am not involved in that process so do not know. Previously arch was using the wrong major version of sqlcipher |
I get these occasional crashes with the official element deb packages as well. There's not much visible in the console log though:
Edit: Okay, in the beginning this worked okay-ish with only 2 crashes in 10 minutes. But now it's crashing every couple of seconds, seemingly after indexing a single batch of messages. :-( |
Steps to reproduce
It seems to happens at random time, but was caused by the fact I had to reset my messages index because I experienced this: #904
Outcome
It shouldn't crash
Operating system
Linux
Application version
1.11.26-1
How did you install the app?
Package Manager
Logs
Coredump
Messages before and after the coredump in
journalctl
:The text was updated successfully, but these errors were encountered: