Temporary screen freeze when coming back from screen standby

Bug #1769981 reported by Alberto Donato

This bug report will be marked for expiration in 28 days if no further activity occurs. (find out why)

6
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

When waking up the PC screen from standby, quite often the screen freezes for 10-20s.
I can't move the mouse or type anything. After a while, it unfreezes.
This is quite annoying because often the freeze is long enough to send the screen to standby again for absence of singal, so then I have to wake it up and wait again.

This is not 100% reproducible but happens very frequently, both when the screen is locked and when it's not.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue May 8 20:26:27 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-02-25 (72 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Alberto Donato (ack) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
tags: added: unlock
Revision history for this message
Alberto Donato (ack) wrote :

FTR this also happens on another PC, also with Intel card (different model), also a fresh Bionic install

Revision history for this message
Alberto Donato (ack) wrote :

@Daniel, I just got a session crash because of this freeze and got an Xwayland core file in my home.
Should I open a different bug? How do I attach the core through apport?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If you have a core or crash file then yes please open a new bug, but only by running:

  ubuntu-bug YOURFILE

See also https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

Revision history for this message
Alberto Donato (ack) wrote :

Thanks Daniel,

the core file I got from the crash (in my home dir) shows as

core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -d', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, execfn: '/usr/bin/Xwayland', platform: 'x86_64'

If I try to run "ubuntu-bug core" on it, I get a dialog saying that the problem cannot be reported because the core is about a snap published by Canonical.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That's OK. We can probably ignore most Xwayland crashes anyway. They are mostly just Xwayland dying because gnome-shell crashed...

Do you get any other crash files in /var/crash?

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Alberto Donato (ack) wrote :

Yes I have a Xwayland crash file in /var/crash with the same timestamp.

I tried running ubuntu-bug on it, but after I confirm the popup message, it just exits without any error and it doesn't pop up a launchpad window.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Alberto Donato (ack) wrote :

That link mentions how to create a crash file, but I do have one, I just can't upload it via ubuntu-bug

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It gives you several steps that must be followed first to *fix* the problem with not being able to upload it via ubuntu-bug. Please follow all steps.

Revision history for this message
Alberto Donato (ack) wrote :

@Daniel I followed the steps there (specifically, enabling crashes for X). I just got a freeze with subsequent crash and got a new Xwayland .crash file.
Still, running ubuntu-bug on it it just exits with no error when I click to submit, and it doesn't seem to be submitting the bug.

What steps can I take?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The next step I suggest is to look up automatic crash reports your system has made:

  https://errors.ubuntu.com/user/ID
  where ID is the contents of /var/lib/whoopsie/whoopsie-id

If you find any relevant links there then please share them here.

As a last resort you can also:

  1. Change this bug to Private.
  2. Attach the .crash file to this bug.

but chances we can debug it that way are usually low.

Revision history for this message
Alberto Donato (ack) wrote :

From the list on that page I can see that a report was indeed uploaded for that crash:

2018-05-22 20:05 2018-05-22 18:05 UTC Crash xwayland

Unfortunately if I click on the link, I get an error saying that I'm not allowed to see crash reports. Is it ok for me to share the link to the oops here?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes, links please.

Revision history for this message
Alberto Donato (ack) wrote :
Changed in gnome-shell (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

> https://errors.ubuntu.com/oops/93aef40e-5deb-11e8-945f-fa163e8d4bab (most recent)
> https://errors.ubuntu.com/oops/c9e22fbe-58dc-11e8-9127-fa163ed44aae
> https://errors.ubuntu.com/oops/385a60b4-334f-11e8-a211-fa163ef911dc
are all bug 1731261

> https://errors.ubuntu.com/oops/8fd0adc2-334e-11e8-b7c3-fa163e8d4bab
is bug 1748450 (fixed already, a few weeks after your crash report)

So this seems to be related to bug 1731261. Although we also seem to be missing any indication of what is triggered that for you.

Actually I'm starting to think your freezes are not related to any crashes. It sounds like your freezes are more frequent and less fatal than the above crashes would be.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If you log in remotely from another machine and watch the log:

  journalctl -f

then do you find any messages coincide with the freezes?

Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Alberto Donato (ack) wrote :

No, I've never seen any message in log that could seem related to the issue.

Yes there are two cases here, although related. I experience these freezes when coming out of screen standby, which sometime are longer and end up with a session crash, but in many case they just freeze the UI and send the screen back to dmps standby

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

No messages at all just before or just after the freezes?

How about in the kernel log?; dmesg -w

Revision history for this message
Alberto Donato (ack) wrote :

I only see apparmor audit messages there

Revision history for this message
Alberto Donato (ack) wrote :

Daniel, not sure if they're related, but it seems that when I get back from the "slide" screen (even if not locked) I'm getting a lot of these errors repeated in journalctl:

May 24 14:52:47 kashyyyk gnome-shell[6901]: Object Meta.Background (0x562f8156e590), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: == Stack trace for context 0x562f7ecee330 ==
May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #0 0x7ffe191266b0 b resource:///org/gnome/shell/ui/background.js:718 (0x7f7fbc60f450 @ 22)
May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #1 0x7ffe19127610 b resource:///org/gnome/shell/ui/tweener.js:113 (0x7f7fc81c7e68 @ 37)
May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #2 0x7ffe19128580 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f7fc81d3b38 @ 54)
May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #3 0x7ffe191286d0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f7fc81d3bc0 @ 1626)
May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #4 0x7ffe19128780 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f7fc81d3c48 @ 100)
May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #5 0x7ffe19128810 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f7fc81d3cd0 @ 10)
May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #6 0x7ffe19128900 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f7fc81d3230 @ 386)
May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #7 0x7ffe191289b0 b resource:///org/gnome/shell/ui/tweener.js:245 (0x7f7fc81cf808 @ 159)
May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #8 0x7ffe19128a10 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f7fc81b5de0 @ 71)
May 24 14:52:47 kashyyyk org.gnome.Shell.desktop[6901]: #9 0x7ffe19128ab0 b resource:///org/gnome/shell/ui/tweener.js:220 (0x7f7fc81cf780 @ 15)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

For the default Ubuntu installation I believe we have fixed all the log messages that look like that.

So if you're seeing those I suggest removing some/all of your extensions:

b'org.gnome.shell' b'enabled-extensions' b"['<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'suspend-button@laserb', '<email address hidden>', '<email address hidden>', '<email address hidden>']"

However, all of that might not be related to this bug...

Revision history for this message
Alberto Donato (ack) wrote :

I just had a series of freezes, and managed to ssh and watch logs in the meantime, the only messages that I that might be relevant are the following (repeated many times):

May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed
May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed

Changed in gnome-shell (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Vivek Gani (vivekgani2) wrote :

I've been having an issue similar to this on 22.04 (jammy) and don't recall experiencing it on 21.10. It's actually happened not just from standby but from just being on (with display off) as well. I'm still testing, but it could be extensions like 'blur my shell' causing an issue. Couldn't find anything associated with this in /var/crash or in errors.ubuntu.com for my id.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Vivek,

This is a 4 year old bug reported by someone else on a different Ubuntu version with likely different hardware. Please open your own bug by running:

  ubuntu-bug gnome-shell

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Alberto,

Do you still experience this bug?

Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers