Computer locks even when Screen Lock off

Bug #1789095 reported by John Rose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
New
Undecided
Unassigned
gnome-shell (Ubuntu)
New
Undecided
Unassigned
xorg-server (Ubuntu)
New
Undecided
Unassigned

Bug Description

Computer locks after a few minutes even when Automatic Screen Lock turned off. I've also tried Screen Lock after e.g. 30 minutes. This happens on both a new install of 18.04 (on this computer) or after an upgrade from 16.04 to 18.04 on another computer.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 26 13:43:57 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.15.0-32-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
InstallationDate: Installed on 2018-07-30 (26 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=e504ff2a-eea2-4b23-9877-f078e8762eab ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2018
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745
dmi.board.name: NUC5CPYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H61145-404
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

When you say "locks", does that mean you can unlock it with a password?

You're not talking about a permanent crash, right?

affects: xorg (Ubuntu) → xorg-server (Ubuntu)
Changed in gdm3 (Ubuntu):
status: New → Incomplete
Changed in xorg-server (Ubuntu):
status: New → Incomplete
Revision history for this message
John Rose (johnaaronrose) wrote :

It's not a crash or a hang. It locks in terms of the screen being blank and the login password being required to unlock the screen. Also, I put this glitch down to the xorg package but I could be wrong.

Changed in gdm3 (Ubuntu):
status: Incomplete → New
Changed in xorg-server (Ubuntu):
status: Incomplete → New
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.