2012/8/12 Roger Leigh <rle...@codelibre.net>: > On Sun, Aug 12, 2012 at 03:37:52PM +1000, James Tocknell wrote: >> I've tested the patch, and it doesn't fix the issue I'm having. I'm >> using Upstart >> as my init daemon, and lightdm still fails, with no useful output in >> /var/log/boot. However, lightdm does start when I use sysvinit as the init >> daemon, with the patch. Could this be a Upstart issue? I know lightdm has >> some association with Ubuntu, and Upstart is Ubuntu's default init daemon, >> could the issue be with the very different versions of Upstart in Ubuntu and >> Debian? The problem could lie in the fix for the bug #660824, which was a >> change between the version of sysvinit-utils that works for me and don't work >> for me, as it's Upstart related. > > I'll have to ask Steve Langasek, who was responsible for that change. > > Steve, it appears that lightdm won't start using upstart with the > recent sysvinit upstart bridge stuff. I'm not sure if this is an > issue in sysvinit, startpar-upstart-inject, or upstart. I've > patched startpar to special-case lightdm as for gdm/kdm, but this > doesn't appear to have any effect here (but is probably generally > a good thing to have).
I'm wondering whether keeping the severity of this bug at RC level for what seems to be a corner case that only occurs whenever using 'upstart' as /sbin/init makes sense. It's currently blocking the transition into Testing of all packages generated from src:sysvinit, including recent fixes for a number of long-standing bugs. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
