Bug#907753: gnome-shell: Shell crash after blank screen

[Michael Ott]

Hi Simon!

On Sat, 01 Sep 2018 at 14:39:26 +0200, Michael Ott wrote:
> > 1. Screen is blank
> > 2. Press any key
> 
> Please give a specific example of the key you press? You will get
> different results if you press a modifier key like Shift (screen
> wakes
> up but password prompt does not appear), or a key that could be part
> of
> your password like "a" (password prompt appears and that letter is
> typed
> into the password box).
For example my box resumed from suspend. The lock screen image is
visible. I press space to get to my desktop. 
> 
> > 3. Wipe to close screen saver picture
> 
> What exactly do you mean by "wipe"? Click the mouse button and drag
> upwards? Click the mouse button and drag downwards? Touch a
> touchscreen
> and drag in some direction?
Nearly the same as on the last "chapter". I want to "close" the lock
screen.

> > 4. Gnome shell start again like alt + F2 and r
> 
> Please look for more information about this crash in the systemd
> journal
> or in /var/log/syslog, and send it to the bug report.
I will add the syslog file after the resume is finished.


> 
A backtrace from the crash is also likely to be useful. Since you are
using systemd, here is a convenient way to get backtraces:

- Install the systemd-coredump package
- Enable the debug archive
  
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
  and install relevant debug symbols
- Reproduce the bug, causing the crash to happen
- Use "coredumpctl gdb" to debug the most recent core dump
- Use the "bt" command as in
  https://wiki.debian.org/HowToGetABacktrace#Running_gdb
This i will try the next time

CU
  Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: screensaver.log
Type: text/x-log
Size: 88825 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20180903/15a61a57/attachment-0001.bin>