Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)

Bug #1774188 reported by Götz Waschk
210
This bug affects 45 people
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Low
Unassigned
gnome-shell (Ubuntu)
Low
Unassigned
mutter (Ubuntu)
Low
Unassigned
xorg-server (Ubuntu)
Low
Unassigned

Bug Description

This is a fresh installation of 18.04. After entering the password and pressing enter, it takes 5 seconds for the lock screen to disappear. This problem didn't happen on the same machine with 16.04 or 14.04.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 30 15:31:48 2018
InstallationDate: Installed on 2018-05-04 (25 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Götz Waschk (goetz-waschk) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Can you please attach output from 'journalctl -b' covering a time period when the bug occurred?

Changed in gdm3 (Ubuntu):
status: New → Incomplete
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Götz Waschk (goetz-waschk) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. It looks like there is maybe a logical reconnect of the display to the X server at the start around 14:32:29, and that could be triggering a lot of things.

Then problems occur in:
  /<email address hidden>
Can you tell us which app indicator icons are visible after unlocking?

Then gnome-software is running:
  Jun 01 14:32:36 goetz-Latitude-E7250 gnome-software[1784]: no app for changed <email address hidden>
  Jun 01 14:32:37 goetz-Latitude-E7250 gnome-software[1784]: no app for changed <email address hidden>
I don't know why that is or if it is a problem.

Finally, does logging into "Ubuntu on Wayland" avoid the problem?

Revision history for this message
Götz Waschk (goetz-waschk) wrote :

I guess the app indicator icons are the menus in the top-right corner. I have these:
Accessibility
Input Language
Network
Speaker
Battery
The downward triangle that opens the menu

With wayland, the screen unlocking is much faster (about 1s total time).

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

It sounds like most of the issue is confined to Xorg sessions, so reassigning as appropriate.

Changed in gdm3 (Ubuntu):
status: Incomplete → New
Changed in gnome-shell (Ubuntu):
status: Incomplete → New
summary: - unlocking the screen takes 5 seconds
+ Unlocking the screen takes 5 seconds in Xorg sessions (not so much in
+ Wayland sessions)
Changed in gdm3 (Ubuntu):
importance: Undecided → Low
Changed in gnome-shell (Ubuntu):
importance: Undecided → Low
Changed in mutter (Ubuntu):
importance: Undecided → Low
Changed in xorg-server (Ubuntu):
importance: Undecided → Low
tags: added: unlock
Revision history for this message
Götz Waschk (goetz-waschk) wrote :

I think it got slower over time even under the Wayland session. I have clocked the latest unlock time at 2.5 seconds, still rather slow.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gdm3 (Ubuntu):
status: New → Confirmed
Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Changed in mutter (Ubuntu):
status: New → Confirmed
Changed in xorg-server (Ubuntu):
status: New → Confirmed
Revision history for this message
bitinerant (bitinerant) wrote :

I occasionally see this on two separate 18.04 installations using Xorg sessions. The time to unlock varies from a couple of seconds to several minutes. Everything other than unlocking the screen feels to work at a normal speed.

I can reliably reproduce this issue (cause screen unlocking to take several minutes) by reading files from my Android 8 phone over USB (phone in "Use USB to transfer files" mode; Ubuntu directory /run/user/1000/gvfs/mtp:host...). (Probably not related, but this file transfer seems extremely slow.)

See also: https://askubuntu.com/questions/1038723 (5 people experiencing this issue; no solution)

Possibly related: https://askubuntu.com/questions/993984

Revision history for this message
Santiago Gala (sgala) wrote :

/metoo

App indicators visible:
* accessibility
* skype (quitting skype does not make any difference)
* remmina (quitting remmina does not make any difference)
* input languages
* standard "network-volume-battery" one
I used to have the indicator-multiload too, but I removed it due to heavy log spam and unreadable display.

BTW, how can one remove the accessibility or keyboard indicators? I can no longer find where or how to remove them both, as the only functionality I need (switch keyboard layouts) is available via key combo.

Revision history for this message
Carlos Yanez (yanezpena) wrote :

/metoo

>uname -a
Linux ubuntu-W520 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Ricardo Contreras (aztlan2k) wrote :

i'm seeing the same thing. nothing serious but it is annoying that after authenticating you have to wait ~5 secs before getting your desktop.

Is there any way to turn on some debugging to see what's going on during those 5 secs?

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

Maybe turn on debugging in /etc/gdm3/custom.conf, reboot, and then look at the more detailed log from 'journalctl -b0' to see what was happening during that time.

Revision history for this message
Götz Waschk (goetz-waschk) wrote :

I have attached the journal with gdm3 debugging enabled. It starts after waking up the notebook. The screen unlocking was really slow.

Revision history for this message
sokai (sokai) wrote :

FYI: I feel it's (somehow) fixed (for me). I haven't seen this behavior since some days.

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

The log in comment #17 shows the delays are/were specifically here:

Feb 03 21:06:04 goetz-Latitude-E7250 gdm-password][1365]: Process exit status: 0
Feb 03 21:06:36 goetz-Latitude-E7250 wpa_supplicant[845]: wlp2s0: WPA: Group rekeying completed with e0:28:6d:24:15:dd [GTK=CCMP]
Feb 03 21:08:32 goetz-Latitude-E7250 /usr/lib/gdm3/gdm-x-session[1409]: (II) modeset(0): EDID vendor "LGD", prod id 1078

I *think* that means:

Feb 03 21:06:04 User enters password to unlock.
Feb 03 21:06:36 System rejoins wifi network.
Feb 03 21:08:32 Xorg wakes up and redetects the connected monitor.

