Electerm crashes with TRAP on start up

[Lunarequest]

Electerm version:

electerm-1.16.21-linux-x64

Operating system(linux, macos, or windows7/8/10?):

Linux

Expected Behavior

When electerm is started it should work as intended.

Can you reproduce the same behavior in other terminal:

I can reproduce the launching from other treminals on the same system

Current Behavior

it crashes with a TRAP signal and a core dump

Possible Solution

Steps to Reproduce

1.launch electerm
2. electerm crashes

The following is output in a terminal when electerm is started

08:13:49 debug › electerm start
Gtk-Message: 08:13:50.593: Failed to load module "appmenu-gtk-module"
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
useSystemTitleBar false

(electerm:504227): LIBDBUSMENU-GLIB-WARNING **: 08:14:05.661: About to Show called on an item wihtout submenus.  We're ignoring it.

(electerm:504227): LIBDBUSMENU-GLIB-WARNING **: 08:14:05.824: About to Show called on an item wihtout submenus.  We're ignoring it.
08:14:07 info › server runs on 127.0.0.1 30975
08:14:08 info › database version: 1.16.21
[504227:1027/081409.191974:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
[1]    504227 trace trap (core dumped)  ./electerm

[zxdong262]

What kind of Linux?

[Lunarequest]

Fedora kinonite

[zxdong262]

Fedora kinonite

Install from deb? or rpm? or tar.gz? Can you try snap?

[Lunarequest]

I used the tar.gz. i can not use snap as kinonite is an ostree distro

[zxdong262]

I used the tar.gz. i can not use snap as kinonite is an ostree distro

How about the .rpm build?

[Lunarequest]

rpm build also crashes with the same log output

18:43:27 debug › electerm start
Gtk-Message: 18:43:29.192: Failed to load module "appmenu-gtk-module"
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
useSystemTitleBar false
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so

(electerm:5923): LIBDBUSMENU-GLIB-WARNING **: 18:43:30.788: About to Show called on an item wihtout submenus.  We're ignoring it.

(electerm:5923): LIBDBUSMENU-GLIB-WARNING **: 18:43:30.872: About to Show called on an item wihtout submenus.  We're ignoring it.
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
18:43:33 info › server runs on 127.0.0.1 30975
[5923:1027/184334.065205:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
[1]    5923 trace trap (core dumped)  electerm

[zxdong262]

Can you try latest release?

[Lunarequest]

@zxdong262 it gets a bit father but still crashes

19:07:37 debug › electerm start
Gtk-Message: 19:07:40.680: Failed to load module "appmenu-gtk-module"
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
useSystemTitleBar false

(electerm:252401): LIBDBUSMENU-GLIB-WARNING **: 19:07:46.741: About to Show called on an item wihtout submenus.  We're ignoring it.

(electerm:252401): LIBDBUSMENU-GLIB-WARNING **: 19:07:46.832: About to Show called on an item wihtout submenus.  We're ignoring it.
19:07:47 info › server runs on 127.0.0.1 30975
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
19:07:51 info › database version: 1.16.21
19:07:51 info › dbVersion 1.16.21
19:07:51 info › upgrade db version to 1.17.3
19:08:01 debug › ws: connected to terminal -> DwjTcoZy2HCzPM1_UlEf_
[252401:1031/190801.598913:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
[1]    252401 trace trap (core dumped)  ./electerm

[Lunarequest]

This is known issue with electron https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1944468 it's due to glibc incompatibilities and has been fixed in electron 15

[Lunarequest]

updating the electron version fixes the issues

[LordofAgents]

Would like to remember to this issue, it seems to not be resolved yet.