Chromium Based Apps Crashing | Arch Linux Community | Page 1

tough cloak Mar 9, 2026, 9:46 PM

#

I am hoping this is not indicative of a memory issue considering how expensive RAM is atm... But every Chromium based app I have had issues with crashing. Steam will randomly close the main window and reopen, I get a Signal 5 (TRAP) crash every time I open Vesktop up (even though it works just fine), and I have experience a few crashes with Chromium while using it. I can't find anyone else with the same issue so I am starting to think maybe it is a hardware issue... empty Any idea of something else being the issue?

#

Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
           PID: 7237 (ThreadPoolForeg)
           UID: 1000 (Retalak)
           GID: 1000 (Retalak)
        Signal: 5 (TRAP)
     Timestamp: Mon 2026-03-09 17:13:45 EDT (22min ago)
  Command Line: /usr/lib/vesktop/vesktop
    Executable: /usr/lib/vesktop/vesktop
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.chromium.Chromium-7149.scope
          Unit: user@1000.service
     User Unit: app-org.chromium.Chromium-7149.scope
         Slice: user-1000.slice
     Owner UID: 1000 (Retalak)
       Boot ID: 8ec3ca9a4bf645e0ae6b48307d6b8097
    Machine ID: 37866a49f4ee4b799a305015357d2211
      Hostname: ARCH2025
       Storage: /var/lib/systemd/coredump/core.ThreadPoolForeg.1000.8ec3ca9a4bf645e0ae6b48307d6b8097.7237.1773090825000000.zst (present)
  Size on Disk: 5.7M
       Message: Process 7237 (ThreadPoolForeg) of user 1000 dumped core.

#

APPIMAGE env is not defined, current application is not an AppImage
Vesktop v1.6.5
Disabled Chromium features: WinRetrieveSuggestionsOnlyOnDemand, HardwareMediaKeyHandling, MediaSessionService
[6961:0309/171337.294922:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.systemd1.Manager.StartTransientUnit: object_path= /org/freedesktop/systemd1: org.freedesktop.systemd1.UnitExists: Unit app-org.chromium.Chromium-6961.scope was already loaded or has a fragment file.
[7000:0309/171337.415584:ERROR:media/gpu/vaapi/vaapi_wrapper.cc:1627] vaInitialize failed: unknown libva error
[6961:0309/171337.509462:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:296] Unable to set image transfer function.
[6961:0309/171337.509477:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:214] Failed to populate image description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}
[6961:0309/171337.597687:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:296] Unable to set image transfer function.
[6961:0309/171337.597703:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:214] Failed to populate image description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}
[6961:0309/171337.597712:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_management_surface.cc:63] Failed to get image description for color space.

atomic summit Mar 9, 2026, 10:01 PM

#

looks like graphics issues

#

what wm are you on

#

and when was the last time you updated

tough cloak Mar 10, 2026, 12:52 AM

#

atomic summit what wm are you on

Kwin

#

I also just ran memtest86+ for 3 passes no errors. So I dont think its memory.

#

It happens every time I open vesktop consistently so if there were a memory issue I imagine I would have gotten an error in 3 passes

tough cloak Mar 10, 2026, 12:54 AM

#

atomic summit and when was the last time you updated

Yesterday, it has been happening for about a month or so through multiple updates

broken briar Mar 11, 2026, 12:38 AM

#

run chromium or vesktop with --disable-gpu

#

@tough cloak

#

If they launch we know its gpu drivers

#

very unlikely to be memory if its a chromium specific issue

tough cloak Mar 11, 2026, 12:39 AM

#

broken briar run chromium or vesktop with --disable-gpu

Same crash empty

broken briar Mar 11, 2026, 12:39 AM

#

try --ozone-platform=x11

#

and when you get a chance run pacman -Qs mesa for me aswell and send the output here

#

@tough cloak

tough cloak Mar 11, 2026, 12:42 AM

#

broken briar try --ozone-platform=x11

Same crash

tough cloak Mar 11, 2026, 12:42 AM

#

broken briar try --ozone-platform=x11

local/glu 9.0.3-3
    Mesa OpenGL utility library
local/lib32-mesa 1:26.0.1-1
    Open-source OpenGL drivers - 32-bit
local/mesa 1:26.0.1-1
    Open-source OpenGL drivers
local/mesa-utils 9.0.0-7
    Essential Mesa utilities

broken briar Mar 11, 2026, 12:45 AM

#

are you open to trying propriety drivers?

tough cloak Mar 11, 2026, 12:47 AM

#

broken briar are you open to trying propriety drivers?

Proprietary opengl drivers? Sure why not - is that an aur package? Id give it a try to narrow it down but wouldnt want to keep aur package drivers long term

broken briar Mar 11, 2026, 12:48 AM

#

nvidia drivers

sudo pacman -R nvidia-open
sudo pacman -S nvidia

tough cloak Mar 11, 2026, 12:48 AM

#

oh okay yea lemme try

broken briar Mar 11, 2026, 12:48 AM

#

then reboot see if it makes a difference

tough cloak Mar 11, 2026, 12:50 AM

#

broken briar then reboot see if it makes a difference

Nvidia package no longer available

#

Open is the official linux drivers from nvidia now no?

#

Also surely --disable-gpu would root out graphics related issues?

broken briar Mar 11, 2026, 12:52 AM

#

you said its only chromium based apps?

tough cloak Mar 11, 2026, 12:53 AM

#

Yea, chromium, steam, vesktop is what I have had troubles with

#

Vesktop crashes on startup every time but works anyways. Steam and Chromium crash randomly during use

broken briar Mar 11, 2026, 12:54 AM

#

unsure tbh

#

dont think its memory

tough cloak Mar 11, 2026, 12:54 AM

#

Yea ive been stumped

#

Thats what made me think it was hardware because its so obscure and I cant find anyone else with the same issue

broken briar Mar 11, 2026, 12:55 AM

#

tough cloak Thats what made me think it was hardware because its so obscure and I cant find ...

run pacman -Qs libva

#

send output

tough cloak Mar 11, 2026, 12:56 AM

#

broken briar run pacman -Qs libva

local/lib32-libva 2.22.0-1
    Video Acceleration (VA) API for Linux (32-bit)
local/lib32-mesa 1:26.0.1-1
    Open-source OpenGL drivers - 32-bit
local/libva 2.22.0-1
    Video Acceleration (VA) API for Linux
local/mesa 1:26.0.1-1
    Open-source OpenGL drivers

broken briar Mar 11, 2026, 12:57 AM

#

try pacman -S libva-nvidia-driver

tough cloak Mar 11, 2026, 12:58 AM

#

broken briar try pacman -S libva-nvidia-driver

Same crash

broken briar Mar 11, 2026, 12:58 AM

#

yeah no clue then only said that due to vaInitialize failed: unknown libva error

tough cloak Mar 11, 2026, 1:03 AM

#

broken briar yeah no clue then only said that due to vaInitialize failed: unknown libva error

That did get rid of those errors but apparently were unrelated to the crash

APPIMAGE env is not defined, current application is not an AppImage
Vesktop v1.6.5
Disabled Chromium features: WinRetrieveSuggestionsOnlyOnDemand, HardwareMediaKeyHandling, MediaSessionService
[7469:0310/210302.127088:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.systemd1.Manager.StartTransientUnit: object_path= /org/freedesktop/systemd1: org.freedesktop.systemd1.UnitExists: Unit app-org.chromium.Chromium-7469.scope was already loaded or has a fragment file.

#

I have also tried deleting chromium and vesktop config folders in ~/.config

broken briar Mar 11, 2026, 1:09 AM

#

tough cloak That did get rid of those errors but apparently were unrelated to the crash ``` ...

one last thing run printenv | grep -S -e libva -e nvidia and send output

tough cloak Mar 11, 2026, 1:12 AM

#

broken briar one last thing run ```printenv | grep -S -e libva -e nvidia``` and send output

There is nothing in there with libva or nvidia

broken briar Mar 11, 2026, 1:24 AM

#

tough cloak There is nothing in there with libva or nvidia

journalctl -xe | grep -e vesktop -e chromium

#

send output

tough cloak Mar 11, 2026, 1:26 AM

#

broken briar journalctl -xe | grep -e vesktop -e chromium

📎 message.txt

#

This basically just repeats so didnt include all of it

broken briar Mar 11, 2026, 1:28 AM

#

close vesktop fully then run
LIBVA_DRIVER_NAME=nvidia vesktop

#

still same crash?

tough cloak Mar 11, 2026, 1:30 AM

#

broken briar still same crash?

Yea haha

[Retalak@ARCH2025 ~]$ LIBVA_DRIVER_NAME=nvidia vesktop
APPIMAGE env is not defined, current application is not an AppImage
Vesktop v1.6.5
Disabled Chromium features: WinRetrieveSuggestionsOnlyOnDemand, HardwareMediaKeyHandling, MediaSessionService
[20789:0310/212909.727707:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.systemd1.Manager.StartTransientUnit: object_path= /org/freedesktop/systemd1: org.freedesktop.systemd1.UnitExists: Unit app-org.chromium.Chromium-20789.scope was already loaded or has a fragment file.

broken briar Mar 11, 2026, 1:30 AM

#

gg

#

certain its something with gpu idk im probably not smart enough to figure it out

tough cloak Mar 11, 2026, 1:31 AM

#

Its weird because vesktop works without interruption. Its a minor annoyance that I get the crash notification every time I open vesktop. But Steam and Chromium actually quit in the middle of using them so I really want to figure out why lol

broken briar Mar 11, 2026, 1:32 AM

#

i looked it up same stuff comes up on forums about the vaapi but I have no clue what the fix for it is

tough cloak Mar 11, 2026, 1:33 AM

#

Its all good, I appreciate having another person to think on it. Ive been racking my brain for like a month on and off trying to figure out why

broken briar Mar 11, 2026, 1:33 AM

#

just out of intrest can you send a screenshot or the output of

nvidia-smi

tough cloak Mar 11, 2026, 1:34 AM

#

broken briar just out of intrest can you send a screenshot or the output of nvidia-smi

#

I did have to RMA my card in 2023... They sent the same card back so Im not sure what they did to it

#

They did nothing I guess

Process Result: Product test ok, no trouble found.

tough cloak Mar 11, 2026, 2:14 AM

#

https://github.com/electron/electron/issues/49806

GitHub

Global shortcuts failing on Wayland - regression in 40.x · Issue #...

Preflight Checklist I have read the Contributing Guidelines for this project. I agree to follow the Code of Conduct that this project adheres to. I have searched the issue tracker for a bug report ...

#

I wonder if perhaps my vesktop issue is this?

tough cloak Mar 11, 2026, 2:34 AM

#

There seems to be a lot of other people complaining about the same error for vesktop in their discord. Wonder if it is a bug in vesktop that is also causing issues with other chromium based apps

tough cloak Mar 11, 2026, 2:35 AM

#

tough cloak https://github.com/electron/electron/issues/49806

Cause I don't think it is this, from what I see vesktop is on electron 39 still

#Chromium Based Apps Crashing