<div dir="ltr"><span style="font-family:monospace,monospace">Hello Richard,</span><div><span style="font-family:monospace,monospace"><br></span></div><div><span style="font-family:monospace,monospace">I was under impression that installing Ubuntu-14.04.4 (+lastest updates) would give me stable build environment, unfortunately that is not the case ! I could see the logout issue on this installation too. So I believe that issue should be reproducible on any 14.04.x installation including 16.04.x with all latest updates installed. The second attempt of build on "Ubuntu-14.04.4" shows the status of bitbake as halted at libvorbis when logout happened:<br><br>---------------------------------------------------------<br>NOTE: Running task 2460 of 4212 (/home/poky/meta/recipes-core/ncurses/ncurses_6.0+20160625.bb:do_packagedata)<br>NOTE: recipe ncurses-6.0+20160625-r0: task do_packagedata: Started<br>NOTE: recipe ncurses-6.0+20160625-r0: task do_packagedata: Succeeded<br>NOTE: Running task 2461 of 4212 (/home/poky/meta/recipes-core/readline/readline_6.3.bb:do_package)<br>NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_package: Succeeded<br>NOTE: Running task 2462 of 4212 (/home/poky/meta/recipes-graphics/jpeg/libjpeg-turbo_1.5.0.bb:do_packagedata)<br>NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_packagedata: Started<br>NOTE: recipe libjpeg-turbo-1_1.5.0-r0: task do_packagedata: Succeeded<br>NOTE: Running task 2463 of 4212 (/home/poky/meta/recipes-multimedia/libvorbis/libvorbis_1.3.5.bb:do_package)<br>NOTE: recipe readline-6.3-r0: task do_package: Started<br>NOTE: recipe libvorbis-1.3.5-r0: task do_package: Started<br>---------------------------------------------------------<br><br></span></div><div><span style="font-family:monospace,monospace">The "$HOME/.xsession-errors.old" file shows the message:<br>---------------------------------------------------------<br>Script for ibus started at run_im.<br>Script for auto started at run_im.<br>Script for default started at run_im.<br>init: at-spi2-registryd main process ended, respawning<br>init: at-spi2-registryd main process ended, respawning<br>init: at-spi2-registryd main process ended, respawning<br>init: at-spi2-registryd respawning too fast, stopped<br>init: indicator-messages main process (17542) killed by SEGV signal<br>init: indicator-messages main process ended, respawning<br>init: update-notifier-crash (/var/crash/_usr_lib_x86_64-linux-gnu_indicator-messages_indicator-messages-service.1000.crash) main process (18792) terminated with status 1<br>init: update-notifier-crash (/var/crash/_usr_share_apport_apport-gtk.1000.crash) main process (21151) terminated with status 1<br>init: unity-panel-service-lockscreen main process (29904) killed by KILL signal<br>---------------------------------------------------------<br><br></span></div><div><span style="font-family:monospace,monospace">It appears that lightdm is unable the handle the SIGNAL and restarting when it receives them. Some of the most anticipated bugfixes patches for lightdm yet to arrive in ubuntu-14.04.6 which are not released yet can be found here:<br><br><a href="https://launchpad.net/lightdm/+milestone/1.10.7">https://launchpad.net/lightdm/+milestone/1.10.7</a><br><br></span></div><div><span style="font-family:monospace,monospace">Current version of lightdm in ubuntu-14.04.4/5 -> 1.10.6<br><br></span></div><div><span style="font-family:monospace,monospace">Thanks,<br></span></div><div><span style="font-family:monospace,monospace">Srikant</span><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 26, 2016 at 6:59 PM, srikanth krishnakar <span dir="ltr"><<a href="mailto:skrishnakar@gmail.com" target="_blank">skrishnakar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><span style="font-family:monospace,monospace">Hello Richard,<br><br></span></div><span style="font-family:monospace,monospace">bitbake | cat shows that when this logout happened during build, log file captured below packages in process: <br><br>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>--<br>NOTE: Running task 1886 of 4212 (/home/builder/poky/meta/<wbr>recipes-graphics/xorg-proto/<wbr>kbproto_1.0.7.bb:do_<wbr>packagedata)<br>NOTE: recipe kbproto-1_1.0.7-r0: task do_packagedata: Started<br>NOTE: recipe kbproto-1_1.0.7-r0: task do_packagedata: Succeeded<br>NOTE: Running task 1887 of 4212 (/home/builder/poky/meta/<wbr>recipes-support/libffi/libffi_<wbr>3.2.1.bb:do_package)<br>NOTE: recipe ncurses-6.0+20160625-r0: task do_package: Started<br>NOTE: recipe libffi-3.2.1-r0: task do_package: Started<br>NOTE: recipe libffi-3.2.1-r0: task do_package: Succeeded<br>NOTE: Running task 1888 of 4212 (/home/builder/poky/meta/<wbr>recipes-support/libffi/libffi_<wbr>3.2.1.bb:do_packagedata)<br>NOTE: recipe libffi-3.2.1-r0: task do_packagedata: Started<br>NOTE: recipe libffi-3.2.1-r0: task do_packagedata: Succeeded<br>NOTE: Running task 1889 of 4212 (/home/builder/poky/meta/<wbr>recipes-extended/bzip2/bzip2_<wbr>1.0.6.bb:do_package)<br>NOTE: recipe bzip2-1.0.6-r5: task do_package: Started<br>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>-----<br><br></span></div><span style="font-family:monospace,monospace">Also there was a crash file generated in "/var/crash" folder: /var/crash/_usr_lib_<wbr>accountsservice_accounts-<wbr>daemon.0.crash<br><br></span></div><span style="font-family:monospace,monospace">That has following information in it: <br>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>-------<br>ProblemType: Crash<br>Architecture: amd64<br>Date: Mon Dec 26 18:23:22 2016<br>DistroRelease: Ubuntu 14.04<br>ExecutablePath: /usr/lib/accountsservice/<wbr>accounts-daemon<br>ExecutableTimestamp: 1478200365<br>ProcCmdline: /usr/lib/accountsservice/<wbr>accounts-daemon<br>ProcCwd: /<br>ProcEnviron:<br>ProcMaps:<br> 00400000-00426000 r-xp 00000000 08:01 2626520 <wbr> /usr/lib/accountsservice/<wbr>accounts-daemon<br> 00625000-00628000 r--p 00025000 08:01 2626520 <wbr> /usr/lib/accountsservice/<wbr>accounts-daemon<br> 00628000-00629000 rw-p 00028000 08:01 2626520 <wbr> /usr/lib/accountsservice/<wbr>accounts-daemon<br> 024aa000-0252a000 rw-p 00000000 00:00 0 <wbr> [heap]<br> 7fe460000000-7fe460022000 rw-p 00000000 00:00 0<br> 7fe460022000-7fe464000000 ---p 00000000 00:00 0<br> 7fe464000000-7fe464021000 rw-p 00000000 00:00 0<br> 7fe464021000-7fe468000000 ---p 00000000 00:00 0<br> 7fe469f56000-7fe469f60000 r-xp 00000000 08:01 1839849 /lib/x86_64-linux-gnu/<a href="http://libnss_files-2.19.so" target="_blank">libnss_<wbr>files-2.19.so</a><br> 7fe469f60000-7fe46a15f000 ---p 0000a000 08:01 1839849 /lib/x86_64-linux-gnu/<a href="http://libnss_files-2.19.so" target="_blank">libnss_<wbr>files-2.19.so</a><br> 7fe46a15f000-7fe46a160000 r--p 00009000 08:01 1839849 /lib/x86_64-linux-gnu/<a href="http://libnss_files-2.19.so" target="_blank">libnss_<wbr>files-2.19.so</a><br>...<br>...<br> 7fe474b3e000-7fe474b40000 rw-p 00000000 00:00 0<br> 7fe474b40000-7fe474b41000 r--p 00022000 08:01 1839750 /lib/x86_64-linux-gnu/<a href="http://ld-2.19.so" target="_blank">ld-2.19.<wbr>so</a><br> 7fe474b41000-7fe474b42000 rw-p 00023000 08:01 1839750 /lib/x86_64-linux-gnu/<a href="http://ld-2.19.so" target="_blank">ld-2.19.<wbr>so</a><br> 7fe474b42000-7fe474b43000 rw-p 00000000 00:00 0<br> 7ffcaca64000-7ffcaca85000 rw-p 00000000 00:00 0 [stack]<br> 7ffcacaf5000-7ffcacaf7000 r--p 00000000 00:00 0 [vvar]<br> 7ffcacaf7000-7ffcacaf9000 r-xp 00000000 00:00 0 [vdso]<br> ffffffffff600000-<wbr>ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]<br>ProcStatus:<br> Name: accounts-daemon<br> State: D (disk sleep)<br> Tgid: 1248<br> Ngid: 0<br> Pid: 1248<br> PPid: 1<br> TracerPid: 0<br> Uid: 0 0 0 0<br> Gid: 0 0 0 0<br> FDSize: 64<br> Groups: 0<br> NStgid: 1248<br> NSpid: 1248<br> NSpgid: 795<br> NSsid: 795<br> VmPeak: 302404 kB<br> VmSize: 302368 kB<br> VmPin: 0 kB<br> VmHWM: 10128 kB<br> VmRSS: 4464 kB<br> VmData: 221944 kB<br> VmStk: 136 kB<br> VmExe: 152 kB<br> VmLib: 10140 kB<br> VmPTE: 200 kB<br> VmPMD: 12 kB<br> VmSwap: 2976 kB<br> HugetlbPages: 0 kB<br> Threads: 3<br> SigQ: 0/31670<br> SigPnd: 0000000000000000<br> ShdPnd: 0000000000000000<br> SigBlk: 0000000000000000<br> SigIgn: 0000000000001000<br> SigCgt: 0000000180004002<br> CapInh: 0000000000000000<br> CapPrm: 0000003fffffffff<br> CapEff: 0000003fffffffff<br> CapBnd: 0000003fffffffff<br> CapAmb: 0000000000000000<br> Seccomp: 0<br> Cpus_allowed: ff<br> Cpus_allowed_list: 0-7<br> Mems_allowed: 00000000,00000001<br> Mems_allowed_list: 0<br> voluntary_ctxt_switches: <wbr> 152<br> nonvoluntary_ctxt_switches: <wbr> 2<br>Signal: 7<br>Uname: Linux 4.4.0-57-generic x86_64<br>UserGroups:<br>CoreDump: base64<br>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>-------<br><br></span><div><div><span style="font-family:monospace,monospace">My machine is: <br><br></span></div><div><span style="font-family:monospace,monospace"><b>Quad-Core:</b> (0-8)<br></span></div><div><span style="font-family:monospace,monospace">------------------------------<wbr>---------<br>$ cat /proc/cpuinfo <br>processor : 0<br>vendor_id : GenuineIntel<br>cpu family : 6<br>model : 42<br>model name : Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz<br>-----<br>$ cat /proc/meminfo<br>MemTotal: 8132472 kB<br>------------------------------<wbr>----------<br><br></span></div><div><span style="font-family:monospace,monospace">When I checked free memory just before the logout was about "125MB" out of 8GB RAM. <br><br></span></div><div><span style="font-family:monospace,monospace">NOTE: The Ubuntu-14.04.4 that had older graphics stack seem to work normally without any issue. The "ubuntu-14.04.5" & "16.04" came with latest graphics stack & kernel with removal of non-opensource fglrx drivers. <br><br></span></div><div><span style="font-family:monospace,monospace">Thanks for your patience! <br><br>--<br></span></div><div><span style="font-family:monospace,monospace">Regards,<br></span></div><div><span style="font-family:monospace,monospace">Srikant</span><br></div><div><br></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 26, 2016 at 4:28 PM, srikanth krishnakar <span dir="ltr"><<a href="mailto:skrishnakar@gmail.com" target="_blank">skrishnakar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><font face="monospace, monospace">Hello Richard,</font><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">Sure, watching is best thing we can do, but it happens somewhere after 2900 tasks i.e just after linux-yocto. </font></div><div><font face="monospace, monospace">Screen recorders usually ask for file name and destination folder for saving the file, will try to see if it works as you said. </font></div><div><font face="monospace, monospace">"bitbake | cat" is the best method that we can get info from. </font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">The issue is noticeable only in ubuntu (unity) desktop's and not in Kubuntu (KDE), Ubuntu-gnome (Gnome-3) or Xubuntu (XFCE) desktops. </font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">Will fetch more details as per your suggestion. </font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">Thank you !</font></div></div><div class="m_55862884651501980HOEnZb"><div class="m_55862884651501980h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 26, 2016 at 4:06 PM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundatio<wbr>n.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_55862884651501980m_-395161690401130742HOEnZb"><div class="m_55862884651501980m_-395161690401130742h5">On Mon, 2016-12-26 at 15:11 +0530, srikanth krishnakar wrote:<br>
> Environment: Ubuntu-14.04.5/16.04.1 (64-bit)<br>
> Yocto build: qemuarm<br>
> Target image: core-image-sato<br>
> Error nature: The lightdm restarts on its own and logs out by killing<br>
> processes running and brings up a login UI. <br>
><br>
><br>
> We have been observing yocto-2.2 build failures on Ubuntu 14.04.5 and<br>
> Ubuntu-16.04.1 hosts due to restart of "lightdm" (Light Desktop<br>
> Manager) that is triggered by crash of "unity-settings-daemon", we<br>
> couldn't figure out any workaround so far to overcome the issue. The<br>
> build goes fine in the beginning but eventually the unity desktop<br>
> logs out and kills all the processes running in the user session<br>
> (including bitbake) and lands us into "Login screen" and when we<br>
> login its a new session where as the bitbake running in previous<br>
> session is killed and we need to continue the build. This is<br>
> happening consistently when the user logs into desktop via lightdm<br>
> and triggers a build. <br>
><br>
> Another interesting thing to notice is the build goes fine if we<br>
> connect to host via. SSH session and invoke a bitbake build. We are<br>
> suspecting on unity-settings-daemon that is crashing consistently and<br>
> is evident from the ".xsession-errors" log file as shown below:<br>
><br>
> builder@ubuntu:~$ cat .xsession-errors.old<br>
> Script for ibus started at run_im.<br>
> Script for auto started at run_im.<br>
> Script for default started at run_im.<br>
> init: Disconnected from notified D-Bus bus<br>
> init:"unity-settings-daemon main process (2076) terminated with<br>
> status 1"<br>
> init: indicator-bluetooth main process (2212) killed by TERM signal<br>
> init: indicator-power main process (2214) killed by TERM signal<br>
> init: indicator-datetime main process (2215) killed by TERM signal<br>
> init: indicator-printers main process (2222) killed by TERM signal<br>
> init: indicator-session main process (2245) killed by TERM signal<br>
> init: indicator-application main process (2270) killed by TERM signal<br>
><br>
> Corresponding unity-settings-daemon bug reported in Launchpad:<br>
><br>
> <a href="https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/" rel="noreferrer" target="_blank">https://bugs.launchpad.net/ubu<wbr>ntu/+source/unity-settings-dae<wbr>mon/+bug/</a><br>
> 1546641<br>
><br>
> Would anyone kindly confirm the logout behaviour during bitbake<br>
> process on Ubuntu-14.04.5 & Ubuntu-16.04.1 ? Since Yocto 2.2 mentions<br>
> both Ubuntu-14.04 & 16.04 as supported distributions this blocker<br>
> issue must be resolved at earliest. <br>
><br>
> Appreciate your Inputs !<br>
<br>
</div></div>What would really help is knowing what recipe is being built when this<br>
happens. There are a few ways you might be able to figure this out:<br>
<br>
a) Watching the screen to see which recipes were building when it<br>
happens<br>
b) Perhaps using some kind of screen recorder to automate this, you'd<br>
be able to review the recording to see when it breaks<br>
c) Looking at the bitbake/build logs to see what it was doing when the<br>
build broke (assuming bitbake stops when the session dies).<br>
<br>
"bitbake | cat" can provide better output for this since it will<br>
produce a scrolling log rather than the more interactive UI.<br>
<br>
Once you find the problematic recipe, a "bitbake XXX -c clean; bitbake<br>
XXX" should hopefully reproduce this more easily.<br>
<br>
Cheers,<br>
<br>
Richard<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>