Login screen hangs

Bug #1866219 reported by Gaurav Kumar
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

One the screen is locked the user is unable to get the login screen. Though the user can see the windows of applications opened in the background but can not activaely interact with them. However the random keys pressed during this issue can be seen once user logs in by following the below steps:

1. Let the lockscrren tp display.
2. Click on the icon on the bottom-right corner of the lockscreen.
3. Get the log in window and enter password to log in.
4. User is now logged in and is out of the issue.

* lsb_release -rd:
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04

* Software Center version: 3.35.91

* What you expected to happen: User when locks the system and tries to log in back then the user should get a log in window and untill user logs in the background application windows should not be visible and user cannot interact with them without logging in successfully.

* What happened instead: User when logs out and tries to log in again, the application windows are visible opened in the background instead getting a login screen. If user press random keys on the visible application windows during system lock it seems that nothing happens but once user successfully logs in, the random keystrokes can be seen on the application window in background. The issue goes after following the below steps:
1. Let the lockscrren tp display.
2. Click on the icon on the bottom-right corner of the lockscreen.
3. Get the log in window and enter password to log in.
4. User is now logged in and is out of the issue.

Attachment of issue is attached, the black screen in video end is of screen where user gets login prompt after clicking on the icon on the bottom-right corner of the lockscreen.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 5 23:02:36 2020
DistUpgraded: 2020-02-04 22:40:17,211 DEBUG inhibit gnome-session idle
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1921] (rev 0a) (prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 520 [17aa:39f2]
InstallationDate: Installed on 2019-12-14 (82 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp.
 Bus 001 Device 003: ID 5986:0711 Acer, Inc EasyCamera
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80S7
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=9e20a847-bcac-4f7f-ae59-60a69ec18299 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to focal on 2020-02-04 (30 days ago)
dmi.bios.date: 06/19/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0VCN31WW(V1.15)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 510-14ISK
dmi.modalias: dmi:bvnLENOVO:bvr0VCN31WW(V1.15):bd06/19/2018:svnLENOVO:pn80S7:pvrLenovoYOGA510-14ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct31:cvrLenovoYOGA510-14ISK:
dmi.product.family: YOGA 510-14ISK
dmi.product.name: 80S7
dmi.product.sku: LENOVO_MT_80S7_BU_idea_FM_YOGA 510-14ISK
dmi.product.version: Lenovo YOGA 510-14ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-12-14 (83 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal
Uname: Linux 5.4.0-14-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-02-04 (30 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Gaurav Kumar (gauravkt7) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote :
information type: Private Security → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Can you please run this command (again)?

  apport-collect 1866219

It should give us more relevant information now the bug is assigned to gnome-shell.

affects: ubuntu → gnome-shell (Ubuntu)
Revision history for this message
Gaurav Kumar (gauravkt7) wrote :

@vanvugt I have ran the suggested command on my Ubuntu machine. Please let me know how may I help you in collecting more details regarding the stated issue.

Thanks

tags: added: apport-collected
description: updated
Revision history for this message
Gaurav Kumar (gauravkt7) wrote : Dependencies.txt

apport information

Revision history for this message
Gaurav Kumar (gauravkt7) wrote : GsettingsChanges.txt

apport information

Revision history for this message
Gaurav Kumar (gauravkt7) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Gaurav Kumar (gauravkt7) wrote : ProcEnviron.txt

apport information

Revision history for this message
Gaurav Kumar (gauravkt7) wrote : ShellJournal.txt

apport information

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

Please start by uninstalling these extensions:

b'org.gnome.shell' b'enabled-extensions' b"['<email address hidden>', '<email address hidden>', 'cpufreq@konkor', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'Internet-Speed-Meter@TH3L0N3C0D3R']"

We need to check if removing them makes a difference because so often gnome-shell bugs (and the login screen is gnome-shell) are caused by extensions. And we need to uninstall them and not just disable them because a buggy extension can still interfere even when disabled.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Gaurav Kumar (gauravkt7) wrote :

@vanvugt I appreciate your help. I did removed all the extensions and disabled the animation. However this did not helped to mitigate the issue.

I found a tweak to mitigate the issue on bug#1866256 (@ernstp) by again enabling the animation again which resolved the issue.

Thanks

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1866044, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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

Other bug subscribers

Remote bug watches

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