Lock screen not working

Bug #1877746 reported by Byron
260
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

The screen will not automatically lock on the specified timer.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:09:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020
 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May 9 08:54:58 2020
DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-29-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe]
InstallationDate: Installed on 2018-07-01 (678 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-28 (11 days ago)
dmi.bios.date: 11/27/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F50
dmi.board.asset.tag: Default string
dmi.board.name: X470 AORUS ULTRA GAMING-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X470 AORUS ULTRA GAMING
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Byron (byron-goodman) wrote :
information type: Private Security → Public Security
affects: xorg (Ubuntu) → gnome-shell (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please run these commands and send us the output:

  gsettings list-recursively org.gnome.desktop.session

  gsettings list-recursively org.gnome.desktop.lockdown

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Byron (byron-goodman) wrote :

org.gnome.desktop.session session-name 'ubuntu'
org.gnome.desktop.session idle-delay uint32 900

org.gnome.desktop.lockdown mount-removable-storage-devices-as-read-only false
org.gnome.desktop.lockdown disable-command-line false
org.gnome.desktop.lockdown disable-log-out false
org.gnome.desktop.lockdown disable-printing false
org.gnome.desktop.lockdown disable-lock-screen false
org.gnome.desktop.lockdown disable-print-setup false
org.gnome.desktop.lockdown disable-user-switching false
org.gnome.desktop.lockdown disable-application-handlers false
org.gnome.desktop.lockdown disable-save-to-disk false
org.gnome.desktop.lockdown user-administration-disabled false

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

Thanks. That's not the problem...

Maybe some app is inhibiting the lock screen. Is it any different if you select 'Ubuntu on Wayland' from the login screen?

Revision history for this message
Byron (byron-goodman) wrote :

Wayland won't launch.

Revision history for this message
Byron (byron-goodman) wrote :
Download full text (5.1 KiB)

No crash files for Wayland.

May 12 16:21:46 apollo systemd[2574]: Starting GNOME Shell on Wayland...
May 12 16:21:46 apollo rtkit-daemon[2201]: Successfully made thread 3777373 of process 3777373 owned by '1000' high priority at nice level -11.
May 12 16:21:46 apollo rtkit-daemon[2201]: Supervising 4 threads of 2 processes of 2 users.
May 12 16:21:46 apollo rtkit-daemon[2201]: Supervising 4 threads of 2 processes of 2 users.
May 12 16:21:46 apollo rtkit-daemon[2201]: Successfully made thread 3777422 of process 3777373 owned by '1000' RT at priority 5.
May 12 16:21:46 apollo rtkit-daemon[2201]: Supervising 5 threads of 2 processes of 2 users.
May 12 16:21:46 apollo gnome-shell[3777410]: Failed to open gpu '/dev/dri/card0': Failed to activate universal planes: Operation not permitted
May 12 16:21:46 apollo gnome-shell[3777410]: Failed to create backend: No GPUs found
May 12 16:21:46 apollo systemd[2574]: Started Sound Service.
May 12 16:21:46 apollo systemd[2574]: gnome-shell-wayland.service: Failed with result 'protocol'.
May 12 16:21:46 apollo systemd[2574]: Failed to start GNOME Shell on Wayland.
May 12 16:21:46 apollo systemd[2574]: Dependency failed for GNOME Shell on Wayland.
May 12 16:21:46 apollo systemd[2574]: Dependency failed for GNOME Wayland Session.
May 12 16:21:46 apollo systemd[2574]: Dependency failed for GNOME Wayland Session (session: ubuntu).
May 12 16:21:46 apollo systemd[2574]: <email address hidden>: Job <email address hidden>/start failed with result 'dependency'.
May 12 16:21:46 apollo systemd[2574]: gnome-session-wayland.target: Job gnome-session-wayland.target/start failed with result 'dependency'.
May 12 16:21:46 apollo systemd[2574]: gnome-shell-wayland.target: Job gnome-shell-wayland.target/start failed with result 'dependency'.
May 12 16:21:46 apollo systemd[2574]: gnome-shell-wayland.service: Triggering OnFailure= dependencies.
May 12 16:21:46 apollo systemd[2574]: unicast-local-avahi.path: Succeeded.
May 12 16:21:46 apollo systemd[2574]: Stopped Path trigger for Avahi .local domain notifications.
May 12 16:21:46 apollo systemd[2574]: update-notifier-release.path: Succeeded.
May 12 16:21:46 apollo systemd[2574]: Stopped Path trigger for new release of Ubuntu notifications.
May 12 16:21:46 apollo systemd[2574]: Condition check resulted in Disable GNOME Shell extensions after failure being skipped.
May 12 16:21:46 apollo systemd[2574]: Stopped target GNOME Session Manager is ready.
May 12 16:21:46 apollo systemd[2574]: Stopping GNOME Session Manager (session: ubuntu)...
May 12 16:21:46 apollo systemd[2574]: <email address hidden>: Succeeded.
May 12 16:21:46 apollo systemd[2574]: Stopped GNOME Session Manager (session: ubuntu).
May 12 16:21:46 apollo systemd[2574]: Stopped target Tasks to be run before GNOME Session starts.
May 12 16:21:46 apollo systemd[2574]: Stopped target Session services which should run early before the graphical session is brought up.
May 12 16:21:46 apollo systemd[2574]: Reached target Shutdown running GNOME Session.
May 12 16:21:46 apollo systemd[2574]: Stopping Start gnome-keyring as SSH agent...
May 12 16:21:46 apollo systemd[2574]: Stopping Moni...

Read more...

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

Please try disabling Bluetooth and/or other peripherals. Does that allow the lock screen to work?

I'm reminded of bug 1823076.

Revision history for this message
Byron (byron-goodman) wrote :

No, but I did do a dconf -f, and that at least lets me do it manually now. It will not lock automatically.

Of course, it reset everything, which as introduced others problems.

Question, what call is exposed to applications to get to determine DPI?

I am having scaling issues in Maple 2017.3 and Maple 2020. If I use Gnome (default) it works fine.

I am unable to get Wayland up.

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

DPI is toolkit-specific and I won't go further into that because it is off-topic. Please open a separate bug for that.

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

In comment #7 I meant please disable Bluetooth, Wifi, and unplug all USB devices. Does that allow the system to sleep? If so then please reintroduce them individually to find out which is the problem.

Revision history for this message
Byron (byron-goodman) wrote :

Done, didn't fix it.

Changed in gnome-shell (Ubuntu):
status: Incomplete → New
tags: added: lock lock-screen
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I've seen a few comments from people finding that their gnome-shell process crashes when it tries to lock the screen. And that means the screen never locks. So please follow these instructions:

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

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
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
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

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