[amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window

[Max Loh]

Step to reproduce the bug

1. Have a active/focused window (e.g. terminal)

2. Press the bottom left "Show application" button / try to lock the screen with Win + L shortcut key

After that, Gnome shell crashes.

I have Ubuntu 19.10 with GNOME Shell 3.34.1

[Max Loh (maxloh)]

Here are the error log generated from journalctl -b0

The most recent crash happens at Mar 19 03:30

[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.

[Max Loh (maxloh)]

I ran the command "ubuntu-bug gnome-shell" right after the bug happens.

Here's the log generated: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868035

[Max Loh (maxloh)]

There was actually something like this in error log generated by journalctl -b0

But I can't find these lines in log generated by ubuntu-bug

```
Mar 19 12:23:08 ubuntu-desktop gnome-shell[26624]: JS WARNING: [resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to method Clutter.Actor.destroy: expected 0, got 1
Mar 19 12:23:08 ubuntu-desktop kernel: gnome-shell[26624]: segfault at 61626786 ip 00007feee2b5b0b0 sp 00007fff2fd76a28 error 4 in libgobject-2.0.so.0.6200.1[7feee2b30000+33000]
Mar 19 12:23:08 ubuntu-desktop kernel: Code: fc 03 00 00 77 3c 48 c1 e8 02 48 8d 15 69 32 02 00 48 8b 04 c2 48 81 fe fc 03 00 00 76 31 48 83 e6 fc 45 31 c0 48 85 c0 74 0e <f6> 40 16 04 74 05 48 85 f6 75 35 45 31 c0 44 89 c0 c3 66 0f 1f 44
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: Main process exited, code=killed, status=11/SEGV
Mar 19 12:23:08 ubuntu-desktop polkitd(authority=local)[1214]: Unregistered Authentication Agent for unix-session:13 (system bus name :1.3180, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_HK.UTF-8) (disconnected from bus)
Mar 19 12:23:08 ubuntu-desktop gsd-media-keys[22316]: Couldn't lock screen: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: Failed with result 'signal'.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped target GNOME X11 Session (session: ubuntu).
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopping GNOME X11 Session (session: ubuntu).
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped target GNOME X11 Session.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopping GNOME X11 Session.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped target GNOME Shell on X11.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopping GNOME Shell on X11.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped GNOME Shell on X11.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Starting GNOME Shell on X11...
```

[Max Loh (maxloh)]

The bug may be Ubuntu-specific, as I did not encounter any crash yet in regular gnome session (the gnome-session package)

[Daniel van Vugt (vanvugt)]

Please follow all the steps in comment #4.

[Max Loh (maxloh)]

If I look into /var/crash/ folder, the closest filename match I found is _usr_bin_gnome-shell.1000.crash
Is that the right file to run the command?

When I encounter crash, there was no report dialog, but I saw a thick blank border around windows. Does it means that Gnome didn't crash but just restarts itself?

[Max Loh (maxloh)]

There was nothing related to the crash I encounter in https://errors.ubuntu.com/user/ID.

[Daniel van Vugt (vanvugt)]

Please try:

  apport-cli /var/crash/_usr_bin_gnome-shell.1000.crash

[Max Loh (maxloh)]

Here's the result of apport-cli /var/crash/_usr_bin_gnome-shell.1000.crash

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868046

[Daniel van Vugt (vanvugt)]

Nice, thanks. We can move the discussion to bug 1868046 then.