Re: [ISSUE] [CLOSED] under VNC, chromium segfaults immediately after starting

Re: [ISSUE] [CLOSED] under VNC, chromium segfaults immediately after starting

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

Closed issue by thamesynne on void-packages repository

https://github.com/void-linux/void-packages/issues/25382

Description:
### System

* xuname:  
  Void 5.7.14_1 x86_64-musl GenuineIntel uptodate rFF
* package:  
  chromium 85.0.4183.121_1
  tigervnc-1.10.1_3

### Expected behavior
chromium starts

### Actual behavior
$ chromium
Received signal 11 SEGV_MAPERR 000000000004
  r8: 000055b7c81ab570  r9: 0000000000000075 r10: 000055b7c81ab768 r11: 0000000000000000
 r12: 000055b7c81b7f68 r13: 000055b7c818bd00 r14: 000055b7c7d80400 r15: 000055b7c7d94dc0
  di: 00007ffee81dfb70  si: 00007f7df9320a40  bp: 00007ffee81dfe70  bx: 00007ffee81dfb70
  dx: 0000000000000001  ax: 0000000000000000  cx: 00000000000001c8  sp: 00007ffee81df870
  ip: 000055b7c3888a30 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000004
[end of stack trace]
Calling _exit(1). Core file will not be generated.
$ 

### Steps to reproduce the behavior
sudo xbps-install chromium
chromium

### Additional information
This happens with or without a profile, or a .config/chromium directory. It happens as root, or as a standard user. It happens more or less instantly (although after the check for root / --no-sandbox). It's fine on a normal X window, but doesn't work at all under TigerVNC's VNC server.