Wrongly boots into low graphics mode

[Dave Goldsbrough]

Initially I thought this was an xorg bug and reported
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087

I also raised the bug https://bugs.freedesktop.org/show_bug.cgi?id=106407 and the very quick response said this
QUOTE
For starters, you are not using the -intel driver. It looks like your bug is a failure in handoff from whatever logind is being run. That prevents X from gaining control of /dev/dri/card0 due to -EPERM, and without that it cannot perform modesetting
UNQUOTE

That surprised me and I am currently researching what driver I am using and what driver I should be using. I have not changed anything for years.

I also looked in the auth.log and this is an extract:-
May 5 07:33:43 dave-ThinkPad-T410 systemd-logind[984]: New seat seat0.
May 5 07:33:43 dave-ThinkPad-T410 systemd-logind[984]: Watching system buttons on /dev/input/event2 (Power Button)
May 5 07:33:43 dave-ThinkPad-T410 systemd-logind[984]: Watching system buttons on /dev/input/event4 (Video Bus)
May 5 07:33:43 dave-ThinkPad-T410 systemd-logind[984]: Watching system buttons on /dev/input/event0 (Lid Switch)
May 5 07:33:43 dave-ThinkPad-T410 systemd-logind[984]: Watching system buttons on /dev/input/event1 (Sleep Button)
May 5 07:33:43 dave-ThinkPad-T410 systemd-logind[984]: Watching system buttons on /dev/input/event7 (ThinkPad Extra Buttons)
May 5 07:34:18 dave-ThinkPad-T410 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
May 5 07:34:18 dave-ThinkPad-T410 lightdm: PAM adding faulty module: pam_kwallet.so
May 5 07:34:18 dave-ThinkPad-T410 lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
May 5 07:34:18 dave-ThinkPad-T410 lightdm: PAM adding faulty module: pam_kwallet5.so
May 5 07:34:18 dave-ThinkPad-T410 lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
May 5 07:34:18 dave-ThinkPad-T410 systemd-logind[984]: New session c1 of user lightdm.
May 5 07:34:18 dave-ThinkPad-T410 systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
May 5 07:34:19 dave-ThinkPad-T410 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
May 5 07:34:19 dave-ThinkPad-T410 lightdm: PAM adding faulty module: pam_kwallet.so
May 5 07:34:19 dave-ThinkPad-T410 lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
May 5 07:34:19 dave-ThinkPad-T410 lightdm: PAM adding faulty module: pam_kwallet5.so
May 5 07:34:19 dave-ThinkPad-T410 lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "dave"
May 5 07:34:32 dave-ThinkPad-T410 lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm
May 5 07:34:32 dave-ThinkPad-T410 lightdm: pam_unix(lightdm:session): session opened for user dave by (uid=0)
May 5 07:34:32 dave-ThinkPad-T410 systemd-logind[984]: New session c2 of user dave.
May 5 07:34:32 dave-ThinkPad-T410 systemd: pam_unix(systemd-user:session): session opened for user dave by (uid=0)
May 5 07:34:38 dave-ThinkPad-T410 gnome-keyring-daemon[1781]: The PKCS#11 component was already initialized
May 5 07:34:38 dave-ThinkPad-T410 gnome-keyring-daemon[1781]: The Secret Service was already initialized
May 5 07:34:38 dave-ThinkPad-T410 gnome-keyring-daemon[1781]: The SSH agent was already initialized
May 5 07:34:39 dave-ThinkPad-T410 polkitd(authority=local): Registered Authentication Agent for unix-session:c2 (system bus name :1.90 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)
May 5 07:35:40 dave-ThinkPad-T410 sudo: dave : TTY=pts/19 ; PWD=/home/dave ; USER=root ; COMMAND=/usr/sbin/service network-manager restart
May 5 07:35:40 dave-ThinkPad-T410 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)

So, is lightdm the culprit?