Many crash (dumped core) after last major update yesterday[gnome]: How to investigate?

Support GNOME
1

Hi everyone
Yesterday everning: major update requested by pacman (almost 1Gb to download). Since I have many crashes. Everything was stable until now.
Can you tell me what I how to investigate ?
Of course, I already did : turning off as many Gnome extentions as possible

10:36:44 systemd-coredum: Process 343182 (gnome-shell) of user 1000 dumped core.
10:34:55 systemd-coredum: Process 332721 (gnome-shell) of user 1000 dumped core.
10:19:16 systemd-coredum: Process 333985 (gjs) of user 1000 dumped core.
10:17:44 systemd-coredum: Process 158504 (gnome-shell) of user 1000 dumped core.
07:50:58 systemd-coredum: Process 218922 (QtWebEngineProc) of user 1000 dumped core.
07:50:57 systemd-coredum: Process 218887 (QtWebEngineProc) of user 1000 dumped core.
00:46:26 systemd-coredum: Process 187355 (com.github.davi) of user 1000 dumped core.
00:25:03 systemd-coredum: Process 156636 (JVM Signal Thre) of user 1000 dumped core
00:23:52 systemd-coredum: Process 975 (gnome-shell) of user 1000 dumped core.
23 mai 23:05:42 systemd-coredum: Process 16322 (com.github.davi) of user 1000 dumped core.

Thanks for suggestions

2

Hi @NicolasMol76, and welcome!

Try inspecting the logs a crash:

journalctl --boot=-1 --priority=3

Where the --boot's parameter of -1 is the last time the problem occurred. So if it happened on the boot just before this one, it’s -1.

This should give you a log of what was happening before the core dump. Which you can share here.

3

Disable all then enable one by one

possible starting points - possibly an extension

Rebuild all your custom packages and extensions

4

I updated my BIOS since, and for 3 days the only process that still persists to crashe & Dump is GJS. The difference however is that it happens in background, I mean without reseting the session and data loss…but I remain worried about this GJS.

Does anyone know or testify something about GJS instability in Gnome 42 ?