riot-desktop does not start on debian 9 (stretch) due to segfault

[cknoll]

Description

After recent update from the package riot-web to riot-desktop I cant start the program.

Steps to reproduce

in a terminal emulator I use the command riot-desktop and get the output:

Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
Seshat unexpected error: Error: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /tmp/.org.chromium.Chromium.Eve6bf)
    at process.func (electron/js2c/asar.js:140:31)
    at process.func [as dlopen] (electron/js2c/asar.js:140:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:1016:18)
    at Object.func (electron/js2c/asar.js:140:31)
    at Object.func [as .node] (electron/js2c/asar.js:149:18)
    at Module.load (internal/modules/cjs/loader.js:816:32)
    at Module._load (internal/modules/cjs/loader.js:728:14)
    at Module._load (electron/js2c/asar.js:717:26)
    at Function.Module._load (electron/js2c/asar.js:717:26)
    at Module.require (internal/modules/cjs/loader.js:853:19)
Starting auto update with base URL: https://packages.riot.im/desktop/update/
Auto update not supported on this platform
Segmentation fault

I would expect the app to start.

Additionally, the same happens if I use riot-desktop --no-update. This seems strange because the the error message seems related to failing autoupdate.

Version information

• Debian GNU/Linux 9 (stretch)
• riot-desktop 1.6.0
• ldd --version gives: ldd (Debian GLIBC 2.24-11+deb9u4) 2.24

Further Information

This issue seems to be related to #7623. There it is suggested to start with a fresh profile. But I dont know where my profile files are stored.

[uhoreg]

The failing autoupdate message is normal. But it may be related to the fact that seshat seems to be expecting glibc >= 2.27, while stretch only has 2.24.

If you want to try with a new profile, your profile is stored in ~/.config/Riot

[dbkr]

Yeah, the docker image we're using to build has glibc 2.27

[cknoll]

If you want to try with a new profile, your profile is stored in ~/.config/Riot

I deleted this directory and tried again: same result with same error message. But at leas a new directory ~/.config/Riot with some files is created.

If it helps I would be available today for a live debug session with voice-chat and screensharing.
topic-specific realtime contact: https://matrix.to/#/!ioMweEZnIFgBvaYGVe:matrix.org?via=matrix.org

#riot-debian9-debugging:matrix.org

[jryans]

Looking across the supported distributions between Ubuntu and Debian, it appears Ubuntu's xenial (16.04 LTS) has the oldest glibc at 2.23.

[jryans]

I'll attempt to craft a custom Docker image that uses Xenial as the base.

[jryans]

@cknoll Could you try installing riot-nightly (you should get version 2020050702 or newer) and checking whether that nightly build works on Stretch? If so, I'll prepare a fixed release build as well.

[t3chguy]

(nightly is affected by the space-in-path issue with electron sandboxing though)

[jryans]

Ah right, I guess you may need to rename /opt/Riot Nightly to not have a space after install... 😭

[cknoll]

just installed riot-nightly and the segfault issue is gone 👍 . However it takes unusually long for syncing (ca. 10min and still going...)

[jryans]

Great to hear the segfault is fixed! I'll proceed with building release the same way then.

However it takes unusually long for syncing (ca. 10min and still going...)

Hmm, okay, that seems unrelated to this issue, but feel free to create a new issue and capture logs to investigate. The initial sync time is highly dependent on account size, server used, etc.

[cknoll]

Finally, syncing finished and the app seems to work fine. Thank you!

[jryans]

1.6.0-2 has now been published which should fix this issue for release as well.

[cknoll]

1.6.0-2 has now been published which should fix this issue for release as well.

I can confirm this on my system.