Crash `Recvmsg error: Connection reset by peer (104) Trace/breakpoint trap (core dumped)`

5HT2 commented 2 years ago

Steps to reproduce

Open element

$ element-desktop
/home/user/.config/Element exists: yes
/home/user/.config/Riot exists: no
No update_base_url is defined: auto update is disabled
Fetching translation json for locale: en_EN
Changing application language to en-us,en
Fetching translation json for locale: en-us
Fetching translation json for locale: en
Resetting the UI components after locale change
Resetting the UI components after locale change
Changing application language to en-us
Fetching translation json for locale: en-us
Resetting the UI components after locale change
[141732:0919/210047.337243:ERROR:broker_posix.cc(40)] Recvmsg error: Connection reset by peer (104)
Trace/breakpoint trap (core dumped)

Leave the client opened

Outcome

What did you expect?

No crash.

What happened instead?

Crash

Operating system

Arch Linux

Application version

element-desktop 1.11.4-1

How did you install the app?

aur

Homeserver

frogg.ie on docker running matrixdotorg/synapse:latest. Not sure how to get version from the container.

Will you send logs?

Yes

5HT2 commented 1 year ago

@hunter2k01 it looks like a config / cache reset in your case might help.

Error getting the event index passphrase out of the secret store [Error: user interaction failed]

hagenest commented 1 year ago

Same happening for me since at least December with the Element Flatpak on both OpenSUSE MicroOS and Tumbleweed. Gnome 43.3, Wayland, Kernel 6.1.

The application works perfectly for between 30 seconds and 2 minutes and then crashes without a warning.

Journalctl:

Feb 18 13:10:05 pc-71-192.customer.ask4.lan kernel: traps: element-desktop[19648] trap int3 ip:55f3c88093ef sp:7ffc8af16330 error:0 in element-desktop[55f3c5021000+75e0000]
Feb 18 13:10:05 pc-71-192.customer.ask4.lan im.riot.Riot.desktop[19647]: /app/bin/element: line 16:     3 Trace/breakpoint trap   (core dumped) env TMPDIR="$XDG_RUNTIME_DIR/app/${FLATPAK_ID:-im.riot.Riot}" zypak-wrapper /app/Element/element-desktop $FLAGS "$@"
Feb 18 13:10:05 pc-71-192.customer.ask4.lan systemd[1909]: app-flatpak-im.riot.Riot-19663.scope: Consumed 53.706s CPU time.
Feb 18 13:10:05 pc-71-192.customer.ask4.lan systemd[1909]: app-flatpak-im.riot.Riot-19632.scope: Consumed 1min 9.967s CPU time.

Weirdly enough this doesn't happen on the Element-Fork Schildichat (Flatpak too)

t3chguy commented 1 year ago

@hagenest looks like Schildichat doesn't include libsqlcipher0 system dependency https://github.com/search?q=repo%3ASchildiChat%2Fschildichat-desktop%20libsqlcipher0&type=code which is the cause for this issue in the community packages e.g. flatpak. The community flatpak for Element just takes our deb and repackages it instead of using a more appropriate build.

iyanmv commented 1 year ago

It was already pointed out before, but I can confirm the app crashes for me on Wayland using electron 22. Either running it with XWayland or downgrading to electron 21 solves the issue for me.

laiti commented 1 year ago

This started happening for me as well with 1.11.20-1 and Manjaro Linux. Element asks me to login even though I have been logged in earlier. After I log in and confirm my session with phone it loads some of the room and then crashes. Tried the removal of ~/.var/app/im.riot.Riot/ but it does not exist on my system.

Kidlike commented 1 year ago

Can confirm that disabling the search inside Element settings fixes the crash.

Element app reports:

Element version: 1.11.23
Olm version: 3.2.12

Flatpak version:

$ flatpak --version
Flatpak 1.12.7

$ flatpak list  | grep -i riot
Element im.riot.Riot    1.11.23 stable  system

On Fedora 35 (oops I know... need to update), with X11.

heigre commented 1 year ago

Confirming that disabling search (Profile picture -> All settings -> Security and Privacy ->Message Search -> Manage --> Disable) solved the issue for me as well.

Element version: 1.11.20
Olm version: 3.2.12

Element Desktop installed via AUR on Arch.

5HT2 commented 1 year ago

Now that I think about it (as the author of this issue), I only ever encountered this after enabling Search, that is probably it.

