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

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 https://github.com/vector-im/riot-web/issues/7623. There it is suggested to start with a fresh profile. But I dont know where my profile files are stored.

[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.

[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.