From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] under VNC, chromium segfaults immediately after starting
Date: Wed, 04 May 2022 04:15:11 +0200 [thread overview]
Message-ID: <20220504021511.GSJ47YagKyL7NQhmLR0Wuvdt2ugBKT_zxw4sq3De8LU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25382@inbox.vuxu.org>
[-- 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.
parent reply other threads:[~2022-05-04 2:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25382@inbox.vuxu.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220504021511.GSJ47YagKyL7NQhmLR0Wuvdt2ugBKT_zxw4sq3De8LU@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).