gnome-shell always crash after boot

[Per-Inge]

gnome-shell always crash after boot with an UnreportableReason. This is in a Wayland session.
There are no stability issues after boot.

I get this information in the terminal after the command ubuntu-bug

p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell
p-i@pi-asus-b450f-gaming:~$ [8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id
[8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1 times!

ERROR:gl goes from 1 to 19.

In Settings the Display is named Microstep 27"
The problem might be hardware related:
Mobo: ASUSTeK model: ROG STRIX B450-F GAMING
GPU: AMD Navi 10 Radeon RX 5700

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.34.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 11 16:43:08 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-02-08 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200207.2)
RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
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. 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.

2. If step 1 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.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

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.

[Daniel van Vugt (vanvugt)]

It sounds like the main issue is that Xwayland has crashed first:

[ 31.095070] pi-asus-b450f-gaming gnome-shell[1400]: Connection to xwayland lost

Please follow the steps in comment #2 to help us diagnose the problem further.

[Per-Inge (per-inge-hallin)]

This is the result:

Error reports sent from this system
Occurred Received Problem Type Program
2020-02-11 19:02 2020-02-11 18:02 UTC Crash gnome-shell
2020-02-11 06:02 2020-02-11 05:02 UTC Crash gnome-shell
2020-02-10 11:02 2020-02-10 11:02 UTC Crash gnome-shell
2020-02-09 12:02 2020-02-09 12:02 UTC Crash gnome-shell
2020-02-08 09:02 2020-02-08 08:02 UTC Crash gnome-shell
2020-02-03 17:02 2020-02-03 16:02 UTC Crash /usr/lib/xorg/Xorg
2020-02-03 07:02 2020-02-03 07:02 UTC Crash /usr/lib/xorg/Xorg
2020-01-24 15:01 2020-01-24 14:01 UTC Crash google-chrome-stable
2020-01-17 21:01 2020-01-17 20:01 UTC Crash gnome-shell
2020-01-13 18:01 2020-01-13 17:01 UTC Crash cups-browsed
2019-12-30 21:12 2019-12-30 20:12 UTC Crash google-chrome-stable
2019-12-27 19:12 2019-12-27 18:12 UTC Crash google-chrome-stable
2019-12-27 12:12 2019-12-27 13:12 UTC Crash cups-browsed

These are the links:
https://errors.ubuntu.com/oops/31013d32-4cfd-11ea-a96b-fa163e983629
https://errors.ubuntu.com/oops/8269e776-4c91-11ea-a07a-fa163e6cac46
https://errors.ubuntu.com/oops/e4e4e6ec-4bfa-11ea-a95c-fa163e983629
https://errors.ubuntu.com/oops/5f9cd9b2-4b3b-11ea-a957-fa163e983629
https://errors.ubuntu.com/oops/650b32dc-4a4e-11ea-a953-fa163e983629
https://errors.ubuntu.com/oops/234b0822-46a3-11ea-aa47-fa163e6cac46
https://errors.ubuntu.com/oops/b2bebda8-4655-11ea-b902-fa163e102db1
https://errors.ubuntu.com/oops/65f83450-3eb8-11ea-a7c8-fa163ee63de6
https://errors.ubuntu.com/oops/a46d4394-3966-11ea-b219-fa163e983629
https://errors.ubuntu.com/oops/cb2e2fc2-3626-11ea-b89d-fa163e102db1
https://errors.ubuntu.com/oops/e2494484-2b44-11ea-a75f-fa163ee63de6
https://errors.ubuntu.com/oops/b45882ec-28d8-11ea-b84d-fa163e102db1
https://errors.ubuntu.com/oops/70a7627c-28b0-11ea-b1c1-fa163e983629

Den ons 12 feb. 2020 kl 03:20 skrev Daniel van Vugt <
<email address hidden>>:

> It sounds like the main issue is that Xwayland has crashed first:
>
> [ 31.095070] pi-asus-b450f-gaming gnome-shell[1400]: Connection to
> xwayland lost
>
> Please follow the steps in comment #2 to help us diagnose the problem
> further.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1862792
>
> Title:
> gnome-shell always crash after boot
>
> Status in gnome-shell package in Ubuntu:
> Incomplete
>
> Bug description:
> gnome-shell always crash after boot with an UnreportableReason. This is
> in a Wayland session.
> There are no stability issues after boot.
>
> I get this information in the terminal after the command ubuntu-bug
>
> p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell
> p-i@pi-asus-b450f-gaming:~$
> [8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID
> data: manufacturer id
> [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)]
> InitializeSandbox() called with multiple threads in process gpu-process.
>
> [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)]
> GetVSyncParametersIfAvailable() failed for 1 times!
>
> ERROR:gl goes from 1 to 19.
>
> In Settings the Display is named Microstep 27"
> The problem might be hardware related:
> Mobo: ASUSTeK mode...

[Daniel van Vugt (vanvugt)]

Thanks, but unfortunately none of those are usable, for a variety of reasons. Obviously we should ignore the crashes in google-chrome-stable and cups-browsed here since this bug report is about gnome-shell crashing. But the gnome-shell crashes are not usable for reasons like:

---

Invalid core dump: BFD: warning: /tmp/apport_core_getbxb5s is truncated: expected core file size >= 1186811904, found: 249229312

---

You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs:

usb-modeswitch

---

Please keep collecting crash reports as one of them should eventually be useful. Please also try uninstalling these:

'<email address hidden>',
'<email address hidden>',
'<email address hidden>',
'<email address hidden>'

We need extensions to be uninstalled because we find a large number of bugs are caused by extensions. And just disabling a buggy extension is not enough to stop it from interfering.

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]