Image location: http://autobuilder.yoctoproject.org/pub/nightly/20130813-3/machines/p1022ds/ Git rev: poky: master/ff10f72abda52315b892c64f711096772d9a4c1c meta-fsl-ppc: master/399c1ab5e86cf6dbb7c0c48d5253ac8798d6bfe4 The desktop matchbox can not startup on sato-sdk image. When boot up the image, the following messages would show: ################## Poky Next (Yocto Project Reference Distro) 1.4+snapshot-20130813 p1022ds /dev/ttyS0 p1022ds login: D-BUS per-session daemon address is: unix:abstract=/tmp/dbus-muMV9QSAEu,guid=11bc79ce36449e273e9227304c60c9d5 matchbox: Cant find a keycode for keysym 269025056 matchbox: ignoring key shortcut XF86Calendar=!$contacts matchbox: Cant find a keycode for keysym 2809 matchbox: ignoring key shortcut telephone=!$dates matchbox: Cant find a keycode for keysym 269025050 matchbox: ignoring key shortcut XF86Start=!matchbox-remote -desktop ** (matchbox-panel:2148): WARNING **: Failed to load applet "battery" (/usr/lib/matchbox-panel/libbattery.so: cannot open shared object file: No such file or directory). [settings daemon] Forking. run with -n to prevent fork Invalid XSETTINGS property (read off end) Invalid XSETTINGS property (read off end) Timeout waiting for org.matchbox_project.desktop.Loaded Poky Next (Yocto Project Reference Distro) 1.4+snapshot-20130813 p1022ds /dev/ttyS0 p1022ds login: Poky Next (Yocto Project Reference Distro) 1.4+snapshot-20130813 p1022ds /dev/ttyS0 ######################## The X and matchbox processes are all running, but now desktop on the screen: ################## root@p1022ds:~# root@p1022ds:~# ps | grep X 2035 root 3720 S xinit /etc/X11/Xsession -- /usr/bin/Xorg :0 -br -pn 2038 root 24540 S < /usr/bin/Xorg :0 -br -pn 2158 root 2648 S grep X root@p1022ds:~# root@p1022ds:~# ps | grep matchbox 2092 root 8368 S matchbox-window-manager -theme Sato -use_desktop_mod 2113 root 7236 S matchbox-keyboard -d 2148 root 50176 S matchbox-panel --titlebar --start-applets showdeskto 2160 root 2648 S grep matchbox root@p1022ds:~# root@p1022ds:~# ##################
My u-boot args: ######### => printenv baudrate=115200 bdev=sda3 bootargs=root=/dev/nfs rw nfsroot=128.224.162.200:/export/pxeboot/rootfs ip=128.224.162.252:128.224.162.200:128.224.162.1:255.255.254.0:p1022ds:eth0:off console=ttyS0,115200 diufb=15M v ideo=fslfb:1024x768-32@60,monitor=1 tty0 debug bootcmd=setenv bootargs root=/dev/sda3 rw console=ttyS0,115200; bootm ec000000 - eff00000 bootdelay=10 bootfile=uImage consoledev=ttyS0 diuerr=md e002c014 1 dium=mw e002c01c diuregs=md e002c000 1d eth1addr=00:04:9F:01:BE:70 ethact=eTSEC1 ethaddr=00:04:9F:01:BE:6F fdtaddr=c00000 fdtfile=p1022ds.dtb flashboot=setenv bootargs root=/dev/ram rw console=ttyS0,115200;bootm ec000000 e8000000 eff00000 gatewayip=128.224.162.1 hostname=p1022ds hwconfig=audclk:12 ipaddr=128.224.162.252 loadaddr=1000000 loads_echo=1 memctl_intlv_ctl=2 monitor=1-LVDS mynfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=dhcp console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr netdev=eth0 netmask=255.255.254.0 nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $load addr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr othbootargs=diufb=15M video=fslfb:800x600-24@60,monitor=1 tty0 debug cache-sram=0xfff00000,0x8000 partition=0:3 perf_mode=stable ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdi skaddr $fdtaddr ramdiskaddr=2000000 ramdiskfile=uramdisk rootpath=/export/pxeboot/rootfs serverip=128.224.162.215 stderr=serial stdin=serial stdout=serial tftpflash=tftpboot $loadaddr $uboot; protect off 0xeff80000 +$filesize; erase 0xeff80000 +$filesize; cp.b $loadaddr 0xeff80000 $filesize; protect on 0xeff80000 +$filesize; cmp.b $loadad dr 0xeff80000 $filesize uboot=u-boot.bin Environment size: 2060/8188 bytes ############## Boot up via nfs: run mynfsboot
Created attachment 1426 [details] Xorg.0.log
Created attachment 1427 [details] dmesg log
poky: master/ff10f72abda52315b892c64f711096772d9a4c1c meta-fsl-ppc: master/399c1ab5e86cf6dbb7c0c48d5253ac8798d6bfe4 I build core-image-sato-sdk in Fedora release 13 (Goddard) the desktop matchbox can boot up with my build image. but the matchbox can not startup with autobuilder image (http://autobuilder.yoctoproject.org/pub/nightly/20130813-3/machines/p1022ds/). I found this in matchbox-keyboard init script if [ "$CMD" ]; then # Delay to make sure the window manager is active # by waiting for the desktop to say its finished loading dbus-wait org.matchbox_project.desktop Loaded exec $CMD fi please enable the option " Event interface " in kernel . Are you sure that usb mouse and keyboard can work? Do you try again the image which you build in your host ?
Hi, I did more testings for this issue. I built an image in local with a clean build and there is no this issue. It is not the kernel issue, even if I disabled the "Event interface" option, the matchbox-desktop still could start up. I found the libcairo caused this problem. Here is the libcairo information from the autobuilder: ######### root@p1022ds:~# ls -l /usr/lib/libcairo.so.2.11200.14 -rwxr-xr-x 1 root root 1134904 Aug 13 23:15 /usr/lib/libcairo.so.2.11200.14 root@p1022ds:~# root@p1022ds:~# ldd /usr/lib/libcairo.so.2.11200.14 linux-vdso32.so.1 (0x00100000) libpthread.so.0 => /lib/libpthread.so.0 (0x0fde0000) libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x0efd0000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x0f6f0000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0x0f610000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x0f650000) libpng16.so.16 => /usr/lib/libpng16.so.16 (0x0f5c0000) libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0x0f3c0000) libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x0eea0000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0x0f5a0000) libXext.so.6 => /usr/lib/libXext.so.6 (0x0f7d0000) libX11.so.6 => /usr/lib/libX11.so.6 (0x0f800000) libxcb.so.1 => /usr/lib/libxcb.so.1 (0x0f950000) libXau.so.6 => /usr/lib/libXau.so.6 (0x0f9a0000) libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x0f980000) libdl.so.2 => /lib/libdl.so.2 (0x0ffa0000) libz.so.1 => /lib/libz.so.1 (0x0fdb0000) librt.so.1 => /lib/librt.so.1 (0x0fd90000) libm.so.6 => /lib/libm.so.6 (0x0fc40000) libc.so.6 => /lib/libc.so.6 (0x0fe10000) /lib/ld.so.1 (0x20248000) ######### I replaced this file with my local build. This issue disappeared. Here is the libcairo information from my local build: ######### root@p1022ds:~# ls -l /usr/lib/libcairo.so.2.11200.14 -rwxr-xr-x 1 root root 1122604 Aug 19 2013 /usr/lib/libcairo.so.2.11200.14 root@p1022ds:~# root@p1022ds:~# ldd /usr/lib/libcairo.so.2.11200.14 linux-vdso32.so.1 (0x00100000) libpthread.so.0 => /lib/libpthread.so.0 (0x0fde0000) libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x0efd0000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x0f6f0000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0x0f610000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x0f650000) libpng16.so.16 => /usr/lib/libpng16.so.16 (0x0f5c0000) libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0x0f3c0000) libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0x0eea0000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0x0f5a0000) libXext.so.6 => /usr/lib/libXext.so.6 (0x0f7d0000) libX11.so.6 => /usr/lib/libX11.so.6 (0x0f800000) libxcb.so.1 => /usr/lib/libxcb.so.1 (0x0f950000) libXau.so.6 => /usr/lib/libXau.so.6 (0x0f9a0000) libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x0f980000) libdl.so.2 => /lib/libdl.so.2 (0x0ffa0000) libz.so.1 => /lib/libz.so.1 (0x0fdb0000) librt.so.1 => /lib/librt.so.1 (0x0fd90000) libm.so.6 => /lib/libm.so.6 (0x0fc40000) libc.so.6 => /lib/libc.so.6 (0x0fe10000) /lib/ld.so.1 (0x20292000) root@p1022ds:~# ############### My local build host is Ubuntu 12.04 x86_64. I will try to build it again in Fedora 19. Is that a sstate issue in autobuilder ?
hello, image locatin: http://autobuilder.yoctoproject.org/pub/nightly/20130816-2/machines/p1022ds/ Thhere is no issue in autobuilder. I think that it is not a sstate issue.
The issue is caused by old caches. Recent image can work well.
I rebuilt the image on Fedora19 x86_64 host. There is no this issue.
(In reply to comment #8) > I rebuilt the image on Fedora19 x86_64 host. There is no this issue. Thanks for the confirmation.