[Bug 1188131] Re: lightdm does not start on boot since change to use plymouth-ready (precise)

2016-04-04 Thread Robert Ancell
Closing assumed fixed. ** Changed in: lightdm (Ubuntu) Status: Confirmed => Fix Released ** Changed in: lightdm (Ubuntu Precise) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1188131] Re: lightdm does not start on boot since change to use plymouth-ready (precise)

2013-07-11 Thread Lindsay
I can confirm Tomasz Miąsko's observation. I changed the startup stanza in lightdm.conf to: start on ((filesystem and runlevel [!06] and started dbus and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1 or stopped udev-fallback-graphics))

[Bug 1188131] Re: lightdm does not start on boot since change to use plymouth-ready (precise)

2013-07-11 Thread Lindsay
See these pages: https://launchpad.net/ubuntu/+source/lightdm/1.6.0-0ubuntu2.1 http://www.ubuntuupdates.org/package/core/raring/main/proposed/plymouth It looks as if changes to lightdm.conf have outstripped changes to plymouth. -- You received this bug notification because you are a member

Re: [Bug 1188131] Re: lightdm does not start on boot since change to use plymouth-ready (precise)

2013-07-11 Thread Steve Langasek
On Thu, Jul 11, 2013 at 09:25:52PM -, Lindsay wrote: See these pages: https://launchpad.net/ubuntu/+source/lightdm/1.6.0-0ubuntu2.1 http://www.ubuntuupdates.org/package/core/raring/main/proposed/plymouth It looks as if changes to lightdm.conf have outstripped changes to plymouth.

Re: [Bug 1188131] Re: lightdm does not start on boot since change to use plymouth-ready (precise)

2013-06-19 Thread Andrew Duncan
Yes, I have /etc/init/plymouth-splash.conf Its contents are: descriptionUserspace bootsplash start on (started plymouth and (graphics-device-added PRIMARY_DEVICE_FOR_DISPLAY=1 or drm-device-added PRIMARY_DEVICE_FOR_DISPLAY=1 or stopped

[Bug 1188131] Re: lightdm does not start on boot since change to use plymouth-ready (precise)

2013-06-10 Thread Sebastien Bacher
thanks for your bug report, some similar issues are being discussed on the SRU bug, do you have a /etc/init/plymouth-splash.conf? ** Summary changed: - lightdm does not start on boot + lightdm does not start on boot since change to use plymouth-ready (precise) ** Changed in: lightdm (Ubuntu)

[Bug 1188131] Re: lightdm does not start on boot

2013-06-09 Thread barjea
Thank you. It works also for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1188131 Title: lightdm does not start on boot To manage notifications about this bug go to:

[Bug 1188131] Re: lightdm does not start on boot

2013-06-07 Thread Tomasz Miąsko
This seems to be caused by the following change in lightdm upstart configuration (introduced in 1.2.3-0ubuntu2.1): $ diff init.working/lightdm.conf init.broken/lightdm.conf 14,15c14 and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1 or stopped

[Bug 1188131] Re: lightdm does not start on boot

2013-06-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1188131 Title:

[Bug 1188131] Re: lightdm does not start on boot

2013-06-06 Thread Lindsay
I can confirm this bug, but have tried several stored kernels going back to 3.2.0-29-generic and the problem doesn't seem to be related to the kernel version. I note that a new version of lightdm came out several days ago and perhaps the problem is there. As a fairly acceptable workaround for

Re: [Bug 1188131] Re: lightdm does not start on boot

2013-06-06 Thread Andrew Duncan
The workaround works perfectly, thanks. I forgot to mention in the bug report that I had tried previous kernel versions, which didn't work for me either. On 06/06/13 20:47, Lindsay wrote: I can confirm this bug, but have tried several stored kernels going back to 3.2.0-29-generic and the