This is not really a bug in ubuntu-drivers-common. Those are just debugging messages (no actual error there). I can probably get rid of them but still that doesn't explain why a second xserver was started. Maybe another user logged into the system from lightdm? Or maybe lightdm is acting funny for some reason.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1452610 Title: /etc/modprobe.d is not a file Status in lightdm package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: /var/log/upstart# cat lightdm.log /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf Above looks weird... modprobe.d is a directory & why update- alternatives are called?! This is lightdm 1.10.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1452610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
