closed lid (hp 15 pavilion) opened to frozen black screen

[travis highley]

switched tty to another and back to currernt (7) and then saw the message "lock screen will show in a second" (something like that). workaround: trying to start x from another tty fails, but seems to reset main tty so you can resume session with no data loss

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: xfdesktop4 4.13.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-8.9-lowlatency 4.18.7
Uname: Linux 4.18.0-8-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Oct 11 01:55:57 2018
ExecutablePath: /usr/bin/xfdesktop
InstallationDate: Installed on 2018-10-10 (0 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927.1)
ProcCmdline: xfdesktop
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f009e434ac5 <g_type_check_instance_is_fundamentally_a+5>: mov (%rdi),%rax
 PC (0x7f009e434ac5) ok
 source "(%rdi)" (0x69506b6447203a29) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xfdesktop4
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_task_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_input_stream_read_async () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: xfdesktop crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1781298, so 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. Please continue to report any other bugs you may find.