Ok, so it looks like this is intended behaviour, ie to save memory? When
I first reported the bug, gdm3 didn't reappear when I switched to tty1,
but now it reappears after five seconds or so of showing a blank screen.
It then dies shortly after I switch back to tty2. It's just a pity it
takes so lo
Do you have evidence of a "crash"? If not then please reword the bug to
describe the problem more specifically.
I know the new version of gdm3 in cosmic is a bit buggy, related to it
trying to kill/restart its own gnome-shell instance on VT switch
changes. That's intended as a memory-saving featur
This is pretty easy to reproduce: the latest daily build (Oct 4) of
cosmic does it on first reboot after installation in a VM: as on my
system, loginctl shows only a single session present. There are no crash
files in /var/crash, and there are no errors logged at ubuntu.com.
Is this expected behav
In that case someone needs to debug the script and update the comment in
that bug :( Or better yet, fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794638
Title:
gdm crashes immediately after
There aren't any crash files and there aren't any relevant errors at
errors.ubuntu.com. I can't apply the workaround from bug #994921 because
there is no line with problem_types in /etc/apport/crashdb.conf to
comment out.
--
You received this bug notification because you are a member of Ubuntu
Bu
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
