** Changed in: gdm
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1874262
Title:
User session does not start: Problem with
The above fix was released in gdm3 3.37.1
** Changed in: gdm3 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1874262
Title:
After some further testing, fixing the GDM bug allows logging into both
X11 and Wayland on 19.10 while Chrome Remote Desktop is running, but on
20.04, I cannot start a Wayland while CRD is running (X11 still works
once the GDM fix is applied).
Taking a brief look at the logs, it appears there is
There's only one GDM greeter in this case. The bug is that if there's
*any* other PAM/loginctl session for the user of type "x11", GDM will
fail to log the user in without the above patch.
When Chrome Remote Desktop starts at boot, it creates such a user
session (via PAM) under the user who has
Thanks, patching the login code is always a bit risky so we should probably
give those changes some testing in the new cycle first.
How do you end up with several active greeters? It doesn't seem like a common
scenario
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Fix Committed
**
The attachment "try-looking-up-session-by-pid-first.diff" seems to be a
patch. If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad
I can confirm that this upstream commit fixes the issue:
https://gitlab.gnome.org/GNOME/gdm/-/commit/32646105196ed7a687f3684b69ea544dd01d2ade?merge_request_iid=90
I've attached it as a patch, and verified that it applies cleanly to
gdm3-3.34.1 and resolves the issue on Ubuntu 19.10.
Can the
** Also affects: gdm via
https://gitlab.gnome.org/GNOME/gdm/-/issues/580
Importance: Unknown
Status: Unknown
** No longer affects: xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
(the xkbcomp stuff is clearly marked as "Errors from xkbcomp are not fatal to
the X server").
This will likely be resolved with the patch from
https://gitlab.gnome.org/GNOME/gdm/-/issues/580.
** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #580
https://gitlab.gnome.org/GNOME/gdm/-/issues/580
** Changed in: gdm3 (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1874262
Title:
User
** Summary changed:
- User session does not start: xkbcomp "Internal error: Could not resolve
keysym Invalid"
+ User session does not start: Problem with chrome-remote-desktop
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
11 matches
Mail list logo
