`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"
After comment #7 it's rather easy for me to reproduce this bug now.
Interesting the system log during the hang says:
Sep 02 16:56:32 kab systemd-logind[752]: Session 9 logged out. Waiting
for processes to exit.
So maybe one of these are the issue? They are all reproducibly lingering
after
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
the i915 one (Dell XPS 13 9370) is the one with automatic login enabled.
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** 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
Interesting both i915 and amdgpu are affected.
--
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
To manage
... and the other affected machine (just checked it's still affected
today after latest updates)
** Attachment added: "lspcik-dell.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286167/+files/lspcik-dell.txt
--
You received this bug notification because you
As attached.
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286165/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Can you please run:
lspci -k
and send us the output? At least for the graphics card section.
** Tags added: wayland
--
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
Only affects Wayland sessions, not x11. I should have mentioned it
earlier, it's been my default for some time now (because #1827428 which
still affects latest 19.10) and I forgot.
It also seems not to be the upstream bug, unless the discussion there is
going off in the wrong directions. They now
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
there are no crash files relating to when this happens. Currently
sitting at the machine that *doesn't* have autologin enabled, where it's
just happened again, there is nothing in /var/crash relating to this.
(nextcloud client keeps crashing, and there are crash files relating to
that, the most
additionally as it does seem to involve console switching and you might
think kernel to be relevant to that, i tried again after the most recent
kernel upgrade in 19.10 (5.2.20-15-generic). no change.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Let's start by checking for crashes, which can confuse and break the
console switching. Please try these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of Ubuntu
Desktop
Network connection does not die. (It appeared to first time but I think
that's just my ongoing random - and irrelevant here - avahi issues on
this machine.)
But gnome-shell is *not* running after triggering the bug, so sudo
killall on it just produces "gnome-shell: no process found". So that was
This might be somehow related to bug 1841873. To check that, please log
in via ssh and force a crash dump while it is unresponsive:
sudo killall -ABRT gnome-shell
Then please report that in a new bug using:
ubuntu-bug /var/crash/YOURFILE
and tell us the new bug ID.
** Changed in: gdm3
32 matches
Mail list logo
