touch-packages team mailing list archive

[TJ <ubuntu@xxxxxx>]

Hit this again today; Was working fine until about 05:40 when I locked
the session and left. Returned around 12:20, touched the mousepad to
wake the monitors, backlights come on but no display. SSH from another
host shows a 2nd X server attempts to start on :1 at the time I
returned, fails, tries again and fails.

The original X server :0 on tty7 still has a process in memory running
with no faults recorded in its Xorg.0.log but it is not possible to find
it on the tty.

Log file is full of the spamming messages since the system was locked
until lightdm service is restarted.

-- 
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