[Bug 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2019-10-17 Thread Ted Goddard
Retested with Ubuntu 19.10 release. Auto login still causes login loop
on above system. Disabling auto login allows login to work as expected.

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

Title:
  Automatic login fails and then all subsequent logins fail. Killing
  gnome-session-binary fixes it, or just not using automatic login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2019-10-15 Thread Ted Goddard
Confirmed: the user can successfully log in with auto login turned off.

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

Title:
  Automatic login fails and then all subsequent logins fail. Killing
  gnome-session-binary fixes it, or just not using automatic login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2019-10-15 Thread Ted Goddard
I will test with auto login turned off. Is there a different video
driver setting that might be useful to test, like VGA only?

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

Title:
  Automatic login fails and then all subsequent logins fail. Killing
  gnome-session-binary fixes it, or just not using automatic login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848093] [NEW] Login loop with gdm3 and 19.10 beta

2019-10-14 Thread Ted Goddard
Public bug reported:

The user is unable to login from the login screen. The password is
accepted but the password prompt is displayed again.

Description:Ubuntu Eoan Ermine (development branch)
Release:19.10

gdm3:
  Installed: 3.34.1-1ubuntu1
  Candidate: 3.34.1-1ubuntu1
  Version table:
 *** 3.34.1-1ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status


Note that the login screen appears even though I had specified auto login. 

Perhaps this one line is important:
Oct 14 14:41:24 carbon gdm3: GdmSession: Considering session (null) for 
username (null)

I am using an NVIDIA RTX 2080Ti with the bundled drivers.

When used via ssh, the following brings the system to a working desktop:

sudo service gdm restart

However, when this was used from a terminal from ctrl-alt-F3 the system
locked completely and was unresponsive over ssh.

/var/log/syslog is below:

Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: trying to get updated 
username
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: PAM conversation 
returning 0: Success
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: state AUTHENTICATED
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: trying to get updated 
username
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: username is 'ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: old-username='ted' 
new-username='ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: attempting to change 
state to AUTHORIZED
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: determining if 
authenticated user (password required:0) is authorized to session
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: state AUTHORIZED
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: attempting to change 
state to ACCREDITED
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'LOGNAME=ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'USER=ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'USERNAME=ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'HOME=/home/ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'PWD=/home/ted'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'SHELL=/usr/bin/zsh'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: Set PAM environment 
variable: 'PATH=/usr/local/bin:/usr/bin:/bin:/usr/games'
Oct 14 14:41:24 carbon gdm-password]: GdmSessionWorker: state ACCREDITED
Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorker: pid 1802 
reauthenticated user 124 with service 'gdm-password'
Oct 14 14:41:24 carbon gdm-autologin]: GdmSession: Stopping all conversations
Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorkerJob: Stopping job 
pid:3419
Oct 14 14:41:24 carbon gdm-autologin]: GdmCommon: sending signal 15 to process 
3419
Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorkerJob: Waiting on process 
3419
Oct 14 14:41:24 carbon gdm-autologin]: GdmCommon: process (pid:3419) done 
(status:0)
Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorkerJob: SessionWorkerJob 
died
Oct 14 14:41:24 carbon gdm-autologin]: GdmSessionWorker: client cancelled 
reauthentication request
Oct 14 14:41:24 carbon gdm-autologin]: GdmSession: Stopping all conversations
Oct 14 14:41:24 carbon gdm3: GdmSession: Emitting 'reauthenticated' signal 
Oct 14 14:41:24 carbon gdm3: GdmSession: type (null), program? no, seat seat0
Oct 14 14:41:24 carbon gdm3: GdmManager: Considering session 1 on seat seat0 
belonging to user ted
Oct 14 14:41:24 carbon gdm3: GdmManager: yes, found session 1
Oct 14 14:41:24 carbon gdm3: Unlocking session 1
Oct 14 14:41:24 carbon gdm3: GdmManager: trying to open new session
Oct 14 14:41:24 carbon gdm3: Finding a graphical session for user 124
Oct 14 14:41:24 carbon gdm3: Considering session 'c1'
Oct 14 14:41:24 carbon gdm3: GdmSession: Considering session (null) for 
username (null)
Oct 14 14:41:24 carbon gdm3: GdmDBusServer: new connection 0x5631e08edec0
Oct 14 14:41:24 carbon gdm3: GdmSession: Handling new connection from outside
Oct 14 14:41:24 carbon gdm3: GdmManager: client with pid 1802 connected
Oct 14 14:41:24 carbon gdm3: GdmDisplay: Got timed login details for display: 0
Oct 14 14:41:31 carbon xdg-desktop-por[1623]: Failed to get application states: 
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not 
allowed
Oct 14 14:41:33 carbon gdm-autologin]: GdmSession: external connection closed
Oct 14 14:41:33 carbon gdm-autologin]: GdmSessionWorker: client disconnected 
from reauthentication server
Oct 14 14:41:33 carbon gdm3: GdmSession: external connection closed
Oct 14 14:41:33 carbon gdm-autologin]: GdmSession: Disposing