turt2live
commented
2 years ago This needs more information: what was going on before the crash? When did it start happening?
Closed 5HT2 closed 5 months ago
turt2live
commented
2 years ago This needs more information: what was going on before the crash? When did it start happening?
5HT2
commented
2 years ago Attempting to open element from a fresh install crashed after a few seconds, whether I interacted with the window or not.
marjakm
commented
2 years ago [52:0922/214304.352622:ERROR:broker_posix.cc(40)] Recvmsg error: Connection reset by peer (104)
/app/bin/element: line 10: 3 Trace/breakpoint trap (core dumped)Also happens for me, in probably less than a minute after starting element.
I'm using arch linux and running it via flatpak https://flathub.org/apps/details/im.riot.Riot
Element version: 1.11.5
Olm version: 3.2.12$ 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.5
License: Apache-2.0
Origin: flathub
Collection: org.flathub.Stable
Installation: user
Installed: 290.6 MB
Runtime: org.freedesktop.Platform/x86_64/22.08
Sdk: org.freedesktop.Sdk/x86_64/22.08
Commit: 2848ba4fb48183b7d02ae89d3ea6d5fc078d1424248f97092762ea955fabaa67
Parent: 21ca5fd133f102bbef56dfe78b16969219bad3eded4a6b70d583be8bd5d08acc
Subject: Update element-desktop_1.11.4-1_amd64.deb to 1.11.5 (c829e1e3)
Date: 2022-09-13 22:19:44 +0000I've found that if it doesn't happen in the first few minutes, it stays stable and doesn't happen again until I re-open element.
marjakm
commented
2 years ago I've found that if it doesn't happen in the first few minutes, it stays stable and doesn't happen again until I re-open element.
Can confirm that. Actually it has worked the last 2 times and I haven't updated anything.
nuke-web3
commented
2 years ago Now I get this error over and over on startup before messages load on my client.
vector-im/element-web#22815 is related perhaps?
flatpak run im.riot.Riot -v# normal startup...
#......
Changing application language to en-us
Fetching translation json for locale: en-us
Resetting the UI components after locale change
[54:0929/091413.797476:ERROR:broker_posix.cc(40)] Recvmsg error: Connection reset by peer (104)
[54:0929/091413.798167:ERROR:broker_posix.cc(110)] Error sending sync broker message: Broken pipe (32)
[54:0929/091413.798484:ERROR:broker_posix.cc(110)] Error sending sync broker message: Broken pipe (32)
[53:0929/091007.745135:ERROR:broker_posix.cc(40)] Recvmsg error: Connection reset by peer (104)
/app/bin/element: line 10: 3 Trace/breakpoint trap (core dumped) env TMPDIR="$XDG_RUNTIME_DIR/app/${FLATPAK_ID:-im.riot.Riot}" zypak-wrapper /app/Element/element-desktop $FLAGS "$@"Using flatpack 1.11.18
Did an uninstall & reinstall, same behavior.
On the opening window the logout option was around long enough to select. Logging out and in again at least lets the app be stable for more than a few seconds so far :crossed_fingers: that resolves it. So far it is at least much more stable.
5HT2
commented
2 years ago This is still happening as of 1.11.10-2
electron19 19.1.4-3
electron20-bin 20.3.4-1
element-desktop 1.11.10-2
element-web 1.11.10-2
t3chguy
commented
2 years ago @5HT2 1.11.10 isn't latest, 1.11.14 is.
5HT2
commented
2 years ago It looks like the community package for element-desktop isn't updated but I can try the git version.
t3chguy
commented
2 years ago This bug seems to not yet have been reproduced on the official builds so is likely specific to the community package and needs to be fixed there
5HT2
commented
2 years ago Is it possible it's to do with the electron version that's being used @t3chguy? Which one are you using?
t3chguy
commented
2 years ago 5HT2
commented
2 years ago ~ ❯ electron20 -v
v20.3.4
~ ❯ which element-desktop
/usr/bin/element-desktop
~ ❯ cat /usr/bin/element-desktop
#!/bin/sh
exec electron20 /usr/lib/element/app.asar --disable-dev-mode "$@"
prototact
commented
1 year ago On fedora 37 and element-desktop installed through flatpak crashes for me too. I am using Wayland.
[3 zypak-helper] Wait found events, but sd-event found none
/home/<username>/.var/app/im.riot.Riot/config/Element exists: yes
/home/<username>/.var/app/im.riot.Riot/config/Riot exists: no
LaunchProcess: failed to execvp:
xdg-settings
Gtk-Message: 13:03:59.201: Failed to load module "canberra-gtk-module"
Gtk-Message: 13:03:59.201: Failed to load module "pk-gtk-module"
Gtk-Message: 13:03:59.202: Failed to load module "canberra-gtk-module"
Gtk-Message: 13:03:59.202: Failed to load module "pk-gtk-module"
[3:1211/130359.216754:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:1211/130359.216789:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
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 en-us
Fetching translation json for locale: en-us
Resetting the UI components after locale change
Resetting the UI components after locale change
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
Changing application language to en-us
Fetching translation json for locale: en-us
Resetting the UI components after locale change
[50:1211/130411.537512:ERROR:broker_posix.cc(40)] Recvmsg error: Connection reset by peer (104)
/app/bin/element: line 10: 3 Trace/breakpoint trap (core dumped) env TMPDIR="$XDG_RUNTIME_DIR/app/${FLATPAK_ID:-im.riot.Riot}" zypak-wrapper /app/Element/element-desktop $FLAGS "$@"
lcomrade
commented
1 year ago Flatpak 1.12.7, X11, Debian 11, Element 1.11.16:
leonidm@thinkpad:~$ flatpak run im.riot.Riot
/home/leonidm/.var/app/im.riot.Riot/config/Element exists: yes
/home/leonidm/.var/app/im.riot.Riot/config/Riot exists: no
LaunchProcess: failed to execvp:
xdg-settings
Gtk-Message: 18:53:51.825: Failed to load module "canberra-gtk-module"
Gtk-Message: 18:53:51.827: Failed to load module "canberra-gtk-module"
[3:1211/185351.869503:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:1211/185351.869597:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
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 en-us
Fetching translation json for locale: en-us
Resetting the UI components after locale change
Resetting the UI components after locale change
libva error: /usr/lib/x86_64-linux-gnu/dri/intel-vaapi-driver/iHD_drv_video.so init failed
Changing application language to en-us
Fetching translation json for locale: en-us
Resetting the UI components after locale change
/app/bin/element: line 10: 3 Trace/breakpoint trap env TMPDIR="$XDG_RUNTIME_DIR/app/${FLATPAK_ID:-im.riot.Riot}" zypak-wrapper /app/Element/element-desktop $FLAGS "$@"
leonidm@thinkpad:~$ 
martijnkruiten
commented
1 year ago For me removing ~/.var/app/im.riot.Riot/ was enough to fix the issue, which is essentially the same as what @NukeManDan did. Of course don't do this, unless you've got a backup of your encryption keys or have access to another verified session. I've not checked if just removing the cache is enough to fix the issue.
schildbach
commented
1 year ago Here is my version of the crash, on 1.11.16:
$ flatpak run im.riot.Riot
/home/aschildbach/.var/app/im.riot.Riot/config/Element exists: yes
/home/aschildbach/.var/app/im.riot.Riot/config/Riot exists: no
LaunchProcess: failed to execvp:
xdg-settings
Gtk-Message: 16:44:07.514: Failed to load module "canberra-gtk-module"
Gtk-Message: 16:44:07.515: Failed to load module "canberra-gtk-module"
[3:1214/164407.525563:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:1214/164407.525587:ERROR:bus.cc(399)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
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 en-us
Fetching translation json for locale: en-us
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
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
/app/bin/element: line 10: 3 Trace/breakpoint trap env TMPDIR="$XDG_RUNTIME_DIR/app/${FLATPAK_ID:-im.riot.Riot}" zypak-wrapper /app/Element/element-desktop $FLAGS "$@"It looks like running yay -R element-desktop and then yay -S element-desktop.. fixed the issue..? I'm so confused as to what could be going on here, because when I reported this issue it was on a fresh install on a new computer.
schildbach
commented
1 year ago "Clear caches and reload" did not fix this issue for me.
5HT2
commented
1 year ago Which ones did you clear? I didn't have to clear any caches manually, I just re-installed it from my package manager.
schildbach
commented
1 year ago Which ones did you clear? I didn't have to clear any caches manually, I just re-installed it from my package manager.
The one from the settings of the app itself.
xz-dev
commented
1 year ago When I enable "message search", it will been crash as title say, if I try disable it before the crash, it will not crash. Also I have a very bad network. So, it seems like something about network connect.
5HT2
commented
1 year ago Message search requires some lib installed locally iirc
yajo
commented
1 year ago I just got the same problem after restablishing search index. Fedora 37, flathub package. Core dumped:
Like aforementioned, disabling local encrypted messages search index disables the crash. But I need searches! 😢
weeman1337
commented
1 year ago Happened for me on start up. Nightly 2022122201 on 2022122201 installed via official deb repo
weeman1337
commented
1 year ago Removing unsupported platform, because installed from official deb repo.
e00E
commented
1 year ago I experience this issue on an up to date Arch system with the Arch package. Same error as described in OP. For me it happens within 5 seconds on startup before the windows shows anything.
e00E
commented
1 year ago On an existing profile I get the same error as OP with broker_posix.cc. On a fresh profile I get
ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -3followed by segfaulting.
e00E
commented
1 year ago On my system this was fixed by unsetting --ozone-platform-hint=wayland in my electron config. I use this setting to make electron use wayland. This is likely an electron + wayland issue instead of an Element issue.
Note that Arch recently switched to electron22 which likely caused the issue to appear.
freswa
commented
1 year ago Note that Arch recently switched to electron22 which likely caused the issue to appear.
I disagree. Downgrading the element-web package to 1.11.16 solves the issue. So the culprit is probably somewhere in this repo.
e00E
commented
1 year ago I'm not familiar with electron development but it seems unlikely that an electron app could do something that makes it crash only on wayland, without this being a bug in electron. I expect the app code to not know about low level details like the graphics environment. Maybe a recent change in element exercises the electron bug but it's still an electron bug. Although element might still want to work around the bug in that case. And it would be good to isolate it and forward it to electron.
noantiq
commented
1 year ago I experienced this crash throughout the last few days since I installed Element 1.11.17 as a flatpak on Fedora 37. Element usually crashes within a couple of seconds to minutes when I run it and often looses the whole session. Obviously very annoying.
turt2live
commented
1 year ago Please note that community platforms are not supported in this issue tracker - please report them upstream. We'll be investigating this from the Debian angle most likely.
poperigby
commented
1 year ago @turt2live Is Flatpak counted as a community platform?
turt2live
commented
1 year ago Yes, the flatpak is maintained by a community member: https://github.com/flathub/im.riot.Riot/
5HT2
commented
1 year ago This is likely an electron + wayland issue instead of an Element issue.
As the person who reported the issue, I don't use Wayland period.
Operating System: Arch Linux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.8
Kernel Version: 6.1.3-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i7-8665U CPU @ 1.90GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20QD000LUS
System Version: ThinkPad X1 Carbon 7thI experience this issue on an up to date Arch system with the Arch package. Same error as described in OP. For me it happens within 5 seconds on startup before the windows shows anything.
Can you try this like I did earlier? https://github.com/vector-im/element-desktop/issues/648
5HT2
commented
1 year ago @e00E ping for the above comment
e00E
commented
1 year ago I do not have yay. Reinstalling the package through pacman does not fix the issue. Completely deleting my element profile folder does not fix the issue.
As the person who reported the issue, I don't use Wayland period.
Then we might be experiencing different bugs.
5HT2
commented
1 year ago I'm no longer able to reproduce this issue after reinstalling the package (I'm also using Arch), so I am unfortunately not sure what's wrong here.
partizanna
commented
1 year ago /home/partizan/.config/Element exists: yes
/home/partizan/.config/Riot exists: no
(electron:118340): Gtk-WARNING **: 14:09:07.359: Theme parsing error: gtk.css:63:28: The :prelight pseudo-class is deprecated. Use :hover instead.
(electron:118340): Gtk-WARNING **: 14:09:07.359: Theme parsing error: gtk.css:73:35: The :prelight pseudo-class is deprecated. Use :hover instead.
No update_base_url is defined: auto update is disabled
Fetching translation json for locale: en_EN
Changing application language to en-us
Fetching translation json for locale: en-us
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
Trace/breakpoint trapI still have this random crash, even with no interaction at all. Its also on Archlinux with version 1.11.17-1 and electron22. On previous version of electron and element everything was fine. I also tried to remove the config dir and setup a new.
kernel: traps: electron[118340] trap int3 ip:55e6ea890a6e sp:7ffc59e876b0 error:0 in electron[55e6e726a000+7267000]
This is the only thing in journal logs
makew0rld
commented
1 year ago I am also seeing this fixed (for now anyway) after uninstalling and reinstalling electron-desktop on Arch Linux.
harmathy
commented
1 year ago Reinstalling the package on Arch Linux does not fix the problem. It goes away when the message search index for encrypted rooms is completed. By disabling and re-enabling the message search I can reproduce this issue reliably.
SpiritCroc
commented
1 year ago I started getting this kind of crash frequently with a self-built element fork (SchildiChat) on Arch linux, I think since the 1.11.17 merge. A week ago, I downgraded electron in element-desktop/package.json from version 22 back to 21, and it hasn't crashed anymore since then. So at least for me, looks like something broke with electron 22. From my experiments on my machine, it didn't relate to message search this time, but rather what happens when the client loses focus? Not sure. Using wayland/sway.
popcorn9499
commented
1 year ago I have found two different packages on arch both I believe use older electron versions. The arch package for element-desktop version 1.11.15-1 with the corresponding element-web version seem to function properly without crashes and with search enabled. Also the element-desktop-nightly-bin package seems to work properly.
Had issues on both kde plasma x11 and kde plasma wayland.
damnms
commented
1 year ago same here on opensuse tumbleweed. i open it, start typing and after 5-10 seconds its just gone. this happens now over a week.
Orhideous
commented
1 year ago So, as far as I can see, it's not uncommon.
5HT2
commented
1 year ago Is anybody in this thread on non-Arch able to try uninstalling the package, clearing all related caches and package caches, and reinstalling?
Doing yay -R element-desktop; yay -S element-desktop worked on Arch for me.
poperigby
commented
1 year ago I cleared the data of the Flatpak version and reinstalled it, and it's still happening.
ghost
commented
1 year ago Similar experience with the Flatpak on Void glibc with KDE Plasma, but my output is the following:
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 en-us
Fetching translation json for locale: en-us
Resetting the UI components after locale change
[47:0214/101025.004099:ERROR:gpu_init.cc(523)] Passthrough is not supported, GL is egl, ANGLE is
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
Error getting the event index passphrase out of the secret store [Error: user interaction failed]
/app/bin/element: line 16: 3 Trace/breakpoint trap env TMPDIR="$XDG_RUNTIME_DIR/app/${FLATPAK_ID:-im.riot.Riot}" zypak-wrapper /app/Element/element-desktop $FLAGS "$@"
Steps to reproduce
Outcome
What did you expect?
No crash.
What happened instead?
Crash
Operating system
Arch Linux
Application version
element-desktop 1.11.4-1How 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