That;s even worse. I don't any working screen, no login. This is not a trivial bug, I think, although I'd be happy for an easy solution.
ul 26 17:26:38 raffles systemd[2817]: Starting Accessibility services bus... Jul 26 17:26:38 raffles dbus-daemon[2832]: Successfully activated service 'org.a11y.Bus' Jul 26 17:26:38 raffles systemd[2817]: Started Accessibility services bus. Jul 26 17:26:38 raffles at-spi-bus-launcher[2843]: Activating service name='org.a11y.atspi.Registry' Jul 26 17:26:38 raffles at-spi-bus-launcher[2843]: Successfully activated service 'org.a11y.atspi.Registry' Jul 26 17:26:38 raffles org.a11y.atspi.Registry[2848]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Jul 26 17:26:38 raffles gnome-session[2839]: gnome-session-binary[2839]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Jul 26 17:26:38 raffles gnome-session-binary[2839]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Jul 26 17:26:38 raffles kernel: [ 21.885358] show_signal_msg: 1 callbacks suppressed Jul 26 17:26:38 raffles kernel: [ 21.885360] gnome-shell[2869]: segfault at 28 ip 00007f00f6c3ad74 sp 00007ffef4304940 error 4 in libmutter-0.so.0.0.0[7f00f6bf3000+131000] Jul 26 17:26:39 raffles gnome-session[2839]: gnome-session-binary[2839]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Jul 26 17:26:39 raffles gnome-session[2839]: gnome-session-binary[2839]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Jul 26 17:26:39 raffles gnome-session-binary[2839]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Jul 26 17:26:39 raffles gnome-session-binary[2839]: Unrecoverable failure in required component org.gnome.Shell.desktop Jul 26 17:26:39 raffles gnome-session[2839]: gnome-session-binary[2839]: CRITICAL: We failed, but the fail whale is dead. Sorry.... Jul 26 17:26:39 raffles gnome-session-binary[2839]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Jul 26 17:26:39 raffles gnome-session-binary[2839]: CRITICAL: We failed, but the fail whale is dead. Sorry.... Jul 26 17:26:39 raffles org.a11y.atspi.Registry[2848]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Jul 26 17:26:39 raffles org.a11y.atspi.Registry[2848]: after 21 requests (21 known processed) with 0 events remaining. Jul 26 17:26:39 raffles /usr/lib/gdm3/gdm-x-session[2822]: (**) Option "fd" "33" Jul 26 17:26:39 raffles /usr/lib/gdm3/gdm-x-session[2822]: (**) Option "fd" "36" On 26 July 2017 at 15:01, Daniel van Vugt <daniel.van.v...@canonical.com> wrote: > If everything works fine with lightdm then you can configure gdm to > behave the same as lightdm. > > Just edit /etc/gdm3/custom.conf and uncomment: #WaylandEnable=false > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1706474 > > Title: > gdm3 nvidia modeset=1 is broken, external screens don't work > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions > -- Tim Richardson ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1706474/+attachment/4921515/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706474 Title: gdm3 nvidia modeset=1 is broken, external screens don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
