mirror of
https://github.com/element-hq/element-web
synced 2024-11-24 10:15:43 +03:00
Updated Getting a crash log out of Element Desktop (markdown)
parent
359a7999d6
commit
0116c4a7c0
1 changed files with 15 additions and 0 deletions
|
@ -27,6 +27,21 @@ It depends on your system. The overall idea is
|
|||
- Arch: https://wiki.archlinux.org/title/Core_dump#Examining_a_core_dump
|
||||
- Ubuntu: https://askubuntu.com/questions/966407/where-do-i-find-the-core-dump-in-ubuntu-16-04lts#:~:text=In%20Ubuntu%20the%20core%20dumps,or%20sudo%20service%20apport%20start%20.
|
||||
|
||||
#### Ubuntu 22.04 LTS
|
||||
|
||||
With these instructions you can retrieve the stack trace after a crash. Tested on Ubuntu 22.04 LTS:
|
||||
|
||||
- Search for `electron@` within [`yarn.lock`](https://github.com/vector-im/element-desktop/blob/develop/yarn.lock) in the Element Desktop repo
|
||||
- Note the version, e.g. `version "24.3.1"`
|
||||
- Download the debug build for the same version from [here](https://github.com/electron/electron/releases/)
|
||||
- Extract the contents of `debug` from the archive to `/opt/Element` (or `/opt/Element-Nightly` for the nightly version)
|
||||
- If Element crashes let the system create a crash report
|
||||
- Open a terminal
|
||||
- Go to `/var/crash`
|
||||
- Run `apport-unpack _opt_Element-Nightly_element-desktop-nightly.1000.crash /tmp/elecrash`
|
||||
- `cd /tmp/elecrash`
|
||||
- The stacktrace is located in the `Stacktrace` file there
|
||||
|
||||
#### Debug builds
|
||||
|
||||
On most Linux builds, Element doesn't include debug symbols, which means it's still quite hard to tell what's going on - the crash dump won't contain the names of functions that the program is in, just which libraries are being used.
|
||||
|
|
Loading…
Reference in a new issue