Electron Apps Crashing

Problem

Well, like the title says all of my electron apps are crashing when opening them.

Background

I don’t think i have done anything wrong although i did a fresh eos install a few days ago and when i was programming in vscode suddenly it crashed and all other electron apps and chromium browsers started crashing too.

I thought it was some kind of huge bug and it would be updated on a day or two but days have passed and haven’t seen anyone with my problem.

Attempts To Fix

  • Open the apps in x11 (though stremio actually opens on x11 but not other apps like vscode)
  • Tested on both Hyprland and Gnome
  • Use LTS Kernel
  • Downgrade Nvidia Drivers

Logs

This is the output from the command journalctl | grep electron

nov 09 22:14:23 lighttigerxiv-eos dev.vencord.Vesktop.desktop[17566]:     at t.readdirSync (node:electron/js2c/node_init:2:13773)
nov 09 22:41:43 lighttigerxiv-eos sudo[5200]: lighttigerxiv : TTY=pts/0 ; PWD=/home/lighttigerxiv ; USER=root ; COMMAND=/usr/bin/pacman -S --config /etc/pacman.conf -- extra/electron
nov 09 22:42:01 lighttigerxiv-eos sudo[5250]: lighttigerxiv : TTY=pts/0 ; PWD=/home/lighttigerxiv ; USER=root ; COMMAND=/usr/bin/pacman -D -q --asexplicit --config /etc/pacman.conf -- electron
nov 09 22:47:07 lighttigerxiv-eos dev.vencord.Vesktop.desktop[3229]: [3:1109/224707.173198:FATAL:electron_browser_main_parts.cc(503)] Failed to shutdown.
nov 09 22:54:27 lighttigerxiv-eos com.visualstudio.code.desktop[5263]: Warning: 'ms-enable-electron-run-as-node' is not in the list of known options, but still passed to Electron/Chromium.
nov 10 13:55:48 lighttigerxiv-eos dev.vencord.Vesktop.desktop[7421]: [3:1110/135548.163675:FATAL:electron_browser_main_parts.cc(503)] Failed to shutdown.

From the command nvidia-smi

Sun Nov 10 14:44:33 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 565.57.01              Driver Version: 565.57.01      CUDA Version: 12.7     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3060 ...    Off |   00000000:01:00.0  On |                  N/A |
| N/A   48C    P5             20W /   80W |    1746MiB /   6144MiB |     24%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

TLDR;

If you need more logs i can provide them too. Can someone help me with this? :pray:

Welcome back @lighttigerXIV :wave: :sunglasses: :enos_flag:

Could you also share system specs please:

inxi -Fxxc0z | eos-sendlog

Would you note any stability issues with anything else, such as web browsing?

Are you overclocking?

Thanks XD

Here you go

In regards to web browsing i didn’t experience any issue since i am using firefox normally. But when testing i used brave browser and it was crashing too.
This is the crash log messages on brave:

[25555:25555:1110/221436.097712:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSa                                                                                      ver: org.freedesktop.DBus.Error.UnknownMethod: Unknown method GetActive or interface org.freedesktop.ScreenSaver.
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

fish: Job 1, 'brave' terminated by signal SIGSEGV (Address boundary error)

Nope. I never felt the need to overclock my pc.

And sorry for only replying an hour later. Email notifications take some time to show up.

Is this a behaviour with Brave something you’re able to replicate under X11?

I just wonder if what you’ve noted about X11, might actually be pointing to two different issues.

On x11 it has the same problem. It keeps being open on start but as soon as i click the window it crashes. The same with vscode and so one.

Also i am not sure since i can’t remember but when i was installing some packages and installed nwg-look, vscode crashed a few minutes after. Maybe some of the dependencies needs a downgrade or something.

If you turn off “Use graphics acceleration when available” in Brave (Settings > System) and re-launch Brave, does the issue persist?

I can’t open brave to change settings XD.
Is there a flag that does that?

1 Like

Try running:

/usr/bin/brave --disable-gpu

Crashes the same

1 Like

Running from command line, did that give you any useful output?

I will have to check that tomorrow but i am pretty sure it was the same. I will have to dedicate tomorrow in trying to fix this

A simple thing to try, is creating a new user, log in with that and test the problem applications there. If the issue isn’t there, it may be a user specific configuration setting.

1 Like

You are right :open_mouth: . I created a new user for testing and brave didn’t crash.
These are the configs i have in my normal user (the ones with @ are symlinks because i use stow):

❯ ls -a
 ./               EOS-greeter.conf   .gsd-keyboard.settings-ported   mako@           pavucontrol.ini   TabNine/             whiskers-launcher-bookmarks/
 ../              evolution/         gtk-3.0/                        mimeapps.list   pulse/            user-dirs.dirs       xdg-terminals.list
 autostart/       fish@              gtk-4.0/                        monitors.xml    qBittorrent/      user-dirs.locale     xsettingsd/
 BraveSoftware/   gnome-session/     hypr@                           monitors.xml~   spicetify@        waybar@              yay/
 Code/            goa-1.0/           Hyprland-xdg-terminals.list     nautilus/       starship@         wezterm@            'YouTube Music'/
 dconf/           Google/            ibus/                           nwg-look/       systemd/          whiskers-launcher@   zed@

And these are the ones from the new user.

❯ ls -a
./   BraveSoftware/  dconf/            evolution/      goa-1.0/                       gtk-3.0/  ibus/      pulse/          user-dirs.locale
../  Code/           EOS-greeter.conf  gnome-session/  .gsd-keyboard.settings-ported  hypr/     nautilus/  user-dirs.dirs

Any idea which one might be making the apps crash?

So i copied my .config to a pendrive then on my actual user copy and pasted those configs. After a reboot electron apps are working again. I think it’s probably a dconf setting making them crash.

The lesson i learned from this is never use Gnome again . Always breaks some stupid thing because of theming. I will just go back at using sddm as my login screen and only use gnome apps but not gnome itself.

Proof it’s working XD

1 Like

Great news, well done @lighttigerXIV :slightly_smiling_face: :enos_flag:

1 Like

Forgot to say thank you XD. That new user trick helped a lot.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.