Hit this again today with lightdm spamming the logs.

I'd left the PC for about 45 minutes; came back to a backlit but black
display and no response to input.

I connected via SSH and found lightdm had TWO instances of X running,
one on tty7 and the other on tty8

I could find no clues in any of the logs as to what caused it; no signs
of errors or crashes. the Xorg.1.log for tty8 showed the GPU couldn't
obtain resources and failed (presumably due to tty7 with the first X
instance).

14:43:30 lightdm[1704]: /etc/modprobe.d is not a file
14:43:30 lightdm[1704]: message repeated 3 times: [ /etc/modprobe.d is not a 
file]
14:43:30 lightdm[1704]: update-alternatives: error: no alternatives for 
x86_64-linux-gnu_gfx
core_conf
14:43:30 lightdm[1704]: /etc/modprobe.d is not a file
14:43:30 lightdm[1704]: message repeated 3 times: [ /etc/modprobe.d is not a 
file]
14:43:30 lightdm[1704]: update-alternatives: error: no alternatives for 
x86_64-linux-gnu_gfxcore_conf
...
15:25:04 lightdm[1704]: /etc/modprobe.d is not a file
15:25:04 lightdm[1704]: message repeated 3 times: [ /etc/modprobe.d is not a 
file]
15:25:04 lightdm[1704]: update-alternatives: error: no alternatives for 
x86_64-linux-gnu_gfxcore_conf
15:25:04 lightdm[1704]: /etc/modprobe.d is not a file
15:25:04 lightdm[1704]: message repeated 3 times: [ /etc/modprobe.d is not a 
file]
15:25:04 lightdm[1704]: update-alternatives: error: no alternatives for 
x86_64-linux-gnu_gfxcore_conf

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452610

Title:
  /etc/modprobe.d is not a file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1452610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to