[oe] LXDM failure on master-next
Hello everybody, my image has been booting into shell instead of LXDM ever since I switched to master-next from Dora. I believe LXDM is not compatible with the new systemd, but my knowledge is limited. Here is what I gathered so far: 1.5 Dora: root@overo:~$ cat log | grep -i lxdm Jan 01 00:02:38 overo systemd[1]: Looking at job lxdm.service/start conflicted_by=no Jan 01 00:02:38 overo systemd[1]: Looking at job lxdm.service/stop conflicted_by=no Jan 01 00:02:38 overo systemd[1]: Fixing conflicting jobs by deleting job lxdm.service/stop Jan 01 00:02:38 overo systemd[1]: Installed new job lxdm.service/start as 89 Jan 01 00:02:48 overo systemd[1]: About to execute: /usr/sbin/lxdm Jan 01 00:02:48 overo systemd[1]: Forked /usr/sbin/lxdm as 127 Jan 01 00:02:48 overo systemd[127]: Executing: /usr/sbin/lxdm Jan 01 00:02:53 overo kernel[114]: [4.286621] systemd[1]: Looking at job lxdm.service/start conflicted_by=no Jan 01 00:02:53 overo kernel[114]: [4.286651] systemd[1]: Looking at job lxdm.service/stop conflicted_by=no Jan 01 00:02:53 overo kernel[114]: [4.286682] systemd[1]: Fixing conflicting jobs by deleting job lxdm.service/stop Jan 01 00:02:53 overo kernel[114]: [4.289398] systemd[1]: Installed new job lxdm.service/start as 89 Jan 01 00:02:55 overo kernel[114]: [ 15.754699] systemd[1]: lxdm.service changed dead - running Jan 01 00:02:55 overo kernel[114]: [ 15.754852] systemd[1]: Job lxdm.service/start finished, result=done Jan 01 00:02:55 overo systemd[1]: lxdm.service changed dead - running Jan 01 00:02:55 overo systemd[1]: Job lxdm.service/start finished, result=done root@overo:~$ master-next: root@overo:~$ cat systemd_log | grep -i lxdm Jan 01 00:22:42 overo systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/lxdm_2eservice interface=org.freedesktop.DBus.Properties member=GetAll cookie=1 reply_cookie=0 error=n/a Jan 01 00:22:42 overo systemd[1]: Collecting lxdm.service Jan 01 00:22:42 overo systemd[1]: Failed to send unit change signal for lxdm.service: Transport endpoint is not connected Jan 01 00:22:42 overo systemd[1]: Failed to send unit remove signal for lxdm.service: Transport endpoint is not connected root@overo:~$ Manually starting the service works. Adding the lxdm service to multi-user target works also, however this feels like a hack. Any pointers will be appreciated! Thanks, Adam -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] LXDM failure on master-next
On Thu, Apr 3, 2014 at 7:52 PM, Adam Lee adam.yh@gmail.com wrote: Hello everybody, my image has been booting into shell instead of LXDM ever since I switched to master-next from Dora. I believe LXDM is not compatible with the new systemd, but my knowledge is limited. Here is what I gathered so far: 1.5 Dora: root@overo:~$ cat log | grep -i lxdm Jan 01 00:02:38 overo systemd[1]: Looking at job lxdm.service/start conflicted_by=no Jan 01 00:02:38 overo systemd[1]: Looking at job lxdm.service/stop conflicted_by=no Jan 01 00:02:38 overo systemd[1]: Fixing conflicting jobs by deleting job lxdm.service/stop Jan 01 00:02:38 overo systemd[1]: Installed new job lxdm.service/start as 89 Jan 01 00:02:48 overo systemd[1]: About to execute: /usr/sbin/lxdm Jan 01 00:02:48 overo systemd[1]: Forked /usr/sbin/lxdm as 127 Jan 01 00:02:48 overo systemd[127]: Executing: /usr/sbin/lxdm Jan 01 00:02:53 overo kernel[114]: [4.286621] systemd[1]: Looking at job lxdm.service/start conflicted_by=no Jan 01 00:02:53 overo kernel[114]: [4.286651] systemd[1]: Looking at job lxdm.service/stop conflicted_by=no Jan 01 00:02:53 overo kernel[114]: [4.286682] systemd[1]: Fixing conflicting jobs by deleting job lxdm.service/stop Jan 01 00:02:53 overo kernel[114]: [4.289398] systemd[1]: Installed new job lxdm.service/start as 89 Jan 01 00:02:55 overo kernel[114]: [ 15.754699] systemd[1]: lxdm.service changed dead - running Jan 01 00:02:55 overo kernel[114]: [ 15.754852] systemd[1]: Job lxdm.service/start finished, result=done Jan 01 00:02:55 overo systemd[1]: lxdm.service changed dead - running Jan 01 00:02:55 overo systemd[1]: Job lxdm.service/start finished, result=done root@overo:~$ master-next: root@overo:~$ cat systemd_log | grep -i lxdm Jan 01 00:22:42 overo systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/lxdm_2eservice interface=org.freedesktop.DBus.Properties member=GetAll cookie=1 reply_cookie=0 error=n/a Jan 01 00:22:42 overo systemd[1]: Collecting lxdm.service Jan 01 00:22:42 overo systemd[1]: Failed to send unit change signal for lxdm.service: Transport endpoint is not connected Jan 01 00:22:42 overo systemd[1]: Failed to send unit remove signal for lxdm.service: Transport endpoint is not connected root@overo:~$ Manually starting the service works. Adding the lxdm service to multi-user target works also, however this feels like a hack. Any pointers will be appreciated! Thanks, Adam See http://lists.openembedded.org/pipermail/openembedded-core/2014-April/091380.html -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] LXDM failure on master-next
Great! Exactly what I needed. Thanks Andreas, Adam On Thu, Apr 3, 2014 at 11:08 AM, Andreas Müller schnitzelt...@googlemail.com wrote: On Thu, Apr 3, 2014 at 7:52 PM, Adam Lee adam.yh@gmail.com wrote: Hello everybody, my image has been booting into shell instead of LXDM ever since I switched to master-next from Dora. I believe LXDM is not compatible with the new systemd, but my knowledge is limited. Here is what I gathered so far: 1.5 Dora: root@overo:~$ cat log | grep -i lxdm Jan 01 00:02:38 overo systemd[1]: Looking at job lxdm.service/start conflicted_by=no Jan 01 00:02:38 overo systemd[1]: Looking at job lxdm.service/stop conflicted_by=no Jan 01 00:02:38 overo systemd[1]: Fixing conflicting jobs by deleting job lxdm.service/stop Jan 01 00:02:38 overo systemd[1]: Installed new job lxdm.service/start as 89 Jan 01 00:02:48 overo systemd[1]: About to execute: /usr/sbin/lxdm Jan 01 00:02:48 overo systemd[1]: Forked /usr/sbin/lxdm as 127 Jan 01 00:02:48 overo systemd[127]: Executing: /usr/sbin/lxdm Jan 01 00:02:53 overo kernel[114]: [4.286621] systemd[1]: Looking at job lxdm.service/start conflicted_by=no Jan 01 00:02:53 overo kernel[114]: [4.286651] systemd[1]: Looking at job lxdm.service/stop conflicted_by=no Jan 01 00:02:53 overo kernel[114]: [4.286682] systemd[1]: Fixing conflicting jobs by deleting job lxdm.service/stop Jan 01 00:02:53 overo kernel[114]: [4.289398] systemd[1]: Installed new job lxdm.service/start as 89 Jan 01 00:02:55 overo kernel[114]: [ 15.754699] systemd[1]: lxdm.service changed dead - running Jan 01 00:02:55 overo kernel[114]: [ 15.754852] systemd[1]: Job lxdm.service/start finished, result=done Jan 01 00:02:55 overo systemd[1]: lxdm.service changed dead - running Jan 01 00:02:55 overo systemd[1]: Job lxdm.service/start finished, result=done root@overo:~$ master-next: root@overo:~$ cat systemd_log | grep -i lxdm Jan 01 00:22:42 overo systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/lxdm_2eservice interface=org.freedesktop.DBus.Properties member=GetAll cookie=1 reply_cookie=0 error=n/a Jan 01 00:22:42 overo systemd[1]: Collecting lxdm.service Jan 01 00:22:42 overo systemd[1]: Failed to send unit change signal for lxdm.service: Transport endpoint is not connected Jan 01 00:22:42 overo systemd[1]: Failed to send unit remove signal for lxdm.service: Transport endpoint is not connected root@overo:~$ Manually starting the service works. Adding the lxdm service to multi-user target works also, however this feels like a hack. Any pointers will be appreciated! Thanks, Adam See http://lists.openembedded.org/pipermail/openembedded-core/2014-April/091380.html -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
