*** This bug is a duplicate of bug 1800352 ***
https://bugs.launchpad.net/bugs/1800352
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 1800352, 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.
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** This bug has been marked a duplicate of bug 1800352
screen lock leaves desktop and current applications displayed unless
activated twice
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1806194
Title:
Lock screen / Screensaver doesn't work in Ubuntu 18.10
Status in gdm3 package in Ubuntu:
New
Status in gnome-shell package in Ubuntu:
New
Bug description:
In Gnome, when I hit "Super-L" my screen freezes but the image remains
intact instead of taking me to a login screen.
Further, I can still access the application dock and start
applications (though I cannot see the apps or interact with them) and
I can interact with the top activities bar.
Maybe it's useful, maybe not, but I'm using X11 not Wayland due to an issue
with my NVidia card.
$ gnome-screensaver-command --lock
** (gnome-screensaver-command:22849): WARNING **: 10:37:00.517: unable to
send message: Timeout was reached
** Message: 10:37:00.517: Did not receive a reply from the screensaver.
$ vi /var/log/syslog
Dec 1 10:36:31 hostname dbus-daemon[1488]: [session uid=123 pid=1488]
Reloaded configuration
Dec 1 10:36:31 hostname dbus-daemon[2445]: [session uid=1000 pid=2445]
Reloaded configuration
Dec 1 10:36:31 hostname dbus-daemon[1488]: [session uid=123 pid=1488]
Reloaded configuration
Dec 1 10:36:31 hostname dbus-daemon[2445]: [session uid=1000 pid=2445]
Reloaded configuration
Dec 1 10:36:31 hostname dbus-daemon[1488]: [session uid=123 pid=1488]
Reloaded configuration
Dec 1 10:36:31 hostname dbus-daemon[2445]: [session uid=1000 pid=2445]
Reloaded configuration
Dec 1 10:36:35 hostname gnome-shell[2614]: pushModal: invocation of
begin_modal failed
Dec 1 10:36:35 hostname gnome-shell[2614]:
../../../../gobject/gsignal.c:2641: instance '0x556570a1cbb0' has no handler
with id '143890'
Dec 1 10:36:35 hostname gnome-shell[2614]:
../../../../gobject/gsignal.c:2641: instance '0x556570a1cbb0' has no handler
with id '143891'
Dec 1 10:36:35 hostname gnome-shell[2614]: Object Meta.WindowActor
(0x556573104440), has been already deallocated — impossible to access it. This
might be caused by the object having been destroyed from C code using something
such as destroy(), dispose(), or remove() vfuncs.
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: == Stack trace for
context 0x55656e024200 ==
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #0 7ffe9ff3c590 b
resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f6fa3ecc040 @ 25)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #1 5565960b1138 i
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416
(7f6fa068aca0 @ 20)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #2 7ffe9ff3d700 b
self-hosted:261 (7f6fa3ec1dc0 @ 223)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #3 5565960b1080 i
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415
(7f6fa068ac10 @ 172)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #4 7ffe9ff3e810 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #5 5565960b1000 i
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424
(7f6fa068ad30 @ 17)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #6 7ffe9ff3f780 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #7 5565960b0f80 i
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89
(7f6fa068a430 @ 42)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #8 7ffe9ff406f0 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #9 5565960b0ef8 i
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456
(7f6fa067f280 @ 82)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #10 7ffe9ff41660 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #11 5565960b0e60 i
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784
(7f6fa0684670 @ 116)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #12 7ffe9ff425d0 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #13 5565960b0de0 i
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903
(7f6fa0684a60 @ 37)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #14 7ffe9ff43540 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #15 5565960b0d60 i
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31
(7f6fa06759d0 @ 12)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #16 5565960b0ca0 i
resource:///org/gnome/shell/ui/extensionSystem.js:83 (7f6fa3a5a040 @ 436)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #17 5565960b0c20 i
resource:///org/gnome/shell/ui/extensionSystem.js:354 (7f6fa3a5ab80 @ 13)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #18 7ffe9ff446b0 b
self-hosted:261 (7f6fa3ec1dc0 @ 223)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #19 5565960b0ba0 i
resource:///org/gnome/shell/ui/extensionSystem.js:353 (7f6fa3a5aaf0 @ 64)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #20 5565960b0b20 i
resource:///org/gnome/shell/ui/extensionSystem.js:371 (7f6fa3a5ac10 @ 87)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #21 7ffe9ff457f0 b
resource:///org/gnome/gjs/modules/signals.js:128 (7f6fa3ec18b0 @ 386)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #22 7ffe9ff46410 b
resource:///org/gnome/shell/ui/sessionMode.js:208 (7f6fa3841ca0 @ 254)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #23 7ffe9ff47090 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #24 5565960b09e0 i
resource:///org/gnome/shell/ui/sessionMode.js:170 (7f6fa3841a60 @ 40)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #25 7ffe9ff48010 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #26 5565960b0938 i
resource:///org/gnome/shell/ui/screenShield.js:1282 (7f6fa38289d0 @ 188)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #27 7ffe9ff48f90 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #28 5565960b0888 i
resource:///org/gnome/shell/ui/screenShield.js:1331 (7f6fa3828a60 @ 391)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #29 7ffe9ff49f10 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #30 5565960b0800 i
resource:///org/gnome/shell/ui/shellDBus.js:371 (7f6fa3831d30 @ 67)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #31 7ffe9ff4ae90 b
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6fa3eb0b80 @ 71)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #32 5565960b0738 i
resource:///org/gnome/gjs/modules/overrides/Gio.js:295 (7f6fa3ebd5e0 @ 604)
Dec 1 10:36:35 hostname org.gnome.Shell.desktop[2614]: #33 5565960b0690 i
resource:///org/gnome/gjs/modules/overrides/Gio.js:326 (7f6fa3ebd820 @ 34)
I also saw the message "Screen lock is locked down, not locking" but
that appears to be at hibernation/sleep rather than lock.
I also saw this AskUbuntu page, but they didn't give an indication
that they'd posted a formal bug:
https://askubuntu.com/questions/1082761/automatic-locking-screen-
doesnt-work-in-ubuntu-18-10
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05
PDT 2018
GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 1 11:01:35 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA
controller])
Subsystem: Dell HD Graphics 530 [1028:06b7]
NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00
[VGA controller])
Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097]
InstallationDate: Installed on 2018-11-16 (14 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
MachineType: Dell Inc. Precision Tower 3620
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic
root=UUID=de881e3f-27b8-44b5-9e72-86a1d5b774b0 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.3.5
dmi.board.name: 09WH54
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.3.5:bd08/06/2017:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.family: Precision
dmi.product.name: Precision Tower 3620
dmi.product.sku: 06B7
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1806194/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
