[Touch-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file

2018-03-02 Thread Jerome Warnier
*** This bug is a duplicate of bug 1369216 *** https://bugs.launchpad.net/bugs/1369216 ** This bug has been marked a duplicate of bug 1369216 gpu-manager: /etc/modprobe.d is not a file -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file

2017-03-09 Thread davidak
Same with 16.04.2 with HWE stack on a Macbook Pro (Retina) with Intel i915 graphic. -- 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

[Touch-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file

2016-09-15 Thread Pander
Duplicate of https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1369216 ? -- 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

[Touch-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file

2015-10-13 Thread Goddard
I got a very similar error when doing prime-switch nvidia from intel on my Razer Blade 2015 /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

[Touch-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file

2015-09-14 Thread Alberto Milone
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

[Touch-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file

2015-09-07 Thread TJ
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

[Touch-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file

2015-09-06 Thread TJ
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

[Touch-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file

2015-09-01 Thread TJ
Also happening in 15.10 Wily, with lightdm 1.15.3-0ubuntu3 Repeated 3 times per second constantly for about 15 minutes and then system froze - not sure if this was the cause of the freeze but it was the only logged info immediately before the freeze. Sep 1 19:23:43 hephaestion lightdm[951]: