You are not logged in.
Chromium (or ungoogled chromium) will fail to start, crashing a couple of seconds after launching.
Upon application startup it displays an error page reporting a SIGILL error. Starting from terminal I get:
[3115:3115:0509/180927.034497:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
zsh: segmentation fault (core dumped) chromiumsteps I already tried
chrome --disable-gpu
rm -rf $HOME/.cache/chromium rm -rf $HOME/.config/chromium rm $HOME/.config/chromium-flags.conf chromium --disable-gpu --disable-software-rasterizerSome info about my system:
chromium --versionChromium 90.0.4430.93 Arch Linuxuname -r5.10.35-1-ltspacman -Q | grep mesamesa 21.1.0-1pacman -Q | grep video xf86-video-intel 1:2.99.917+916+g31486f40-1
xf86-video-vesa 2.5.0-1coredump output for chromium:
PID: 875 (chromium)
UID: 1000 (al)
GID: 985 (users)
Signal: 11 (SEGV)
Timestamp: Sun 2021-05-09 15:18:57 EEST (3h 16min ago)
Command Line: /usr/lib/chromium/chromium
Executable: /usr/lib/chromium/chromium
Control Group: /user.slice/user-1000.slice/session-1.scope
Unit: session-1.scope
Slice: user-1000.slice
Session: 1
Owner UID: 1000 (al)
Boot ID: a3cbb5b648484cc8bc23b1d9e0b3e783
Machine ID: 9edb49ca60444e7f88f907eec3020707
Hostname: arch
Storage: /var/lib/systemd/coredump/core.chromium.1000.a3cbb5b648484cc8bc23b1d9e0b3e783.875.1>
Disk Size: 7.2M
Message: Process 875 (chromium) of user 1000 dumped core.
Stack trace of thread 932:
#0 0x00007f8be22f7161 realpath_stk (libc.so.6 + 0x4a161)
#1 0x00007f8be22f7876 realpath@@GLIBC_2.3 (libc.so.6 + 0x4a876)
#2 0x0000555ddf3bd826 n/a (chromium + 0x5207826)
#3 0x0000555de0044ad3 n/a (chromium + 0x5e8ead3)
#4 0x0000555de0045055 n/a (chromium + 0x5e8f055)
#5 0x0000555de0045055 n/a (chromium + 0x5e8f055)
#6 0x0000555de0045055 n/a (chromium + 0x5e8f055)
#7 0x0000555de0045055 n/a (chromium + 0x5e8f055)
#8 0x0000555de0045055 n/a (chromium + 0x5e8f055)
#9 0x0000555de0045055 n/a (chromium + 0x5e8f055)
#10 0x0000555de0045055 n/a (chromium + 0x5e8f055)
#11 0x0000555de0045055 n/a (chromium + 0x5e8f055)
#12 0x0000555de0045055 n/a (chromium + 0x5e8f055)
#13 0x0000555de0045055 n/a (chromium + 0x5e8f055)
#14 0x0000555de0045055 n/a (chromium + 0x5e8f055)
#15 0x0000555de0045055 n/a (chromium + 0x5e8f055)for vscodium
PID: 1059 (codium)
UID: 1000 (al)
GID: 985 (users)
Signal: 11 (SEGV)
Timestamp: Sun 2021-05-09 18:30:18 EEST (9min ago)
Command Line: /usr/share/vscodium-bin/codium --no-sandbox --unity-launch --no-sandbox
Executable: /usr/share/vscodium-bin/codium
Control Group: /user.slice/user-1000.slice/session-1.scope
Unit: session-1.scope
Slice: user-1000.slice
Session: 1
Owner UID: 1000 (al)
Boot ID: ff5dfbcfd0e643e2a718c6850ced5f67
Machine ID: 9edb49ca60444e7f88f907eec3020707
Hostname: arch
Storage: /var/lib/systemd/coredump/core.codium.1000.ff5dfbcfd0e643e2a718c6850ced5f67.1059.16>
Disk Size: 8.7M
Message: Process 1059 (codium) of user 1000 dumped core.
Stack trace of thread 1128:
#0 0x00007f6d66e4e161 realpath_stk (libc.so.6 + 0x4a161)
#1 0x00007f6d66e4e876 realpath@@GLIBC_2.3 (libc.so.6 + 0x4a876)
#2 0x000055d339626822 n/a (codium + 0x3fca822)
#3 0x000055d33a209dc0 n/a (codium + 0x4baddc0)
#4 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)
#5 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)
#6 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)
#7 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)
#8 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)
#9 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)
#10 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)
#11 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)
#12 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)
#13 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)
#14 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)
#15 0x000055d33a20a3cd n/a (codium + 0x4bae3cd)edit:
problem was caused from manually applying a cursor theme
solution was found in this thread
Last edited by Herbalist (2021-05-09 19:35:47)
Offline