gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch()

[Krystian Kalicki]

https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60

I've been using Ubuntu for almost 2 years and it's been working fine. I use a KVM switch (built in Benq monitor) all the time.
Since last month Ubuntu randomly crashes when I switch back to it.

Or it could be wake up/suspend, I can't see when it exactly happens, it's just logging screen after crash.

I am running: openVPN, firefox (dozen tabs), chrome (ms teams), slack, postman, 3x Intellij IDEA, VS Code

System logs don't show anything meaningful to me or Google and I don't know how to get a clue as to what's going on.

I suspect a new version of MS Teams that was introduced a few weeks ago.
Please help me

I cannot reproduce the crash or find anything on the web about it.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 24 15:59:03 2024
DisplayManager: gdm3
InstallationDate: Installed on 2022-08-31 (601 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
RelatedPackageVersions: mutter-common 42.9-0ubuntu7
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Krystian Kalicki (oh-man-ubuntu)]

Thank you for your support, from the end:
(2.) 3. https://errors.ubuntu.com/oops/473115e4-02d3-11ef-9dc3-fa163ec44ecd
but this is not the last crash. I had 3 more crashes during the day

1. journal,txt (can attach only 1 file)

[Krystian Kalicki (oh-man-ubuntu)]

1. prevjournal.txt

[Krystian Kalicki (oh-man-ubuntu)]

I just had a "crash" and saw how it went.
After switching back with KVM I saw my desktop, but mouse/keyboard didn't work. After 2s it switched to the login screen.

After login all applications were closed, like after reboot.

[Daniel van Vugt (vanvugt)]

Tracking in:
https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60

[Shreyas Jothish (shreyasjothish)]

I am facing similar issue with Ubuntu 22.04 crashing repeatedly with error "gnome-shell crashed with sigsev in wl_event_loop_dispatch"

I have collected information files which are requested above for further analysis.