`sudo killall -9 gdm` immediately fixes the "unresponsive" problem for
me. But you have to SSH into the box to do this, which is an extreme
bandaid
The screen remains blank even moving the mouse around for a few minutes,
and pressing ESC a couple times.
The monitor shows as "no input"
--
You
Yes, confirmed fixed... somewhere.
** No longer affects: gnome-shell (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
as of this morning's updates, this problem seems to have disappeared.
I've been able to log out and back in several times to my ubuntu wayland
session, at least on my i915 machine (the dell laptop).
nb: this morning's updates updated gnome-session-bin and ubuntu-session
to 3.33.92-1ubuntu1, gdm3
Sorry I haven't got back to investigating this yet. I wonder though if
it's related to:
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/690
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
My point regarding gnome-session-wayland.target is that if we're seeing
different filenames for that file (assuming they're functionally the
same) and mine definitely comes from gnome-session-bin, does that
suggest we're running different gnome-session-bin versions? And seeing
as you're not
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1841915
Title:
black screen, unresponsive, after logout from gnome Wayland session
To manage
minor contextual note: It took me a little while to get the other
machine, ssh in (offending ssh key to resolve), call up this page to
remind me of the exact commands. The point of which is to say, these
weren't taken *immediately* after the logout, but at least a minute
later, certainly beyond
On Tue, Sep 03, 2019 at 01:28:08PM -, Rachel Greenham wrote:
> It is definitely /usr/lib/systemd/user-gnome-session-wayland.target.
> dpkg -S on that file gives gnome-session-bin which is on version
> 3.33.90-2ubuntu2. dpkg -S on the .service file gives no match.
If it happens when you remove
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
It is definitely /usr/lib/systemd/user-gnome-session-wayland.target.
dpkg -S on that file gives gnome-session-bin which is on version
3.33.90-2ubuntu2. dpkg -S on the .service file gives no match.
This problem didn't start on upgrade to the 5.2 kernels, which happened
a few weeks(?) earlier, but
On Tue, Sep 03, 2019 at 11:42:51AM -, Rachel Greenham wrote:
> With --systemd removed as directed I still ended up stuck on a black
> screen, except this time it had a flashing white text cursor in the top
> left.
OK, please enable GDM debugging as outlined previously, reproduce the
problem,
On Tue, Sep 03, 2019 at 11:34:10AM -, Rachel Greenham wrote:
> There is no /usr/lib/systemd/user/gnome-session-wayland.service file on
> this system. There is a .target file though which is presumably the one.
> As the presumably-default timeout didn't seem to be honoured here there
> didn't
With --systemd removed as directed I still ended up stuck on a black
screen, except this time it had a flashing white text cursor in the top
left.
(BTW reboots occurred between each test, somewhat perforce...)
--
You received this bug notification because you are a member of Ubuntu
Desktop
I tried (just now) deliberately leaving it longer than 30 seconds to
come back after a logout. In fact left it longer than 60 seconds.
Nothing happening. I wasn't logged in via ssh as well at the time (I
hadn't thought the systemd --user instance was related to the ssh
session before so presumably
I have tried to reproduce this but I can't, not in a VM or on my real
system (i915). I tried with and without automatic login, with the
vanilla GNOME session and with the Ubuntu session, with and without the
same user logged in over SSH (to keep the systemd --user instance
alive), and every log
Setting gdm3 to debugging mode reveals:
Sep 02 17:31:01 kab systemd-logind[794]: Failed to restore VT, ignoring:
Input/output error
Full debug log attached.
** Attachment added: "eoan-wayland-logout-hang-verbose.txt.gz"
** Summary changed:
- black screen, unresponsive, after logout from gnome
+ black screen, unresponsive, after logout from gnome Wayland session
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
17 matches
Mail list logo
