FS#76308 - [chromium] crashes on start

Attached to Project: Arch Linux
Opened by Mel (Mel) - Thursday, 27 October 2022, 03:50 GMT
Last edited by Toolybird (Toolybird) - Thursday, 27 October 2022, 22:27 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I get unresponsive chromium window as soon as I open it. It closes few seconds after it's been launched. When launching it from the terminal it outputs Segmentation fault (core dumped).
I've installed the chromium debug symbols and attempted to run chromium inside gdb to obtain the trace. Result is attached to this bug report though I'm not sure how useful it will be. I'm also attaching the result of coredumpctl gdb which seems to capture a more complete trace.

I typically use firefox, so this is a complete clean-slate chromium, no user configuration was ever done to it. I'm running stock arch linux kernel 6.0.5.arch1-1 and stock Mesa from repo, version 22.2.2-1. I'm running xfce4.
System is a ryzen 5600x with rx6700 xt card and 32 gb ram.

To add to this, I've attempted to run google-chrome from AUR and it's segfaults shortly after launch too.

Additional info:
* package version(s) 107.0.5304.68-1 (also happens with chromium 106.0.5249.119-2)
* config and/or log files etc. trace.log, coredumpctl.log
* link to upstream bug report, if any

Steps to reproduce:
launch chromium, observe it crash
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 27 October 2022, 22:27 GMT
Reason for closing:  Works for me
Comment by Mel (Mel) - Thursday, 27 October 2022, 03:51 GMT
Log files as listed above

EDIT: For posterity, I found the reason for the segfaults. Cursor theme doesn't include all pointers chromium based browsers require. Log an error message or a warning? Nah, best just segfault. Thanks chromium.
Comment by Toolybird (Toolybird) - Thursday, 27 October 2022, 22:27 GMT
chromium works fine. Folks would be all over this if it were a widespread issue. There must be something special about your system triggering the crash. The logs don't shed much light unfortunately. Please visit the proper support channels (forum/IRC/etc) to seek help in debugging the problem. Feel free to request re-open if an Arch packaging bug is identified.

Loading...