Ubuntu 18.10 problem after lid close

Bug #1799978 reported by exactt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi, I recently upgraded my Dell 9360 to Ubuntu 18.10. Ever since I cannot login after I close the lid and reopen it. The screen is mostly black. See attached photos. There are also some graphical errors in the still working menues. My work around: Manually suspend the notebook and wake it up via power button. Then I get the regular login screen.

This happens both on X and Wayland sessions.

How can I debug further? Any help much appreciated.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroRelease: Ubuntu 18.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-03-11 (599 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
 Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
Package: systemd 239-7ubuntu10
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=76544dd2-4074-4427-844e-b34151f8ddb5 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Tags: wayland-session cosmic
Uname: Linux 4.18.0-10-generic x86_64
UpgradeStatus: Upgraded to cosmic on 2018-10-18 (13 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 07/09/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.9.0
dmi.board.name: 0VPVXX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd07/09/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0VPVXX:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.

Revision history for this message
exactt (giesbert) wrote :
Revision history for this message
exactt (giesbert) wrote :
Revision history for this message
exactt (giesbert) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected cosmic wayland-session
description: updated
Revision history for this message
exactt (giesbert) wrote : Dependencies.txt

apport information

Revision history for this message
exactt (giesbert) wrote : Lspci.txt

apport information

Revision history for this message
exactt (giesbert) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
exactt (giesbert) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
exactt (giesbert) wrote : ProcInterrupts.txt

apport information

Revision history for this message
exactt (giesbert) wrote : ProcModules.txt

apport information

Revision history for this message
exactt (giesbert) wrote : SystemdDelta.txt

apport information

Revision history for this message
exactt (giesbert) wrote : SystemdFailedUnits.txt

apport information

Revision history for this message
exactt (giesbert) wrote : UdevDb.txt

apport information

Revision history for this message
exactt (giesbert) wrote :
Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: New → Invalid
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.