So the first thing I would try is to disable wifi before sleeping. Does that then make waking up faster?

Revision history for this message
Daniele Besana (WP-OK) (daniele-wpok) wrote :

/metoo

Attached the relevant "journalctl -b" output file.

Is this giving any indication?

mei 12 10:58:22 besa gdm-password][21317]: gkr-pam: unlocked login keyring
mei 12 10:58:23 besa NetworkManager[1034]: <info> [1557651503.3134] agent-manager: req[0x5555d1141cf0, :1.312/org.gnome.Shell.NetworkAgent/1000]: agent registered
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.91/org/ayatana/NotificationItem/chrome_app_indicator_1
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.69/org/ayatana/NotificationItem/Slack1
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.67/org/ayatana/NotificationItem/blueman
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.94/org/ayatana/NotificationItem/software_update_available
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

Thanks

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

Daniele,

Your log looks like a different bug, so please open a new bug for that (after reproducing the bug again) by running:

  ubuntu-bug gnome-shell

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

Götz Waschk,

Please answer the question in comment #19.

Changed in gdm3 (Ubuntu):
status: Confirmed → Incomplete
Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
Changed in mutter (Ubuntu):
status: Confirmed → Incomplete
Changed in xorg-server (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Tom Cook (tom-k-cook) wrote :

I have this same problem on 18.04. It's very noticeable that when my network has no DNS working, screen unlock takes a long time - as much as a minute or two.

I notice this because I often manually configure my network to do DNS lookups over an SSH tunnel. If I just close the lid of my laptop it locks and then goes to sleep, and of course when I open it again the SSH session is down & I have no DNS. In this state, the screen unlock is really slow. If I shut the lid not in this state, screen unlock is quick as normal.

I use an Xorg session.

Revision history for this message
José Manuel Ferrer (jmfo1982) wrote :

It happens to me also. Fresh install of Lubuntu 18.04, fully updated, on an HP Pavilion g6. Whenever the screen is locked (either manually choosing to lock it, or automatically after X amount of time without using it), it will take many seconds just to simply draw the password dialog. But if I switch to the terminal with Ctrl+Alt+F1, then back to the X-Window "terminal", it will draw a text telling me that it will take a few seconds to show me the password dialog ??!! That message then disappears into a black screen, and more than twenty seconds later, finally the password dialog shows up. The laptop was doing nothing, completely idle... this shouldn't happen.

no longer affects: gdm
Revision history for this message
José Manuel Ferrer (jmfo1982) wrote :

Sorry, I think this isn't the proper place for me to report this... because in my case it's not happening with gdm, but with lightdm.

Revision history for this message
Andre Ruiz (andre-ruiz) wrote :

I have seen this on bionic, then on cosmic and now on disco. Type password and it takes 5 to 6 seconds to give you the desktop.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gdm3 (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in mutter (Ubuntu):
status: Incomplete → Expired
Revision history for this message
guus (guus-bloemsma) wrote :

I seem to have the same problem in 19.04. Also it seems to take longer, the longer I'm logged in. Logging out and back in makes it relatively fast again.

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

This bug closed automatically due to no response from the original reporter.

If you still have a problem then please open a new bug by running:

  ubuntu-bug gnome-shell

Revision history for this message
guus (guus-bloemsma) wrote : Re: [Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)

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

Thanks!
Guus C. Bloemsma <http://nl.linkedin.com/in/guusbloemsma>
☎ +31-6-4014-7543
✉ <email address hidden> <email address hidden>

On Thu, Oct 3, 2019 at 3:45 AM Daniel van Vugt <
<email address hidden>> wrote:

> This bug closed automatically due to no response from the original
> reporter.
>
> If you still have a problem then please open a new bug by running:
>
> ubuntu-bug gnome-shell
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1774188
>
> Title:
> Unlocking the screen takes 5 seconds in Xorg sessions (not so much in
> Wayland sessions)
>
> Status in gdm3 package in Ubuntu:
> Expired
> Status in gnome-shell package in Ubuntu:
> Expired
> Status in mutter package in Ubuntu:
> Expired
> Status in xorg-server package in Ubuntu:
> Expired
>
> Bug description:
> This is a fresh installation of 18.04. After entering the password and
> pressing enter, it takes 5 seconds for the lock screen to disappear.
> This problem didn't happen on the same machine with 16.04 or 14.04.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: gdm3 3.28.0-0ubuntu1
> ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
> Uname: Linux 4.15.0-22-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Wed May 30 15:31:48 2018
> InstallationDate: Installed on 2018-05-04 (25 days ago)
> InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> SourcePackage: gdm3
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+subscriptions
>

Revision history for this message
Don Morrison (dfm-m) wrote :

I see this, too, on two different machines (one at home, one at work), both desktops with two monitors. Though for me the delay is usually longer then five seconds. The duration of the delay seems to increase with how long the machine's been up since its last reboot. This was not present when I first installed 18.04 a year ago, but seems to have arisen with some subsequent update.

Revision history for this message
Daniele Besana (WP-OK) (daniele-wpok) wrote :

I just upgraded to Ubuntu 19.10 but nothing changed.
I see the status of the bug is 'expired', is anyone working on this?
Thanks

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

Per comments #32 and #33, this bug is closed because it required specific debugging to be done by the original reporter (which may yield different results for each person). Since no answer was received to comment #19 after 60 days this bug closed automatically.

You may choose to join bug 1847566 instead, or you may choose to open a new bug by running:

  ubuntu-bug gnome-shell

as mentioned in comment #21 :)

Revision history for this message
Lonnie Lee Best (launchpad-startport) wrote :

I recently submitted a bug about this topic for Ubuntu 19.10:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.