Automatic login works only for wayland session

Have you enabled Wayland support by modifying your kernel command line?

Please attach a copy of your /proc/cmdline here, and also please run this command to attach further details:

apport-collect 1719128

From today:
BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=4f723467-a8f6-4798-8ddd-8e69490c4bd5 ro quiet splash vt.handoff=7

I've enabled wayland on nvidia using:
https://bugzilla.gnome.org/show_bug.cgi?id=781075#c2
/etc/modprobe.d/nvidia-graphics-drivers.conf:
options nvidia_381_drm modeset=0

When using Xorg I've tried to enable autologin option inside account settings (it's been working since 2 days after last update), but it gets reset every time I change it and relogin.
And interesting part: automatic login works on same system when it's run inside virtualbox. I'm currently testing 17.10 inside virtualbox and on physical HDD (I've burned virtualbox image into HDD).

So:
- 17.10+Xorg inside virtualbox: autologin works
- 17.10+Wayland from HDD: autologin works
- 17.10+Xorg from HDD: autologin doesn't work

Of course 17.10 inside virtualbox doesn't have nvidia drivers installed.

Feel free to ask me for help on this.

It may be related, error from journalctl:

wrz 25 23:19:30 olo-desktop gnome-shell[921]: Can't initialize KMS backend: could not find drm kms device
wrz 25 23:19:30 olo-desktop gnome-session[911]: gnome-session-binary[911]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
wrz 25 23:19:30 olo-desktop gnome-session-binary[911]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
wrz 25 23:19:30 olo-desktop gnome-session-binary[911]: Unrecoverable failure in required component org.gnome.Shell.desktop
wrz 25 23:19:30 olo-desktop gdm-launch-environment][867]: pam_unix(gdm-launch-environment:session): session closed for user gdm

AFAIK this is not a bug :(

The NVIDIA driver only supports Xorg or Wayland, but not both.

By default it only supports Xorg. And if you have added modeset=0 then it only supports Wayland. So yes we would expect Xorg logins to fail while you have modeset=0.

Actually modeset=1 is what you would use for a Wayland session...

Regardless, the NVIDIA driver only supports Xorg or Wayland for any given kernel configuration and not both.

Ok: I use default kernel (log above) and "default" (from PPA) binary drivers (384.90) and I'm on Xorg (default modeset=0) and here autologin doesn't work. If Nvidia supports Xorg by default why then it doesn't work?
I've made test with wayland just out of curiosity, changed to modeset=1, rebuild initramfs, reboot logged in run nautilus and then *reverted* changes. And I've noted it here because I though it might be somehow related (I usually do this to help devs). I'm not trying to run Xorg on drivers set to wayland.
So:
- I'm on default setup and autologin doesn't work
- autologin switch gets reset after setting it to enabled and restart session
- wayland session was only test because I wanted to check it out
- autologin works when I'm on virtualbox with Xorg
- autologin options are enabled in custom.conf (gdm3)

I can try to uninstall nvidia binary and check neuveau, should I try to do this?

Status changed to 'Confirmed' because the bug affects multiple users.

This bug is effecting all users that have NVidia proprietary drivers installed (everyone using CUDA).
this should be given priority.

Here is a thread about this very topic
https://askubuntu.com/questions/967847/ubuntu-17-10-gdm-auto-login-not-working

Confirmed this is affecting my system. Ubuntu 17.10 with proprietary Nvidia drivers. GDM3 cannot seem to auto-select non-wayland session or something. All options attempted in /etc/gdm3/custom.conf do not work.

Setting WaylandEnabled=false in the daemon secton of /etc/gdm3/custom.conf is a workaround.

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.