5HT2 commented 1 year ago

@turt2live mind updating the status of this issue? it seems like it's affecting quite a few people

t3chguy commented 1 year ago

@5HT2 the vast majority of reports here are from community-maintained packages, the Flatpak for example wrongly repacks the .deb package and is a known fault with that package for example - https://github.com/flathub/im.riot.Riot/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+crash so the occurrence on the official package is far lower

5HT2 commented 1 year ago

Ah, okay! I'm unsure why the issue happens then, intuition says it's probably a missing package / thing that needs to be running for search DB indexing to work?

davidmehren commented 1 year ago

@t3chguy Did you or another Element developer contact @SISheogorath about the "wrong" repackaging? I imagine quite a few users utilize the Flatpak and (therefore?) have a bad experience. Maybe you could work on a solution together, so this does not end in a "downstream is holding it wrong"/"upstream does not accept our bugs" stalemate.

In any case, in https://github.com/vector-im/element-desktop/issues/648 the problem was reproduced on a supported platform, so it does not seem to purely be a packaging problem.

t3chguy commented 1 year ago

I imagine quite a few users utilize the Flatpak and (therefore?) have a bad experience.

The flatpak has many bugs specific to its packaging and then some usability quirks because of the packaging also so even aside this issue it'll be a bad experience. It is generally not advisable to blindly take one package intended for a given system & dependencies and repackage into another (Flatpak). We provide github actions for the entire build so its not like it'd be hard to do it properly.

so it does not seem to purely be a packaging problem.

Indeed, it looks to be https://github.com/matrix-org/seshat or one of its dependencies exploding which is nearly guaranteed in certain packages but rare in the official ones. My best guess is that it is related to libsqlcipher and how it shares symbols with sqlite

harmathy commented 1 year ago

I installed the official deb Packages on a freshly installed Debian 11 bullseye and indeed couldn't reproduce any crash. While on the same system I could reproduce the crash during indexing using the flatpak package, which can be mitigated by disabling the search index.

Kidlike commented 1 year ago

Any chance for an official rpm package then? :grin:

t3chguy commented 1 year ago

@Kidlike https://github.com/vector-im/element-desktop/issues/658

iyanmv commented 1 year ago

I installed the official deb Packages on a freshly installed Debian 11 bullseye and indeed couldn't reproduce any crash. While on the same system I could reproduce the crash during indexing using the flatpak package, which can be mitigated by disabling the search index.

Wayland?

harmathy commented 1 year ago

Wayland?

Yes, but same on Xorg!

5HT2 commented 1 year ago

I reported this issue and I am on Xorg.

FilBot3 commented 1 year ago

Confirming that disabling search (Profile picture -> All settings -> Security and Privacy ->Message Search -> Manage --> Disable) solved the issue for me as well.
Element version: 1.11.20
Olm version: 3.2.12
Element Desktop installed via AUR on Arch.

This so far is what works for me. I just have to be fast about it before the window closes.

eckce commented 1 year ago

This issue occurs for me on three different (similarly configured) PCs. Disabling message search as previously described appears to mitigate the issue. All three PCs use Wayland on Arch Linux with the following packages, installed from the Arch package repository (not flatpak):

electron 22.3.3-1 element-desktop 1.11.20-1

pedrompcaetano commented 1 year ago

I'm running the following version of element flatpak on fedora rawhide: $ flatpak info im.riot.Riot

Element - Create, share, communicate, chat and call securely, and bridge to other apps

      ID: im.riot.Riot
     Ref: app/im.riot.Riot/x86_64/stable
    Arch: x86_64
  Branch: stable
 Version: 1.11.28
 License: Apache-2.0
  Origin: flathub

Collection: org.flathub.Stable Installation: system Installed: 362.5 MB Runtime: org.freedesktop.Platform/x86_64/22.08 Sdk: org.freedesktop.Sdk/x86_64/22.08

  Commit: 710c4a54700b7d82ca5fec116ed1d31104e23f2502935ff068a11843aa2d9523
  Parent: a8c6ccc974e0686f6b7cebc4cfaba69f129e3453ebe053d5a9068cfb58efae48
 Subject: Update element-desktop_1.11.27_amd64.deb to 1.11.28 (f091c9a3)
    Date: 2023-03-31 22:26:38 +0000

When trying to disable message search, the following text is displayed:

Message search

