session logout after suspend

Bug #1753884 reported by Simon
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Only when I have a second monitor plugged in, if I close the lid of my laptop, my session gets logged out. What I'm expecting is the lock screen comes up.

Sometimes (but not always) the second monitor will flash the "logged out" screen for a second or two before going dim.

I have "Suspend even if external monitor is plugged in" enabled in Tweak Tools.

WORKAROUND: Suspend via the GUI with the lid open.

WORKAROUND: Unplug the second monitor before closing the lid.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue Mar 6 18:07:50 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
InstallationDate: Installed on 2018-02-15 (19 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: LENOVO 20AQ009HUS
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=6f20d80f-81f4-40c1-aafd-95b2c5de55ed ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET78WW (2.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQ009HUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ009HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ009HUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440s
dmi.product.name: 20AQ009HUS
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
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

Revision history for this message
Simon (simsamsom) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Simon, thank you for reporting this and helping make Ubuntu better.

1) To clarify, if you keep the lid open, and suspend via the GUI, is your session logged out after resume from suspend?

2) After the session logout, are there crash files in /var/crash?

3) Is this issue something that started to happen after an update?

4) To see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

description: updated
tags: added: bios-outdated-2.47
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Simon (simsamsom) wrote :

Christopher, thanks for responding so quickly!

It took me a while to download the newest ISO.

I've been able to narrow it down a bit more as well: the log out only happens if I have my second monitor plugged in. Sometimes (but not always) the second monitor will flash the "logged out" screen for a second or two before going dim. If I unplug the second monitor and close the lid of my computer I log in and it's still the same session.

I have "Suspend even if external monitor is plugged in" toggled in Tweak Tools.

1) No, my session is not logged out if I suspend via the GUI with the lid open.

2) There are! Is it safe to upload that file? I can do so.

3) I'm fairly sure it's happened since I initially installed 16.04

4) With the live USB I don't think I can set up a user account that will get logged out? When I close the lid of my laptop without the external monitor plugged in there is no log in screen and I just see the desktop (even when I toggle that the user is not logged in automatically). With the external monitor plugged in the desktop just switches. I couldn't find a toggle for the "Suspend even if external monitor is plugged in" option. I'm happy to actually try upgrading my machine to 18.04 or 17.10, but that would lose you your test scenario if it ends up working?

Revision history for this message
penalvch (penalvch) wrote :

Simon:

1) Regarding the crash files, it is best if one reports the crash files as documented at https://help.ubuntu.com/community/ReportingBugs (not attach them).

2) Regarding the crash files, could you please advise to their file name(s)?

3) Regarding upgrading, if you do so and the problem is fixed, then that is the best outcome, and doesn't cause anything negative to happen.

description: updated
Revision history for this message
Simon (simsamsom) wrote :

Hey Christopher,

1) When I report the crash files with:

$ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash

I get a pop saying Ubuntu has experienced an error and asks me to continue to report it. I'm going to assume that this is part of the process of reporting it and it's working correctly, and not ubuntu-bug experiencing a bug while I'm reporting it (it's a bit confusing to me). But it's not clear to me what the next steps are here (even from that documentation).

2) The crash created after the crash are:

ls -la /var/crash/
total 50516
drwxrwsrwt 2 root whoopsie 4096 Mar 9 11:12 .
drwxr-xr-x 14 root root 4096 Aug 1 2017 ..
-rw-r----- 1 root whoopsie 560003 Mar 7 13:16 _lib_systemd_systemd-udevd.0.crash
-rwxrwxrwx 1 root whoopsie 0 Mar 9 11:11 .lock
-rw-r----- 1 simon whoopsie 1585974 Mar 9 11:12 _opt_atom_atom.1000.crash
-rw-r----- 1 simon whoopsie 49568222 Mar 9 11:12 _usr_bin_gnome-shell.1000.crash

The Mar 9 ones are the ones that appeared after I closed my lid, let the laptop suspend, and start things up again. I don't think the atom crash file is always there.

3) I'll try upgrading to 17.10 for now, and then 18.04 when it becomes the new LTS.

Revision history for this message
penalvch (penalvch) wrote :

Simon, given the gnome-shell crash files generated immediately after, I'll move this over there for specialists to review.

affects: xorg (Ubuntu) → gnome-shell (Ubuntu)
Changed in gnome-shell (Ubuntu):
status: Incomplete → New
Revision history for this message
Simon (simsamsom) wrote :

Can confirm that this is fixed in 17.10. When I close the lid of my computer and it suspends, the screen is an "unlock" screen.

Changed in gnome-shell (Ubuntu):
status: New → Fix Released
Revision history for this message
WinEunuchs2Unix (ricklee518) wrote :

This happens to me periodically with Ubuntu 16.04.6 LTS, Kernel 4.14.114.

External HDMI 1080p TV nVidia GTX 970M driven
External HDMI 4K TV i915 Thunderbolt3 USB-C driven
Internal Dell 1080p LCD i915 driven

Method:

1) close laptop lid with power & systemd set to "do nothing"
2) external monitors will disconnect (no signal) and have to move mouse to reconnect.
3) select GUI suspend from external monitor
4) power off external screens after system suspends
5) power on external screens
6) open laptop lid to resume
7) about 20% of time login screen appears and all work is lost

If fixed in 17.10 would be nice to see backported to 16.04 as current plans for upgrade aren't until 20.04.

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

Unfortunately we can't backport a fix which we don't know the location of. And I don't see any links to a patch here. Also, we generally don't support/patch gnome-shell on Ubuntu releases older than 18.04.

Anyway, this bug is closed and we can't be sure you are experiencing the exact same issue. So please open a new bug.

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.