element-web: Element-desktop won't launch on Ubuntu 21.10 (testing)

Steps to reproduce

  1. I installed the app with these commands on Ubuntu 21.10:
sudo apt install -y wget apt-transport-https

sudo wget -O /usr/share/keyrings/riot-im-archive-keyring.gpg https://packages.riot.im/debian/riot-im-archive-keyring.gpg

echo "deb [signed-by=/usr/share/keyrings/riot-im-archive-keyring.gpg] https://packages.riot.im/debian/ default main" | sudo tee /etc/apt/sources.list.d/riot-im.list

sudo apt update

sudo apt install element-desktop

  1. The app won’t launch at all.

What happened?

What did you expect?

nothing much

What happened?

wowpetr@lpau:~$ element-desktop
/home/wowpetr/.config/Element exists: no
/home/wowpetr/.config/Riot exists: no
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
Resetting the UI components after locale change
[5025:0926/023736.697713:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)

Operating system

Ubuntu 21.10

Application version

1.8.5

How did you install the app?

From your repositories (APT)

Homeserver

No response

Have you submitted a rageshake?

No

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 15 (8 by maintainers)

Most upvoted comments

Well, on element-nightly 2021093001 everything seems to be working.

If you have setup our repo already, hopefully you can do apt install element-nightly

yes, I can and I will

Back-trace:

warning: Can't open file /dev/shm/.org.chromium.Chromium.w7v8w2 (deleted) during file-backed mapping note processing
[New LWP 1]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/opt/Element/element-desktop --type=rendere'.
Program terminated with signal SIGSYS, Bad system call.
#0  clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:62
62	../sysdeps/unix/sysv/linux/x86_64/clone3.S: No such file or directory.
(gdb) bt
#0  clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:62
#1  0x00007f9e97d88561 in __GI___clone_internal (cl_args=cl_args@entry=0x7ffcd02bf9d0, func=func@entry=0x7f9e97cf76b0 <start_thread>, arg=arg@entry=0x7f9e954c6640) at ../sysdeps/unix/sysv/linux/clone-internal.c:54
#2  0x00007f9e97cf75b5 in create_thread (pd=pd@entry=0x7f9e954c6640, attr=attr@entry=0x7ffcd02bfd40, stopped_start=stopped_start@entry=0x7ffcd02bface, stackaddr=stackaddr@entry=0x7f9e94cc6000, stacksize=<optimized out>, thread_ran=thread_ran@entry=0x7ffcd02bfacf)
    at pthread_create.c:294
#3  0x00007f9e97cf7fb6 in __pthread_create_2_1 (newthread=<optimized out>, attr=<optimized out>, start_routine=<optimized out>, arg=<optimized out>) at pthread_create.c:785
#4  0x000055683e127bbb in ?? ()
#5  0x0000311bdaec4be0 in ?? ()
#6  0x00007f9e954c6640 in ?? ()
#7  0x0000311bdad61c80 in ?? ()
#8  0x00007ffcd02bfc28 in ?? ()
#9  0x00007ffcd02bfc70 in ?? ()
#10 0x000055683ba522f7 in ?? ()
#11 0x0000000000000000 in ?? ()

Valgrind output: https://drive.google.com/file/d/1A3y3nWaSx7uF3ZK2S-f_Q97HHe-NxAZg/view?usp=sharing

P.S. the app version was updated to 1.9.0 via apt