[Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session

Rachel Greenham 1841915 at bugs.launchpad.net
Tue Sep 3 13:39:24 UTC 2019


journalctl -b output as attached

loginctl as below:

rachel in ~ at rainbow
➜ loginctl
SESSION  UID USER   SEAT  TTY
      1 1000 rachel seat0 tty2
      3 1000 rachel       pts/0

2 sessions listed.

rachel in ~ at rainbow
➜ loginctl show-session 1
Id=1
User=1000
Name=rachel
Timestamp=Tue 2019-09-03 14:30:40 BST
TimestampMonotonic=20750725
VTNr=2
Seat=seat0
TTY=tty2
Remote=no
Service=gdm-autologin
Scope=session-1.scope
Leader=5228
Audit=1
Type=wayland
Class=user
Active=yes
State=closing
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
LockedHint=no

rachel in ~ at rainbow
➜ loginctl show-session 3
Id=3
User=1000
Name=rachel
Timestamp=Tue 2019-09-03 14:31:47 BST
TimestampMonotonic=87793987
VTNr=0
TTY=pts/0
Remote=yes
RemoteHost=192.168.1.109
Service=sshd
Scope=session-3.scope
Leader=7048
Audit=3
Type=tty
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=1567517624629274
IdleSinceHintMonotonic=205041051
LockedHint=no


** Attachment added: "jctl.log"
   https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286446/+files/jctl.log

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1841915

Title:
  black screen, unresponsive, after logout from gnome Wayland session

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  on logout the screen is black, the system is unresponsive and has to
  be restarted. (Untested by me yet, but I expect ssh-ing in and
  restarting gdm would work.)

  I believe this may be already reported upstream here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've
  reported this against gdm3 even though I honestly don't know if it
  might be a gnome-shell, gnome-session or mutter based error. (FWIW
  without the upstream bug to link to I'd maybe suspect gnome-shell
  first.)

  NB: This machine's conf has AutomaticLogin enabled, but another
  machine also on 19.10 does not, and it's showing the same thing. On
  *this* machine I found that the *first* time I logged out, it was OK,
  but not the second time. On the other machine, it fails first time
  too. It's as if the gdm login screen can appear exactly once. That
  (and being on gnome 3.33) is why I don't think this is a dupe of
  #1824588.

  Nothing appears in /var/crash as a result of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.33.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 29 10:51:22 2019
  InstallationDate: Installed on 2018-09-11 (351 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions



More information about the foundations-bugs mailing list