Element is missing some components required for securely caching encrypted messages locally. If you'd like to experiment with this feature, build a custom Element Desktop with search components added.

Unfortunately element crashes within a few minutes of running.

aquatix commented 1 year ago

Happens to me on Ubuntu 22.04 LTS with Element installed from the official PPA: element-desktop | 1.11.28 | https://packages.riot.im/debian default/main amd64 Packages. Disabling message indexing mitigates the issue here too.

Ramen-LadyHKG commented 1 year ago

Happens to me on Arch Linux with Element installed from flatpak: 1.11.35 it always crashes when I maximize the window

DE: Plasma-wayland

iyanmv commented 1 year ago

Happens to me on Arch Linux with Element installed from flatpak: 1.11.35 it always crashes when I maximize the window

DE: Plasma-wayland

Use element-desktop from [extra] instead of the community package from flatpak, and remember to add the following flags to your ~/.config/electron25-flags.conf:

--enable-features=WaylandWindowDecorations
--ozone-platform-hint=auto
--enable-webrtc-pipewire-capturer

The crash due to message search was solved in this commit. And most other issues (apart from known element bugs like this one) were solved for me (including the crash when maximizing) after this commit some weeks ago that changed to electron 25. Btw, I also use Plasma with wayland.

lanerussell commented 8 months ago

@t3chguy Thanks for mentioning this issue. It looks like this issue hasn't been updated in 240 days. Are there any solutions to this crashing? Has any additional testing been completed? Perhaps message search should be moved behind a feature flag if it is causing the app to crash?

t3chguy commented 8 months ago

You can disable seshat/message indexing in settings. I've never had this crash and nor have most users hence it not being behind a feature flag. Out of a large number of users there's 35 participants in this issue and no more logs/unique sentry reports than that

kolAflash commented 6 months ago

[...] I've never had this crash and nor have most users hence it not being behind a feature flag. Out of a large number of users there's 35 participants in this issue and no more logs/unique sentry reports than that

Maybe it'll help to ask for the involved libsqlcipher versions to find out where it crashes.

When reporting this crash, please provide your libsqlcipher version!

Debian-12 (current stable): sqlcipher-3.4.1 (known to crash)
Ubuntu-22.04 (Jammy): sqlcipher-3.4.1 (known to crash)
Ubuntu-24.04 (Noble): sqlcipher-4.5.6
openSUSE-Tumbleweed (rolling 2022-12-23): sqlcipher-4.5.3 (package rev-15) (probably known to crash)
openSUSE-Tumbleweed (rolling 2024-02-06): sqlcipher-4.5.6 (package rev-19)
openSUSE-15.5 (current stable): sqlcipher-4.5.3
Arch Linux (rolling): unknown - does someone know how to find the sqlcipher version used by Arch at a certain date? (2022-09-20 known to crash)
flathub.org Flatpak package: probably builtin - does someone know how to get the sqlcipher version in the Flathub package? (known to crash)

sqlcipher upstream:
v4.5.7: Apr 22, 2024
v4.5.6: Jan 16, 2024
v4.5.5: Aug 31, 2023
v4.5.4: Apr 27, 2023
v4.5.3: Dec 19, 2022
v4.5.2: Aug 3, 2022
v4.5.1: Mar 2, 2022
v4.5.0: Oct 21, 2021
v4.4.3: Mar 1, 2021
v4.4.2: Nov 24, 2020
v4.4.1: Nov 6, 2020
v4.4.0: May 11, 2020
v4.3.0: Dec 20, 2019
v4.2.0: May 29, 2019
v4.1.0: Mar 12, 2019
v4.0.1: Dec 17, 2018
v4.0.0: Nov 30, 2018
v3.4.2: Dec 21, 2017
v3.4.1: Dec 28, 2016
v3.4.0: Mar 7, 2016

Note:
When no libsqlcipher is available, Element shows this in the settings menu:
Element is missing some components required for securely caching encrypted messages locally. If you'd like to experiment with this feature, build a custom Element Desktop with search components added.

colans commented 5 months ago

@t3chguy Kindly provide the app version it'll go into? I'm sure I'm not the only one wondering when we can turn search back on (Profile picture -> All settings -> Security and Privacy -> Message Search -> Manage --> Disable) . Thanks!

t3chguy commented 5 months ago

@colans sorry I cannot predict future version numbers. The product team may decide to bump the minor or the patch. The one after 1.11.69

element-hq / element-desktop