@Ads20000 Thanks for the link. Sadly, gdm3 is neither in the
autopkgtest-list, nor update-excuses, nor update-list, so it seems
things are stuck at an earlier stage and the documentation does not
clarify where to find out at which point help could be needed.

My intention was not to spam this report, but to find out where things are 
stuck (it's not obvious) and how to give support. 
It's also not about my personal (im)patience, but we have >200 desktops and 
>2000 Ubuntu containers and have had to stop the migration after the first 10 
desktops due to this bug (and three(!) other ones which all have been known 
*before* release and should either have been release blockers or been mentioned 
as "Known Issues" with the new LTS to prevent people from hopping onto the new 
supposedly-stable). For the other critical issues, QA apparently was even 
worse, since Debian and in one case also RHEL have already released fixes 
months or even a year ago, and there has been no reaction on Launchpad 
whatsoever yet. Since we are also still affected by critical bugs in 16.04 
which have been open since 16.04's release and could only be solved by PPA 
(broken OpenAFS), this makes me wonder whether Ubuntu still is a valid choice 
for institutional use, but this discussion certainly goes off topic here. 

Just let us know if there is something people could help with (testing
etc.). As it stands, the status is completely unclear apart from the
statement _to be patient_ - without indicating what the actual point is
where things are stuck.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to