The closed status is implicit. There are a few different Status values
that Launchpad treats as "closed" so I will set one...
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Damn doesn't seem to be a close or delete option. Daniel could you
please do the honours?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946
Title:
Gnome Wayland session starts, then quits.
To
Daniel I was pretty sure that the problem existed in my home directory. So,
rather than go through all the gnome gnome settings one by one, with subsequent
reboots, I cleaned out my home directory of all gnome specific settings at once
this am, and rebooted and problem is gone - I'm now in
Thanks for the log. This suggests gnome-shell died because Xorg or
Xwayland had already died:
Jan 04 12:21:10 stephen-desktop gnome-shell[83433]: gnome-shell: Fatal
IO error 11 (Resource temporarily unavailable) on X server :0.
So please:
1. Delete all existing files from /var/crash/
2.
Regarding Item #3: Didn't know /var/crash existed, thanks for the heads
up with the article too.
I browsed /var/crash, there are quite a few files (18) from yesterday
and today. Now none dated Jan 04 matched XWayland, however 2 from
yesterday. The more recent ones (Jan 04) mention 'Blueman
Thanks Daniel, yes I meant a crash, just different wording.
OK Attached is the file with all extensions disabled. If I'm reading the
file correctly it seems to be a snap issue with an app not autostarting?
Anyway lots of errors but when I scrolled down to the bottom showing the
most recent boot
Sessions generally can't quit themselves so this is probably a crash.
Please:
1. Uninstall any gnome-shell extensions you might have added, because
extensions are the most common cause of bugs.
2. Next time the problem happens, reboot immediately and then run:
journalctl -b-1 > prevboot.txt
