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

2018-09-03 Thread 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
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) systemd-logind: got resume for 13:71
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) systemd-logind: got resume for 13:70
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) systemd-logind: got resume for 13:69
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) systemd-logind: got resume for 13:64
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) systemd-logind: got resume for 13:68
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) systemd-logind: got resume for 13:66
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) systemd-logind: got resume for 226:0
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) AIGLX: Resuming AIGLX clients after VT switch
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) modeset(0): EDID vendor "LGD", prod id 1005
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) modeset(0): Printing DDC gathered Modelines:
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) modeset(0): Modeline "1366x768"x0.0   74.80  1366 1414 1446 1578  768 770 775 790 -hsync -vsync (47.4 kHz eP)
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event2  - Power Button: is tagged by udev as: Keyboard
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event2  - Power Button: device is a keyboard
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event5  - Logitech USB Receiver: is tagged by udev as: Mouse
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event5  - Logitech USB Receiver: device is a pointer
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event6  - Logitech USB Receiver: is tagged by udev as: Keyboard
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event6  - Logitech USB Receiver: device is a keyboard
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event0  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event0  - AT Translated Set 2 keyboard: device is a keyboard
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event7  - TPPS/2 IBM TrackPoint: is tagged by udev as: Mouse Pointingstick
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event7  - TPPS/2 IBM TrackPoint: trackpoint does not have a specified range, guessing... see https://wayland.freedesktop.org/libinput/doc/1.11.3/trackpoints.html
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event7  - TPPS/2 IBM TrackPoint: trackpoint device set to range 31
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event7  - TPPS/2 IBM TrackPoint: device is a pointer
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) systemd-logind: got resume for 13:86
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event22 - Integrated Camera: Integrated C: is tagged by udev as: Keyboard
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) event22 - Integrated Camera: Integrated C: device is a keyboard
Sep  3 18:59:10 k-c13 /usr/lib/gdm3/gdm-x-session[]: (II) systemd-logind: got resume for 13:67
Sep  3 18:59:10 

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

2018-09-02 Thread Simon McVittie
Control: tags -1 + moreinfo

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).

> 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?

> 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.

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

Thanks,
smcv



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

2018-09-01 Thread Michael Ott
Package: gnome-shell
Version: 3.29.92-1
Severity: normal

Dear Maintainer,

1. Screen is blank
2. Press any key
3. Wipe to close screen saver picture
4. Gnome shell start again like alt + F2 and r



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (710, 'unstable'), (660, 'testing'), (600, 'stable'), (510, 
'experimental'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
LANGUAGE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.28.0-2
ii  evolution-data-server3.29.92-1
ii  gir1.2-accountsservice-1.0   0.6.45-1
ii  gir1.2-atspi-2.0 2.29.1-1
ii  gir1.2-freedesktop   1.57.3-2
ii  gir1.2-gcr-3 3.28.0-1
ii  gir1.2-gdesktopenums-3.0 3.28.0-1
ii  gir1.2-gdm-1.0   3.29.91-2
ii  gir1.2-geoclue-2.0   2.4.12-2
ii  gir1.2-glib-2.0  1.57.3-2
ii  gir1.2-gnomebluetooth-1.03.28.2-1
ii  gir1.2-gnomedesktop-3.0  3.29.91-1
ii  gir1.2-gtk-3.0   3.23.2-1
ii  gir1.2-gweather-3.0  3.28.1-1
ii  gir1.2-ibus-1.0  1.5.19-1
ii  gir1.2-mutter-3  3.29.92-1
ii  gir1.2-nm-1.01.12.2-2
ii  gir1.2-nma-1.0   1.8.16-1
ii  gir1.2-pango-1.0 1.42.4-2
ii  gir1.2-polkit-1.00.115-1
ii  gir1.2-rsvg-2.0  2.44.1-1
ii  gir1.2-soup-2.4  2.63.92-1
ii  gir1.2-upowerglib-1.00.99.8-2
ii  gjs  1.53.3-1
ii  gnome-backgrounds3.29.90-1
ii  gnome-settings-daemon3.29.90.1-1
ii  gnome-shell-common   3.29.92-1
ii  gsettings-desktop-schemas3.28.0-1
ii  libatk-bridge2.0-0   2.26.2-1
ii  libatk1.0-0  2.28.1-1
ii  libc62.27-5
ii  libcairo21.15.12-1
ii  libcanberra-gtk3-0   0.30-6
ii  libcanberra0 0.30-6
ii  libcroco30.6.12-2
ii  libecal-1.2-19   3.29.92-1
ii  libedataserver-1.2-233.29.92-1
ii  libgcr-base-3-1  3.28.0-1
ii  libgdk-pixbuf2.0-0   2.36.12-2
ii  libgirepository-1.0-11.57.3-2
ii  libgjs0g [libgjs0-libmozjs-52-0] 1.53.3-1
ii  libglib2.0-0 2.57.2-2
ii  libglib2.0-bin   2.57.2-2
ii  libgstreamer1.0-01.14.2-2
ii  libgtk-3-0   3.23.2-1
ii  libical3 3.0.3-1
ii  libjson-glib-1.0-0   1.4.2-4
ii  libmutter-3-03.29.92-1
ii  libnm0   1.12.2-2
ii  libpango-1.0-0   1.42.4-2
ii  libpangocairo-1.0-0  1.42.4-2
ii  libpolkit-agent-1-0  0.115-1
ii  libpolkit-gobject-1-00.115-1
ii  libpulse-mainloop-glib0  12.0-1
ii  libpulse012.0-1
ii  libsecret-1-00.18.6-2
ii  libstartup-notification0 0.12-5
ii  libsystemd0  239-7
ii  libx11-6 2:1.6.6-1
ii  libxfixes3   1:5.0.3-1
ii  mutter   3.29.92-1
ii  python3  3.6.6-1

Versions of packages gnome-shell recommends:
ii  bolt  0.3-3
ii  chrome-gnome-shell10.1-1
ii  gdm3  3.29.91-2
ii  gkbd-capplet  3.26.0-3
ii  gnome-control-center  1:3.29.92-1
ii  gnome-user-docs   3.28.2-1
ii  iio-sensor-proxy  2.4-2
ii  switcheroo-control1.2-1
ii  unzip 6.0-21

Versions of packages gnome-shell suggests:
ii  gir1.2-telepathyglib-0.12   0.24.1-2
ii  gir1.2-telepathylogger-0.2  0.8.2-3

-- no debconf information