Public bug reported: Doing some tweaks on that yakkety 64 bits running gnome-shell powered by nvidia-370 driver, i've discovered that issue.
Steps to reproduce: - on the initial working session, run "sudo dpkg-reconfigure lightdm" and select/validate gdm3 - close the session and reboot - as a result, X fails to start/load - switched to ctrl+alt+F2 and reconfigure again to choose back lightdm, and reboot - that time X start as expected Could it be related to the lightdm/accountservice relationship, not identical in the case of gdm3 choice ? info: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/857651 #4 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gdm3 3.20.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-4.5-generic 4.8.0-rc3 Uname: Linux 4.8.0-4-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 25 17:03:25 2016 SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616958 Title: GDM3 fails to start X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1616958/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
