[dss-merge-requests] Dev build failure
oebuild at builder.localdomain
oebuild at builder.localdomain
Sun Mar 15 03:46:26 CET 2020
Already up-to-date.
Synchronizing submodule url for 'OE/bitbake'
Synchronizing submodule url for 'OE/meta-angstrom'
Synchronizing submodule url for 'OE/meta-oe'
Synchronizing submodule url for 'OE/openembedded-core'
Synchronizing submodule url for 'org.openembedded.dev'
Synchronizing submodule url for 'yocto/poky-releases/2.5.1/layers/meta-freescale'
Synchronizing submodule url for 'yocto/poky-releases/2.5.1/layers/meta-fsl-arm'
Synchronizing submodule url for 'yocto/poky-releases/2.5.1/layers/meta-fsl-arm-extra'
Synchronizing submodule url for 'yocto/poky-releases/2.5.1/layers/meta-openembedded'
Synchronizing submodule url for 'yocto/poky-releases/2.5.1/layers/meta-swupdate'
Synchronizing submodule url for 'yocto/poky-releases/2.5.1/poky'
Synchronizing submodule url for 'yocto/poky-releases/2.7/layers/meta-freescale'
Synchronizing submodule url for 'yocto/poky-releases/2.7/layers/meta-openembedded'
Synchronizing submodule url for 'yocto/poky-releases/2.7/layers/meta-swupdate'
Synchronizing submodule url for 'yocto/poky-releases/2.7/poky'
RELEASE_TYPE:devel
VERSION:20200315033007
SEND_START_EMAIL:false
SEND_END_EMAIL:false
DO_BITBAKE:true
DO_USB_UPDATE:true
DO_UPLOAD:true
NO_PROMPT:true
MODE_ROOTFS:true
RS_UPLOAD_RESCUE:false
USB_UPDATE_WITH_CUTPOINT:false
Already up-to-date.
Images to be signed:
rescue-devel-update-20200314143008-dss20-20200314133257.swu
[INFO] Starting signing process...
rescue-devel-update-20200314143008-dss20-20200314133257.swu... signing
gpgsm: DBG: adding certificates at level -1
gpgsm: signature created
Images to be signed:
digitalstrom-devel-swupdate-image-20200313143008-dss20-20200313133416.swu
[INFO] Starting signing process...
digitalstrom-devel-swupdate-image-20200313143008-dss20-20200313133416.swu... signing
gpgsm: DBG: adding certificates at level -1
gpgsm: signature created
do_sign_release: success
Building images for devel feed
Configured feed: "devel"
Building configuration for targets/devel/rescue/dss20
[INFO] PACKAGES: update-info-file rescue-usbimage
NOTE: Started PRServer with DBfile: /mnt/vg1-oebuild/dss-oe/poky-rescue-devel-build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 46389, PID: 23442
Parsing recipes...WARNING: /mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb: LICENSE_linux-firmware-rt28x0 includes licenses (LICENCE.ralink-firmware.txt) that are not listed in LICENSE
WARNING: /mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb: LICENSE_linux-firmware-rt2561 includes licenses (LICENCE.ralink-firmware.txt) that are not listed in LICENSE
WARNING: /mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb: LICENSE_linux-firmware-rt2661 includes licenses (LICENCE.ralink-firmware.txt) that are not listed in LICENSE
done.
Parsing of 2196 .bb files complete (0 cached, 2196 parsed). 3264 targets, 350 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: preferred version 1.6.0+git% of rescue-system not available (for item rescue-system)
NOTE: versions of rescue-system available: git
NOTE: preferred version 1.6.0+git% of rescue-system not available (for item rescue-system-dev)
NOTE: versions of rescue-system available: git
Build Configuration:
BB_VERSION = "1.42.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal-4.8"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "dss20"
DISTRO = "poky"
DISTRO_VERSION = "2.7.1"
TUNE_FEATURES = "arm vfp cortexa9 neon thumb callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "HEAD:01b8a8b54bc569e5ef3f5e6fc6abcee365ab25d9"
meta-oe
meta-python
meta-networking
meta-webserver = "HEAD:8d5dcd6522e9d15e68637b6d7dda0401f9bb91d0"
meta-swupdate = "HEAD:d345ba975dc72e1674b2356ce01c50ac8f320f37"
meta-digitalstrom-rescue-devel = "master:415a291d69f0833db2fab8e7310876568a06f884"
Initialising tasks...done.
Sstate summary: Wanted 96 Found 94 Missed 2 Current 661 (97% match, 99% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running noexec task 2522 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usb-initramfs.bb:do_rm_work_all)
NOTE: Running noexec task 2649 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usb-initramfs.bb:do_fetch)
NOTE: Running task 2650 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usb-initramfs.bb:do_prepare_recipe_sysroot)
NOTE: Running task 2654 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-swuimage.bb:do_fetch)
NOTE: Running noexec task 2655 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_fetch)
NOTE: Running task 2656 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_prepare_recipe_sysroot)
NOTE: Running noexec task 2657 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_unpack)
NOTE: Running noexec task 2658 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_patch)
NOTE: Running task 2670 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_fetch)
NOTE: recipe update-info-file-0.1-r1: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-usbimage-1.0-r2: task do_fetch: Started
NOTE: recipe rescue-swuimage-1.0-r4: task do_fetch: Started
NOTE: recipe rescue-usb-initramfs-1.0-r7: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-usbimage-1.0-r2: task do_fetch: Succeeded
NOTE: recipe rescue-swuimage-1.0-r4: task do_fetch: Succeeded
NOTE: Running task 2671 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-swuimage.bb:do_prepare_recipe_sysroot)
NOTE: Running task 2672 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_prepare_recipe_sysroot)
NOTE: Running task 2673 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-swuimage.bb:do_unpack)
NOTE: Running task 2674 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_unpack)
NOTE: recipe rescue-usbimage-1.0-r2: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-swuimage-1.0-r4: task do_prepare_recipe_sysroot: Started
NOTE: recipe rescue-swuimage-1.0-r4: task do_unpack: Started
NOTE: recipe rescue-usbimage-1.0-r2: task do_unpack: Started
NOTE: recipe rescue-swuimage-1.0-r4: task do_unpack: Succeeded
NOTE: recipe rescue-usbimage-1.0-r2: task do_unpack: Succeeded
NOTE: recipe rescue-swuimage-1.0-r4: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 2685 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-swuimage.bb:do_swuimage)
NOTE: recipe rescue-swuimage-1.0-r4: task do_swuimage: Started
NOTE: recipe update-info-file-0.1-r1: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running noexec task 2686 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_configure)
NOTE: recipe rescue-swuimage-1.0-r4: task do_swuimage: Succeeded
NOTE: Running task 2687 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-swuimage.bb:do_rm_work)
NOTE: Running task 2688 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_compile)
NOTE: recipe rescue-swuimage-1.0-r4: task do_rm_work: Started
NOTE: recipe rescue-swuimage-1.0-r4: task do_rm_work: Succeeded
NOTE: recipe update-info-file-0.1-r1: task do_compile: Started
NOTE: recipe update-info-file-0.1-r1: task do_compile: Succeeded
NOTE: Running task 2689 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_deploy)
NOTE: recipe rescue-usbimage-1.0-r2: task do_prepare_recipe_sysroot: Succeeded
NOTE: recipe update-info-file-0.1-r1: task do_deploy: Started
NOTE: recipe update-info-file-0.1-r1: task do_deploy: Succeeded
NOTE: Running task 2702 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_rm_work)
NOTE: recipe update-info-file-0.1-r1: task do_rm_work: Started
NOTE: recipe update-info-file-0.1-r1: task do_rm_work: Succeeded
NOTE: Running noexec task 2703 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_rm_work_all)
NOTE: Running noexec task 2704 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-digitalstrom/update-info-file/update-info-file_0.1.bb:do_build)
NOTE: recipe rescue-usb-initramfs-1.0-r7: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 2710 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usb-initramfs.bb:do_rootfs)
NOTE: recipe rescue-usb-initramfs-1.0-r7: task do_rootfs: Started
NOTE: recipe rescue-usb-initramfs-1.0-r7: task do_rootfs: Succeeded
NOTE: Running task 2711 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usb-initramfs.bb:do_image_qa)
NOTE: recipe rescue-usb-initramfs-1.0-r7: task do_image_qa: Started
NOTE: recipe rescue-usb-initramfs-1.0-r7: task do_image_qa: Succeeded
NOTE: Running task 2715 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usb-initramfs.bb:do_populate_lic_deploy)
NOTE: recipe rescue-usb-initramfs-1.0-r7: task do_populate_lic_deploy: Started
NOTE: recipe rescue-usb-initramfs-1.0-r7: task do_populate_lic_deploy: Succeeded
NOTE: Running task 2716 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usb-initramfs.bb:do_rm_work)
NOTE: recipe rescue-usb-initramfs-1.0-r7: task do_rm_work: Started
NOTE: recipe rescue-usb-initramfs-1.0-r7: task do_rm_work: Succeeded
NOTE: Running noexec task 2717 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usb-initramfs.bb:do_build)
NOTE: Running task 2718 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_usbimage)
NOTE: recipe rescue-usbimage-1.0-r2: task do_usbimage: Started
NOTE: recipe rescue-usbimage-1.0-r2: task do_usbimage: Succeeded
NOTE: Running task 2719 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_rm_work)
NOTE: recipe rescue-usbimage-1.0-r2: task do_rm_work: Started
NOTE: recipe rescue-usbimage-1.0-r2: task do_rm_work: Succeeded
NOTE: Running noexec task 2720 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_rm_work_all)
NOTE: Running noexec task 2721 of 2721 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-rescue-devel/recipes-extended/images/rescue-usbimage.bb:do_build)
NOTE: Tasks Summary: Attempted 2721 tasks of which 2691 didn't need to be rerun and all succeeded.
NOTE: No commit since BUILDHISTORY_COMMIT != '1'
NOTE: Syncing deploy/images.
Summary: There were 3 WARNING messages shown.
[INFO] building package-index
NOTE: Started PRServer with DBfile: /mnt/vg1-oebuild/dss-oe/poky-rescue-devel-build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 36498, PID: 31155
Loading cache...done.
Loaded 3260 entries from dependency cache.
Parsing recipes...done.
Parsing of 2196 .bb files complete (2192 cached, 4 parsed). 3264 targets, 350 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.42.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal-4.8"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "dss20"
DISTRO = "poky"
DISTRO_VERSION = "2.7.1"
TUNE_FEATURES = "arm vfp cortexa9 neon thumb callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "HEAD:01b8a8b54bc569e5ef3f5e6fc6abcee365ab25d9"
meta-oe
meta-python
meta-networking
meta-webserver = "HEAD:8d5dcd6522e9d15e68637b6d7dda0401f9bb91d0"
meta-swupdate = "HEAD:d345ba975dc72e1674b2356ce01c50ac8f320f37"
meta-digitalstrom-rescue-devel = "master:415a291d69f0833db2fab8e7310876568a06f884"
Initialising tasks...done.
Sstate summary: Wanted 0 Found 0 Missed 0 Current 45 (0% match, 100% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running noexec task 354 of 358 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/meta/package-index.bb:do_rm_work_all)
NOTE: Running task 356 of 358 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/meta/package-index.bb:do_package_index)
NOTE: recipe package-index-1.0-r0: task do_package_index: Started
NOTE: recipe package-index-1.0-r0: task do_package_index: Succeeded
NOTE: Running task 357 of 358 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/meta/package-index.bb:do_rm_work)
NOTE: recipe package-index-1.0-r0: task do_rm_work: Started
NOTE: recipe package-index-1.0-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 358 of 358 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/meta/package-index.bb:do_build)
NOTE: Tasks Summary: Attempted 358 tasks of which 354 didn't need to be rerun and all succeeded.
NOTE: No commit since BUILDHISTORY_COMMIT != '1'
NOTE: Syncing deploy/images.
Configured feed: "devel"
Building configuration for targets/devel/rootfs/dss20
[INFO] PACKAGES: update-info-file
NOTE: Started PRServer with DBfile: /mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 39677, PID: 31411
Parsing recipes...WARNING: /mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-bsp/u-boot/u-boot-fw-utils-amlogic_2015.01.bb: Unable to get checksum for u-boot-fw-utils-amlogic-cross SRC_URI entry fw_env.config: file could not be found
WARNING: /mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-bsp/u-boot/u-boot-fw-utils-amlogic_2015.01.bb: Unable to get checksum for u-boot-fw-utils-amlogic-cross SRC_URI entry dssip_boot.patch: file could not be found
WARNING: /mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-bsp/u-boot/u-boot-fw-utils-amlogic_2015.01.bb: Unable to get checksum for u-boot-fw-utils-amlogic SRC_URI entry fw_env.config: file could not be found
WARNING: /mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-bsp/u-boot/u-boot-fw-utils-amlogic_2015.01.bb: Unable to get checksum for u-boot-fw-utils-amlogic SRC_URI entry dssip_boot.patch: file could not be found
WARNING: /mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb: LICENSE_linux-firmware-rt28x0 includes licenses (LICENCE.ralink-firmware.txt) that are not listed in LICENSE
WARNING: /mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb: LICENSE_linux-firmware-rt2561 includes licenses (LICENCE.ralink-firmware.txt) that are not listed in LICENSE
WARNING: /mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb: LICENSE_linux-firmware-rt2661 includes licenses (LICENCE.ralink-firmware.txt) that are not listed in LICENSE
done.
Parsing of 2550 .bb files complete (0 cached, 2550 parsed). 3667 targets, 467 skipped, 50 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.42.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal-4.8"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "dss20"
DISTRO = "poky"
DISTRO_VERSION = "2.7.1"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "HEAD:01b8a8b54bc569e5ef3f5e6fc6abcee365ab25d9"
meta-oe
meta-python
meta-networking
meta-webserver
meta-multimedia = "HEAD:8d5dcd6522e9d15e68637b6d7dda0401f9bb91d0"
meta-freescale = "HEAD:7f92a041728ad401f3b4a6025f96e493a20b229a"
meta-swupdate = "HEAD:d345ba975dc72e1674b2356ce01c50ac8f320f37"
meta-digitalstrom-devel = "master:415a291d69f0833db2fab8e7310876568a06f884"
Initialising tasks...done.
Sstate summary: Wanted 1622 Found 0 Missed 1622 Current 688 (0% match, 29% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running task 398 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/glibc/glibc_2.29.bb:do_compile)
NOTE: Running task 739 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-lua-extensions.bb:do_packagedata)
NOTE: Running task 741 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-compile.bb:do_packagedata)
NOTE: Running task 743 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-linux-5.1.7.bb:do_packagedata)
NOTE: Running task 745 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-addons.bb:do_packagedata)
NOTE: Running task 747 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-system-addons.bb:do_packagedata)
NOTE: Running task 749 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-core/tasks/task-vdcs.bb:do_packagedata)
NOTE: Running task 751 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/packagegroups/packagegroup-core-boot.bb:do_packagedata)
NOTE: recipe glibc-2.29-r0: task do_compile: Started
NOTE: recipe packagegroup-core-boot-1.0-r17: task do_packagedata: Started
NOTE: recipe task-linux-5.1.7-1.0-r0: task do_packagedata: Started
NOTE: recipe task-vdcs-1.0-r30: task do_packagedata: Started
NOTE: recipe task-addons-1.0-r9: task do_packagedata: Started
NOTE: recipe task-compile-1.0-r1: task do_packagedata: Started
NOTE: recipe task-system-addons-1.0-r11: task do_packagedata: Started
NOTE: recipe task-lua-extensions-1.0-r9: task do_packagedata: Started
NOTE: recipe packagegroup-core-boot-1.0-r17: task do_packagedata: Succeeded
NOTE: Running noexec task 798 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-kernel/kmod/kmod-native_git.bb:do_rm_work_all)
NOTE: Running noexec task 821 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/meson/meson_0.49.2.bb:do_rm_work_all)
NOTE: Running noexec task 832 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/meson/meson_0.49.2.bb:do_build)
NOTE: Running task 856 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/glib-2.0/glib-2.0_2.58.3.bb:do_compile)
NOTE: recipe glib-2.0-native-1_2.58.3-r0: task do_compile: Started
NOTE: recipe task-addons-1.0-r9: task do_packagedata: Succeeded
NOTE: Running task 902 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/autoconf-archive/autoconf-archive_2018.03.13.bb:do_packagedata)
NOTE: recipe autoconf-archive-2018.03.13-r0: task do_packagedata: Started
NOTE: recipe task-vdcs-1.0-r30: task do_packagedata: Succeeded
NOTE: Running task 913 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_packagedata)
NOTE: recipe base-files-3.0.14-r89: task do_packagedata: Started
NOTE: recipe task-linux-5.1.7-1.0-r0: task do_packagedata: Succeeded
NOTE: Running task 994 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/initscripts/initscripts_1.0.bb:do_packagedata)
NOTE: recipe initscripts-1.0-r155: task do_packagedata: Started
NOTE: recipe task-system-addons-1.0-r11: task do_packagedata: Succeeded
NOTE: Running task 1005 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb:do_packagedata)
NOTE: recipe update-rc.d-0.8-r0: task do_packagedata: Started
NOTE: recipe task-compile-1.0-r1: task do_packagedata: Succeeded
NOTE: Running noexec task 1085 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/libxml/libxml2_2.9.8.bb:do_build)
NOTE: Running task 1106 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/libxslt/libxslt_1.1.33.bb:do_prepare_recipe_sysroot)
NOTE: recipe libxslt-native-1.1.33-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe initscripts-1.0-r155: task do_packagedata: Succeeded
NOTE: Running task 1107 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/initscripts/initscripts_1.0.bb:do_package_qa)
NOTE: recipe initscripts-1.0-r155: task do_package_qa: Started
NOTE: recipe task-lua-extensions-1.0-r9: task do_packagedata: Succeeded
NOTE: Running task 1181 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.0.bb:do_package_write_ipk)
NOTE: recipe linux-libc-headers-5.0-r0: task do_package_write_ipk: Started
NOTE: recipe base-files-3.0.14-r89: task do_packagedata: Succeeded
NOTE: Running task 1182 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_package_qa)
NOTE: recipe initscripts-1.0-r155: task do_package_qa: Succeeded
NOTE: Running task 1183 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/initscripts/initscripts_1.0.bb:do_package_write_ipk)
NOTE: recipe base-files-3.0.14-r89: task do_package_qa: Started
NOTE: recipe initscripts-1.0-r155: task do_package_write_ipk: Started
NOTE: recipe initscripts-1.0-r155: task do_package_write_ipk: Succeeded
NOTE: Running task 1184 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/initscripts/initscripts_1.0.bb:do_rm_work)
NOTE: recipe base-files-3.0.14-r89: task do_package_qa: Succeeded
NOTE: Running task 1185 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_package_write_ipk)
NOTE: recipe initscripts-1.0-r155: task do_rm_work: Started
NOTE: recipe base-files-3.0.14-r89: task do_package_write_ipk: Started
NOTE: recipe base-files-3.0.14-r89: task do_package_write_ipk: Succeeded
NOTE: Running task 1186 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_rm_work)
NOTE: recipe base-files-3.0.14-r89: task do_rm_work: Started
NOTE: recipe autoconf-archive-2018.03.13-r0: task do_packagedata: Succeeded
NOTE: Running task 1187 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/autoconf-archive/autoconf-archive_2018.03.13.bb:do_package_qa)
NOTE: recipe autoconf-archive-2018.03.13-r0: task do_package_qa: Started
NOTE: recipe update-rc.d-0.8-r0: task do_packagedata: Succeeded
NOTE: Running task 1188 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb:do_package_qa)
NOTE: recipe update-rc.d-0.8-r0: task do_package_qa: Started
NOTE: recipe update-rc.d-0.8-r0: task do_package_qa: Succeeded
NOTE: Running task 1189 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb:do_package_write_ipk)
NOTE: recipe update-rc.d-0.8-r0: task do_package_write_ipk: Started
NOTE: recipe update-rc.d-0.8-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 1190 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb:do_rm_work)
NOTE: recipe update-rc.d-0.8-r0: task do_rm_work: Started
NOTE: recipe autoconf-archive-2018.03.13-r0: task do_package_qa: Succeeded
NOTE: Running task 1191 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/autoconf-archive/autoconf-archive_2018.03.13.bb:do_package_write_ipk)
NOTE: recipe autoconf-archive-2018.03.13-r0: task do_package_write_ipk: Started
NOTE: recipe autoconf-archive-2018.03.13-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 1192 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/autoconf-archive/autoconf-archive_2018.03.13.bb:do_rm_work)
NOTE: recipe autoconf-archive-2018.03.13-r0: task do_rm_work: Started
NOTE: recipe libxslt-native-1.1.33-r0: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 1193 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/libxslt/libxslt_1.1.33.bb:do_configure)
NOTE: recipe libxslt-native-1.1.33-r0: task do_configure: Started
NOTE: recipe glib-2.0-native-1_2.58.3-r0: task do_compile: Succeeded
NOTE: Running task 1194 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/glib-2.0/glib-2.0_2.58.3.bb:do_install)
NOTE: recipe glib-2.0-native-1_2.58.3-r0: task do_install: Started
NOTE: recipe linux-libc-headers-5.0-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 1195 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.0.bb:do_rm_work)
NOTE: recipe linux-libc-headers-5.0-r0: task do_rm_work: Started
NOTE: recipe update-rc.d-0.8-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 1196 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb:do_rm_work_all)
NOTE: Running noexec task 1197 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb:do_build)
NOTE: Running noexec task 1264 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-kernel/kmod/kmod-native_git.bb:do_build)
NOTE: Running task 1294 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-kernel/linux/linux-5.1.7_5.1.7.bb:do_kernel_configcheck)
NOTE: recipe linux-5.1.7-5.1.7-r0: task do_kernel_configcheck: Started
NOTE: recipe initscripts-1.0-r155: task do_rm_work: Succeeded
NOTE: Running noexec task 1295 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/initscripts/initscripts_1.0.bb:do_rm_work_all)
NOTE: Running noexec task 1296 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/initscripts/initscripts_1.0.bb:do_build)
NOTE: Running task 1452 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/swig/swig_3.0.12.bb:do_populate_sysroot)
NOTE: recipe swig-native-3.0.12-r0: task do_populate_sysroot: Started
NOTE: recipe glib-2.0-native-1_2.58.3-r0: task do_install: Succeeded
NOTE: Running task 1453 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/glib-2.0/glib-2.0_2.58.3.bb:do_populate_sysroot)
NOTE: recipe glib-2.0-native-1_2.58.3-r0: task do_populate_sysroot: Started
NOTE: recipe base-files-3.0.14-r89: task do_rm_work: Succeeded
NOTE: Running noexec task 1454 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_rm_work_all)
NOTE: Running noexec task 1455 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_build)
NOTE: Running task 1577 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/timezone/tzdata.bb:do_packagedata)
NOTE: recipe tzdata-2019a-r0: task do_packagedata: Started
NOTE: recipe glib-2.0-native-1_2.58.3-r0: task do_populate_sysroot: Succeeded
NOTE: Running task 1578 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/glib-2.0/glib-2.0_2.58.3.bb:do_rm_work)
NOTE: recipe glib-2.0-native-1_2.58.3-r0: task do_rm_work: Started
NOTE: recipe autoconf-archive-2018.03.13-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 1579 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/autoconf-archive/autoconf-archive_2018.03.13.bb:do_build)
NOTE: Running task 1581 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/qemu/qemu-native_3.1.0.bb:do_prepare_recipe_sysroot)
NOTE: recipe qemu-native-3.1.0-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe libxslt-native-1.1.33-r0: task do_configure: Succeeded
NOTE: Running task 1582 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/libxslt/libxslt_1.1.33.bb:do_compile)
NOTE: recipe libxslt-native-1.1.33-r0: task do_compile: Started
NOTE: recipe qemu-native-3.1.0-r0: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 1583 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/qemu/qemu-native_3.1.0.bb:do_configure)
NOTE: recipe qemu-native-3.1.0-r0: task do_configure: Started
NOTE: recipe libxslt-native-1.1.33-r0: task do_compile: Succeeded
NOTE: Running task 1584 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/libxslt/libxslt_1.1.33.bb:do_install)
NOTE: recipe libxslt-native-1.1.33-r0: task do_install: Started
NOTE: recipe tzdata-2019a-r0: task do_packagedata: Succeeded
NOTE: Running task 1585 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/timezone/tzdata.bb:do_package_qa)
NOTE: recipe tzdata-2019a-r0: task do_package_qa: Started
NOTE: recipe libxslt-native-1.1.33-r0: task do_install: Succeeded
NOTE: Running task 1586 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/timezone/tzdata.bb:do_package_write_ipk)
NOTE: recipe tzdata-2019a-r0: task do_package_write_ipk: Started
NOTE: recipe glib-2.0-native-1_2.58.3-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 1587 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/glib-2.0/glib-2.0_2.58.3.bb:do_build)
NOTE: Running noexec task 1588 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/shared-mime-info/shared-mime-info_1.10.bb:do_rm_work_all)
NOTE: Running noexec task 1589 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_rm_work_all)
NOTE: Running noexec task 1590 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/qemu/qemu-native_3.1.0.bb:do_rm_work_all)
NOTE: Running task 1591 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/libxslt/libxslt_1.1.33.bb:do_populate_sysroot)
NOTE: recipe libxslt-native-1.1.33-r0: task do_populate_sysroot: Started
NOTE: recipe libxslt-native-1.1.33-r0: task do_populate_sysroot: Succeeded
NOTE: Running task 1592 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/libxslt/libxslt_1.1.33.bb:do_rm_work)
NOTE: recipe qemu-native-3.1.0-r0: task do_configure: Succeeded
NOTE: Running task 1593 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/qemu/qemu-native_3.1.0.bb:do_compile)
NOTE: recipe libxslt-native-1.1.33-r0: task do_rm_work: Started
NOTE: recipe qemu-native-3.1.0-r0: task do_compile: Started
NOTE: recipe libxslt-native-1.1.33-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 1594 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/libxslt/libxslt_1.1.33.bb:do_build)
NOTE: Running noexec task 1595 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/layers/meta-openembedded/meta-python/recipes-devtools/python/python-lxml_4.3.3.bb:do_rm_work_all)
NOTE: Running task 1596 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_prepare_recipe_sysroot)
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe swig-native-3.0.12-r0: task do_populate_sysroot: Succeeded
NOTE: Running task 1597 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/swig/swig_3.0.12.bb:do_rm_work)
NOTE: recipe swig-native-3.0.12-r0: task do_rm_work: Started
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 1598 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_configure)
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_configure: Started
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_configure: Succeeded
NOTE: Running task 1599 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile)
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_compile: Started
NOTE: recipe tzdata-2019a-r0: task do_package_qa: Succeeded
NOTE: Running task 1600 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/layers/meta-openembedded/meta-python/recipes-devtools/python/python-lxml_4.3.3.bb:do_prepare_recipe_sysroot)
NOTE: recipe tzdata-2019a-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 1601 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/timezone/tzdata.bb:do_rm_work)
NOTE: recipe tzdata-2019a-r0: task do_rm_work: Started
NOTE: recipe python-lxml-native-4.3.3-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe python-lxml-native-4.3.3-r0: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 1602 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/layers/meta-openembedded/meta-python/recipes-devtools/python/python-lxml_4.3.3.bb:do_configure)
NOTE: recipe python-lxml-native-4.3.3-r0: task do_configure: Started
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_compile: Succeeded
NOTE: Running task 1603 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_install)
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_install: Started
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_install: Succeeded
NOTE: Running task 1604 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_populate_sysroot)
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_populate_sysroot: Started
NOTE: recipe python-lxml-native-4.3.3-r0: task do_configure: Succeeded
NOTE: Running task 1605 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/layers/meta-openembedded/meta-python/recipes-devtools/python/python-lxml_4.3.3.bb:do_compile)
NOTE: recipe python-lxml-native-4.3.3-r0: task do_compile: Started
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_populate_sysroot: Succeeded
NOTE: Running task 1606 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_rm_work)
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_rm_work: Started
NOTE: recipe gobject-introspection-native-1.58.3-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 1607 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_build)
NOTE: Running task 1645 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb:do_package)
NOTE: recipe ca-certificates-20190110-r0: task do_package: Started
NOTE: recipe tzdata-2019a-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 1646 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/timezone/tzdata.bb:do_rm_work_all)
NOTE: Running noexec task 1647 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/timezone/tzdata.bb:do_build)
NOTE: Running task 1661 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-system-addons/framework/addon-framework_git.bb:do_package)
NOTE: recipe addon-framework-git-r2: task do_package: Started
NOTE: recipe swig-native-3.0.12-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 1662 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/swig/swig_3.0.12.bb:do_build)
NOTE: Running task 1669 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/shared-mime-info/shared-mime-info_1.10.bb:do_prepare_recipe_sysroot)
NOTE: recipe shared-mime-info-native-1.10-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe shared-mime-info-native-1.10-r0: task do_prepare_recipe_sysroot: Succeeded
NOTE: Running task 1673 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/shared-mime-info/shared-mime-info_1.10.bb:do_configure)
NOTE: recipe shared-mime-info-native-1.10-r0: task do_configure: Started
NOTE: recipe shared-mime-info-native-1.10-r0: task do_configure: Succeeded
NOTE: Running task 1674 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/shared-mime-info/shared-mime-info_1.10.bb:do_compile)
NOTE: recipe shared-mime-info-native-1.10-r0: task do_compile: Started
NOTE: recipe ca-certificates-20190110-r0: task do_package: Succeeded
NOTE: Running task 1675 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb:do_packagedata)
NOTE: recipe ca-certificates-20190110-r0: task do_packagedata: Started
NOTE: recipe ca-certificates-20190110-r0: task do_packagedata: Succeeded
NOTE: Running task 1711 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/shadow/shadow-securetty_4.6.bb:do_package)
NOTE: recipe shadow-securetty-4.6-r3: task do_package: Started
NOTE: recipe shared-mime-info-native-1.10-r0: task do_compile: Succeeded
NOTE: Running task 1713 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-support/shared-mime-info/shared-mime-info_1.10.bb:do_install)
NOTE: recipe shared-mime-info-native-1.10-r0: task do_install: Started
NOTE: recipe qemu-native-3.1.0-r0: task do_compile: Succeeded
NOTE: Running task 1714 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/qemu/qemu-native_3.1.0.bb:do_install)
NOTE: recipe qemu-native-3.1.0-r0: task do_install: Started
NOTE: recipe addon-framework-git-r2: task do_package: Succeeded
NOTE: Running task 1715 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-system-addons/framework/addon-framework_git.bb:do_packagedata)
NOTE: recipe addon-framework-git-r2: task do_packagedata: Started
NOTE: recipe qemu-native-3.1.0-r0: task do_install: Succeeded
NOTE: Running task 1716 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/qemu/qemu-native_3.1.0.bb:do_populate_sysroot)
NOTE: recipe qemu-native-3.1.0-r0: task do_populate_sysroot: Started
NOTE: recipe shadow-securetty-4.6-r3: task do_package: Succeeded
NOTE: Running task 1717 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/shadow/shadow-securetty_4.6.bb:do_packagedata)
NOTE: recipe shadow-securetty-4.6-r3: task do_packagedata: Started
NOTE: recipe addon-framework-git-r2: task do_packagedata: Succeeded
NOTE: Running task 1718 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-system-addons/framework/addon-framework_git.bb:do_package_qa)
NOTE: recipe addon-framework-git-r2: task do_package_qa: Started
NOTE: recipe python-lxml-native-4.3.3-r0: task do_compile: Succeeded
NOTE: Running task 1719 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-system-addons/framework/addon-framework_git.bb:do_package_write_ipk)
NOTE: recipe addon-framework-git-r2: task do_package_write_ipk: Started
WARNING: addon-framework-git-r2 do_package_qa: QA Issue: addon-framework: /addon-framework/www/pages/framework/ds_gui.css is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/jpicker/images/preview-opacity.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/jpicker/images/Bars.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/jpicker/images/picker.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/jpicker/images/rangearrows.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/jpicker/images/bar-opacity.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/jpicker/images/NoColor.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/jpicker/images/map-opacity.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/jpicker/images/mappoint.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/jpicker/images/AlphaBar.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/jpicker/images/Maps.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/t.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_0.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_7_deact.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_64_active.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_2.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/usergroup_cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/usergroup_white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_6.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_64.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_6_deact.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/usergroup_grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/usergroup_red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_7.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/usergroup_black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/usergroup_green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_1_active.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_1_deact.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_3_deact.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_2_active.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_1.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_2_deact.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_64_deact.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_8.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_6_active.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/usergroup_magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_5.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_4_deact.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_7_active.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_4_active.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/usergroup_yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_3_active.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/usergroup_blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_2_scene_5.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_5_deact.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_4.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_5_active.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_1_auto_off.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_9.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/groupIcons/group_3.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/door_out.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/stop.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/delete.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/missing.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/lightbulb.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/email.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/bedingung_aktiv.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/pause.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/start.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/date_condition.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/right.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/door_in.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/down.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/lightning.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/agt_login.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/bell.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/up.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/ds_logo.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/time_condition.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/trash_deact.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/trash.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/agt_resume.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/weekday_condition.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/edit.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/offline.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/clock_red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/reload.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/left.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/checkbox.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/bedingung_inaktiv.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/lightbulb_off.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/rainbow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/offline.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/cord_m/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/cord_m/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/cord_m/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/cord_m/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/cord_m/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/cord_m/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/cord_m/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/cord_m/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/cord_m/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/colors/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/colors/rainbow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/colors/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/colors/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/colors/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/colors/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/colors/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/colors/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/colors/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/colors/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_l/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_l/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_l/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_l/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_l/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_l/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_l/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_l/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_l/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/button_m/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/button_m/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/button_m/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/button_m/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/button_m/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/button_m/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/button_m/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/button_m/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/button_m/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_m/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_m/rainbow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_m/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_m/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_m/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_m/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_m/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_m/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_m/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/coupler_m/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_l/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_l/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_l/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_l/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_l/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_l/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_l/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_l/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_l/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/button_m/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/button_m/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/button_m/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/button_m/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/button_m/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/button_m/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/button_m/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/button_m/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/button_m/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_m/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_m/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_m/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_m/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_m/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_m/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_m/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_m/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/coupler_m/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/adapter/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/adapter/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/adapter/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/adapter/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/adapter/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/adapter/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/adapter/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/adapter/rot.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/joker/adapter/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/adapter/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/adapter/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/adapter/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/adapter/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/adapter/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/adapter/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/adapter/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/adapter/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/dss/coupler/adapter/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/copy.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/delete.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/export.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/deactivate.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/add.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/right.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/activate.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/down.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/refresh.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/up.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/trash.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/edit.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/test.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/buttonIcons/left.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/default/star_cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/default/star_blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/default/star_red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/default/star_yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/default/star_green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/default/star_black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/default/star_grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/default/star_white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/default/star_magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/black_red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/black_grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/black_blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/black_black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/black_magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/black_white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/black_yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/black_cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/kl/black_green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/black_red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/black_grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/black_blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/black_magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/black_white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/black_yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/black_cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sdm/black_green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/black_red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/black_grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/black_blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/black_black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/black_magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/black_white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/black_yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/black_cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/tkm/black_green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/km/black_green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/akm/sensor.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/black_red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/black_grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/black_blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/black_black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/black_magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/black_white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/black_yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/black_cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/zws/black_green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/black_red.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/black_grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/black_blue.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/black_black.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/grey.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/black_magenta.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/black_white.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/black_yellow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/black_cyan.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/deviceIcons/sds/black_green.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/alarm2.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/panic.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/daynight_indoors_false.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/alarm2_No.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/door-open.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/sun.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/malfunction_no.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/simulation_off.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/malfunction.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/window-open.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/frost_no.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/hail_No.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/rain.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/operation_lock.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/heating_mode_cooling.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/fire.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/sun_no.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/wind.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/service.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/akm_service_no.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/present.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/heating_mode_auto.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/alarm_No.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/akm_service.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/present_No.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/heating_mode_heating.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/sensor.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/alarm3_No.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/wind_No.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/fire_No.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/rain_No.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/daynight_true.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/daynight_false.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/window-tilted.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/daynight_indoors_true.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/uds_state_active.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/door-closed.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/simulation_on.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/daylight_true.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/heating_mode_off.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/operation_lock_no.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/panic_No.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/service_no.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/daylight_false.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/alarm.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/hail.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/frost.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/uds_state_inactive.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/sensor_No.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/window-closed.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/alarm4.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/alarm4_No.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/state/alarm3.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_bell.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_fire.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_alarm1.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_on.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_panic.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_fire.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_sun_protection.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_blink.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_absent.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_stop.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_33.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_rain.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_sleeping.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_75.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_deep_off.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_wakeup.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_norain.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_panic.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_alarm3.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_alarm2.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_25.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_alarm1.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_alarm4.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_sun_protection.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_alarm3.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_present.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_alarm2.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/undo_scene_alarm4.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_50.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_66.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse_off.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_standby.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/images/sceneIcons/scene_impulse.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/DINWeb-Medium.woff is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/fontawesome-webfont.woff is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/fontawesome-webfont.svg is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/fontawesome-webfont.ttf is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/DINNext-Regular.woff is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/fontawesome-webfont.eot is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/FontAwesome.otf is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/DINWeb.woff is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/fonts/fontawesome-webfont.woff2 is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/images/ds_logo.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/css/dss-responsive-ui.css is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/dss-responsive-ui.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/foundation.min.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/jquery.min.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/modernizr.custom.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/polyfill.min.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/motion-ui/motion-ui.min.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/responsive-ui/js/vendor/motion-ui/motion-ui.min.css is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/locale.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-json.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-stores.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-wizard-dialog.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-datamodel.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-edit-dialog.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-property-tree.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-grid.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-types.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-addon-framework.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-timespan-control.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-twitter-message-control.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-condition-selector.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-message-control.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-device-selector.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-radiogroup.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-weekday-selection.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-timereference-control.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-dateedit-control.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-trigger-selector.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-textedit-control.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-action-selector.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/dss/dss-components/dss-combobox.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/jsgettext/Gettext.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/gpl-3.0.txt is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/ext-all.js is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/README-dSS-layout is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/license.txt is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/ext-theme-classic-all.css is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/boundlist/trigger-arrow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/progress/progress-default-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/slider/slider-bg.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/slider/slider-v-bg.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/slider/slider-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/slider/slider-v-thumb.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/slider/slider-v-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/slider/slider-thumb.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/slider/slider-thumb.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/slider/slider-v-thumb.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/editor/tb-sprite.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-pressed-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-disabled-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-disabled-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-pressed-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-over-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-pressed-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-pressed-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-disabled-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-over-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-focus-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-over-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-pressed-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-disabled-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-over-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-focus-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-focus-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-disabled-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-focus-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-focus-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-disabled-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-disabled-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-focus-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-over-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-over-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-disabled-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-over-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-focus-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-focus-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-over-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-pressed-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-focus-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-over-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-focus-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-disabled-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-over-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-over-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-focus-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-over-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-over-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-focus-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-over-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-disabled-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-focus-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-focus-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-focus-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-disabled-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-disabled-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-focus-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-pressed-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-focus-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-disabled-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-focus-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-pressed-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-pressed-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-over-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-over-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-focus-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-focus-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-pressed-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-pressed-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-pressed-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-pressed-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-over-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-disabled-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-pressed-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-pressed-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-disabled-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-over-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-pressed-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-pressed-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-focus-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-pressed-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-focus-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-pressed-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-disabled-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-over-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-small-over-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-focus-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-over-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-large-over-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-medium-pressed-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-pressed-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-over-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-over-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-pressed-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-toolbar-large-pressed-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-disabled-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-disabled-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-small-pressed-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn/btn-default-medium-focus-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab-bar/default-scroll-bottom-left.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab-bar/default-scroll-left-top.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab-bar/tab-bar-default-top-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab-bar/default-scroll-bottom-right.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab-bar/default-scroll-right-top.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab-bar/default-scroll-top-right.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab-bar/default-scroll-top-left.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab-bar/default-scroll-left-bottom.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab-bar/default-scroll-right-bottom.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tools/tool-sprite-tpl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tools/tools-sprites-trans.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tools/tool-sprites.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/layout/mini-bottom.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/layout/mini-right.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/layout/mini-left.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/layout/mini-top.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/toolbar/more.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/toolbar/scroll-right.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/toolbar/more-left.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/toolbar/scroll-left.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/toolbar/toolbar-default-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel/panel-default-framed-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel/panel-default-framed-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-collapsed-left-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-bottom-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-collapsed-right-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-right-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-left-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-bottom-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-collapsed-left-corners-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-top-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-collapsed-top-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-collapsed-top-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-left-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-right-corners-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-top-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-collapsed-bottom-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-collapsed-right-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-collapsed-bottom-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-left-corners-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-collapsed-left-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-collapsed-right-corners-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window-header/window-header-default-right-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/footer-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/pick-button.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/column-header-over-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/row-expand-sprite.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/page-prev.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/dirty-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/refresh-disabled.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/hmenu-lock.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/hmenu-asc.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/group-expand-sprite.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/page-first-disabled.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/grid-blue-split.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/invalid_line.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/row-over.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/mso-hd.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/grid-hrow.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/sort-hd.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/row-sel.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/grid-loading.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/hmenu-unlock.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/col-move-bottom.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/page-first.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/wait.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/page-last.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/grid-split.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/property-cell-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/col-move-top.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/arrow-right-white.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/columns.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/row-check-sprite.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/cell-special-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/hmenu-unlock.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/hmenu-desc.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/group-collapse.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/page-prev-disabled.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/grid3-hd-btn-left.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/drop-yes.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/arrow-left-white.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/drop-no.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/grid-blue-hd.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/cell-special-selected-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/grid3-hrow-over.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/dd-insert-arrow-left.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/done.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/property-cell-selected-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/page-next-disabled.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/refresh.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/grid-vista-hd.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/page-next.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/cell-special-selected-bg.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/dd-insert-arrow-right.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/page-last-disabled.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/dd-insert-arrow-left.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/grid3-hd-btn.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/nowait.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/column-header-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/grid3-rowheader.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/sort_asc.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/sort_desc.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/grid3-hrow.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/hd-pop.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/hmenu-lock.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/dirty.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/loading.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/cell-special-bg.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/group-expand.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/dd-insert-arrow-right.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid/group-by.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/menu/checked.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/menu/group-checked.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/menu/menu-item-active-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/menu/scroll-bottom.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/menu/menu-parent.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/menu/menu-parent-left.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/menu/menu.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/menu/unchecked.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/menu/item-over.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/menu/scroll-top.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/drop-above.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/arrows-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/folder.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-plus.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/folder-open.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/arrows.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-end-minus.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/s.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-minus-nl-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-end-plus.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/drop-under.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/drop-between.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-minus.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/drop-add.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-minus-nl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/drop-below.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-end.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/leaf.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/drop-yes.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/drop-no.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/drop-append.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/drop-over.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-plus-nl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-end-plus-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-end-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-line-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-plus-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-plus-nl-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/folder-open-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/leaf-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/loading.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-line.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-end-minus-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/folder-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tree/elbow-minus-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window/window-default-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/window/window-default-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid-row-editor-buttons/null-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/grid-row-editor-buttons/null-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/datepicker/datepicker-header-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/datepicker/datepicker-footer-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/s-arrow-bo.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/group-tb.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/group-cs.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/s-arrow-noline.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/s-arrow-light.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/s-arrow-o.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/arrow.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/s-arrow-b-noline.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/s-arrow-b.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/s-arrow-o-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/group-lr.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/s-arrow-noline-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/s-arrow.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/s-arrow-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/btn.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/button/s-arrow-light-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tip/tip-default-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tip/tip-form-invalid-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tip/tip-default-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tip/tip-form-invalid-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn-group/btn-group-default-framed-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn-group/btn-group-default-framed-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn-group/btn-group-default-framed-notitle-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/btn-group/btn-group-default-framed-notitle-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/dd/drop-add.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/dd/drop-yes.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/dd/drop-no.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-right-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-top-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-left-bg-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-bottom-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-bottom-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-right-bg-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-left-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-left-sides-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-right-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-right-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-left-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-left-bg-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-bottom-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-right-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-right-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-bottom-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-left-sides-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-right-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-right-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-left-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-bottom-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-bottom-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-right-corners-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-left-fbg-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-left-fbg-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-left-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-left-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-right-sides-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-left-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-left-corners-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-bottom-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-right-sides-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-left-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-bottom-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-right-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-right-fbg-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-top-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-top-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-left-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-right-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-right-bg-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-top-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-left-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-top-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-left-bg-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-right-bg-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-right-corners-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-top-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-top-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-top-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-collapsed-bottom-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-left-corners-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-top-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/panel-header/panel-header-default-framed-right-fbg-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/se-handle.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/e-handle.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/e-handle-dark.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/nw-handle-dark.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/sw-handle-dark.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/se-handle-dark.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/sw-handle.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/square.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/ne-handle-dark.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/s-handle.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/s-handle-dark.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/nw-handle.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/sizer/ne-handle.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/date-trigger.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/spinner-small.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/trigger-tpl-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/text-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/error-tip-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/trigger-square.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/radio.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/clear-trigger-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/exclamation.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/trigger-square-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/spinner.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/search-trigger-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/checkbox.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/date-trigger-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/trigger-tpl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/trigger.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/clear-trigger.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/spinner-small-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/spinner-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/trigger-rtl.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/form/search-trigger.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/box/r-blue.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/box/corners-blue.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/box/l-blue.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/box/corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/box/l.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/box/r.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/box/tb.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/box/tb-blue.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-disabled-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-disabled-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-active-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-active-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-active-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-over-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-active-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-disabled-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-active-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-disabled-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-disabled-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-over-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-over-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-disabled-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-active-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-close.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-over-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-active-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-over-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-disabled-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-active-sides.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-disabled-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-over-fbg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-over-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-top-over-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/tab/tab-default-bottom-corners.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/icon-question.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/loading-balls.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/warning.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/icon-info.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/right-btn.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/icon-error.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/blue-loading.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/large-loading.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/calendar.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/glass-bg.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/hd-sprite.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/left-btn.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/icon-warning.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/shadow-c.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/shadow-lr.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/shared/shadow.png is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/util/splitter/mini-bottom.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/util/splitter/mini-right.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/util/splitter/mini-left.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/ext-theme-classic/images/util/splitter/mini-top.gif is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/js/ext/resources/css/ext-all.css is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/en_pseudo/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/tr_TR/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/it_IT/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/da_DK/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/de_DE/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/fr_CH/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/en_US/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/nb_NO/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/pl_PL/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/templates/dss-addon-framework.pot is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/sv_SE/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/pt_PT/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination
addon-framework: /addon-framework/www/pages/framework/locale/nl_NL/dss-addon-framework.po is owned by uid 1001, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: recipe shadow-securetty-4.6-r3: task do_packagedata: Succeeded
NOTE: Running task 1720 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/shadow/shadow-securetty_4.6.bb:do_package_qa)
NOTE: recipe shadow-securetty-4.6-r3: task do_package_qa: Started
NOTE: recipe addon-framework-git-r2: task do_package_qa: Succeeded
NOTE: Running task 1721 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/shadow/shadow-securetty_4.6.bb:do_package_write_ipk)
NOTE: recipe shadow-securetty-4.6-r3: task do_package_write_ipk: Started
NOTE: recipe shadow-securetty-4.6-r3: task do_package_qa: Succeeded
NOTE: Running task 1722 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/layers/meta-openembedded/meta-python/recipes-devtools/python/python-lxml_4.3.3.bb:do_install)
NOTE: recipe python-lxml-native-4.3.3-r0: task do_install: Started
NOTE: recipe qemu-native-3.1.0-r0: task do_populate_sysroot: Succeeded
NOTE: Running task 1723 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-devtools/qemu/qemu-native_3.1.0.bb:do_rm_work)
NOTE: recipe qemu-native-3.1.0-r0: task do_rm_work: Started
NOTE: recipe shadow-securetty-4.6-r3: task do_package_write_ipk: Succeeded
NOTE: Running task 1724 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/shadow/shadow-securetty_4.6.bb:do_rm_work)
NOTE: recipe shadow-securetty-4.6-r3: task do_rm_work: Started
NOTE: recipe addon-framework-git-r2: task do_package_write_ipk: Succeeded
NOTE: Running task 1725 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-system-addons/framework/addon-framework_git.bb:do_rm_work)
NOTE: recipe addon-framework-git-r2: task do_rm_work: Started
NOTE: recipe addon-framework-git-r2: task do_rm_work: Succeeded
NOTE: Running noexec task 1726 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-system-addons/framework/addon-framework_git.bb:do_rm_work_all)
NOTE: Running noexec task 1727 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-system-addons/framework/addon-framework_git.bb:do_build)
NOTE: Running task 1800 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-api/dsdata_git.bb:do_package)
NOTE: recipe shadow-securetty-4.6-r3: task do_rm_work: Succeeded
NOTE: Running noexec task 1801 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/shadow/shadow-securetty_4.6.bb:do_rm_work_all)
NOTE: Running noexec task 1802 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-extended/shadow/shadow-securetty_4.6.bb:do_build)
NOTE: Running task 1816 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-support/create-certificate/create-certificate_0.6.0.bb:do_package)
NOTE: recipe create-certificate-0.6.0-r7: task do_package: Started
NOTE: recipe dsdata-git-r1: task do_package: Started
NOTE: recipe python-lxml-native-4.3.3-r0: task do_install: Succeeded
NOTE: Running task 1817 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/layers/meta-openembedded/meta-python/recipes-devtools/python/python-lxml_4.3.3.bb:do_populate_sysroot)
NOTE: recipe python-lxml-native-4.3.3-r0: task do_populate_sysroot: Started
NOTE: recipe python-lxml-native-4.3.3-r0: task do_populate_sysroot: Succeeded
NOTE: Running task 1818 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/layers/meta-openembedded/meta-python/recipes-devtools/python/python-lxml_4.3.3.bb:do_rm_work)
NOTE: recipe python-lxml-native-4.3.3-r0: task do_rm_work: Started
NOTE: recipe python-lxml-native-4.3.3-r0: task do_rm_work: Succeeded
NOTE: Running noexec task 1819 of 6952 (virtual:native:/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/layers/meta-openembedded/meta-python/recipes-devtools/python/python-lxml_4.3.3.bb:do_build)
NOTE: Running task 1875 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-support/ntp/synchwclock_0.3.bb:do_package)
NOTE: recipe synchwclock-0.3-r10: task do_package: Started
NOTE: recipe create-certificate-0.6.0-r7: task do_package: Succeeded
NOTE: Running task 1876 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-support/create-certificate/create-certificate_0.6.0.bb:do_packagedata)
NOTE: recipe dsdata-git-r1: task do_package: Succeeded
NOTE: Running task 1877 of 6952 (/mnt/vg1-oebuild/dss-oe/yocto/dS/meta-digitalstrom-devel/recipes-digitalstrom/dsm-api/dsdata_git.bb:do_packagedata)
NOTE: recipe create-certificate-0.6.0-r7: task do_packagedata: Started
ERROR: glibc-2.29-r0 do_compile: oe_runmake failed
ERROR: glibc-2.29-r0 do_compile: Function failed: do_compile (log file is located at /mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/temp/log.do_compile.32663)
ERROR: Logfile of failure stored in: /mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/temp/log.do_compile.32663
Log data follows:
| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
| DEBUG: Executing shell function do_compile
| NOTE: make PARALLELMFLAGS=-j 8 SHELL=/bin/bash
| make -r PARALLELMFLAGS="-j 8" -C ../git objdir=`pwd` all
| make[1]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git'
| make -j 8 subdir=csu -C csu ..=../ subdir_lib
| make -j 8 subdir=iconv -C iconv ..=../ subdir_lib
| make -j 8 subdir=locale -C locale ..=../ subdir_lib
| make -j 8 subdir=localedata -C localedata ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/localedata'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/localedata'
| make -j 8 subdir=iconvdata -C iconvdata ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/iconvdata'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/iconvdata'
| make -j 8 subdir=assert -C assert ..=../ subdir_lib
| make -j 8 subdir=ctype -C ctype ..=../ subdir_lib
| make -j 8 subdir=intl -C intl ..=../ subdir_lib
| make -j 8 subdir=catgets -C catgets ..=../ subdir_lib
| make -j 8 subdir=math -C math ..=../ subdir_lib
| make -j 8 subdir=setjmp -C setjmp ..=../ subdir_lib
| make -j 8 subdir=signal -C signal ..=../ subdir_lib
| make -j 8 subdir=stdlib -C stdlib ..=../ subdir_lib
| make -j 8 subdir=stdio-common -C stdio-common ..=../ subdir_lib
| make -j 8 subdir=libio -C libio ..=../ subdir_lib
| make -j 8 subdir=dlfcn -C dlfcn ..=../ subdir_lib
| make -j 8 subdir=malloc -C malloc ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/malloc'
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/malloc'
| make -j 8 subdir=string -C string ..=../ subdir_lib
| make -j 8 subdir=wcsmbs -C wcsmbs ..=../ subdir_lib
| make -j 8 subdir=timezone -C timezone ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/timezone'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/timezone'
| make -j 8 subdir=time -C time ..=../ subdir_lib
| make -j 8 subdir=dirent -C dirent ..=../ subdir_lib
| make -j 8 subdir=grp -C grp ..=../ subdir_lib
| make -j 8 subdir=pwd -C pwd ..=../ subdir_lib
| make -j 8 subdir=posix -C posix ..=../ subdir_lib
| make -j 8 subdir=io -C io ..=../ subdir_lib
| make -j 8 subdir=termios -C termios ..=../ subdir_lib
| make -j 8 subdir=resource -C resource ..=../ subdir_lib
| make -j 8 subdir=misc -C misc ..=../ subdir_lib
| make -j 8 subdir=socket -C socket ..=../ subdir_lib
| make -j 8 subdir=sysvipc -C sysvipc ..=../ subdir_lib
| make -j 8 subdir=gmon -C gmon ..=../ subdir_lib
| make -j 8 subdir=gnulib -C gnulib ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/gnulib'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/gnulib'
| make -j 8 subdir=wctype -C wctype ..=../ subdir_lib
| make -j 8 subdir=manual -C manual ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/manual'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/manual'
| make -j 8 subdir=shadow -C shadow ..=../ subdir_lib
| make -j 8 subdir=gshadow -C gshadow ..=../ subdir_lib
| make -j 8 subdir=po -C po ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/po'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/po'
| make -j 8 subdir=argp -C argp ..=../ subdir_lib
| make -j 8 subdir=nptl -C nptl ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/nptl'
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/nptl'
| make -j 8 subdir=rt -C rt ..=../ subdir_lib
| make -j 8 subdir=conform -C conform ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/conform'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/conform'
| make -j 8 subdir=debug -C debug ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/debug'
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/debug'
| make -j 8 subdir=mathvec -C mathvec ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/mathvec'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/mathvec'
| make -j 8 subdir=support -C support ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/support'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/support'
| make -j 8 subdir=nptl_db -C nptl_db ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/nptl_db'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/nptl_db'
| make -j 8 subdir=inet -C inet ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/inet'
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/inet'
| make -j 8 subdir=resolv -C resolv ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/resolv'
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/resolv'
| make -j 8 subdir=nss -C nss ..=../ subdir_lib
| make -j 8 subdir=hesiod -C hesiod ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/hesiod'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/hesiod'
| make -j 8 subdir=sunrpc -C sunrpc ..=../ subdir_lib
| make -j 8 subdir=nis -C nis ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/nis'
| make[2]: Nothing to be done for 'subdir_lib'.
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/nis'
| make -j 8 subdir=nscd -C nscd ..=../ subdir_lib
| make -j 8 subdir=streams -C streams ..=../ subdir_lib
| make -j 8 subdir=login -C login ..=../ subdir_lib
| make -j 8 subdir=elf -C elf ..=../ subdir_lib
| make[2]: Entering directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/elf'
| arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard --sysroot=/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/recipe-sysroot -fuse-ld=bfd -nostdlib -nostartfiles -r -o /mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/build-arm-poky-linux-gnueabi/elf/librtld.map.o \
| '-Wl,-(' /mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/build-arm-poky-linux-gnueabi/elf/dl-allobjs.os /mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/build-arm-poky-linux-gnueabi/libc_pic.a -lgcc '-Wl,-)' -Wl,-Map,/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/build-arm-poky-linux-gnueabi/elf/librtld.mapT
| /mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-ERROR: oe_runmake failed
| poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/8.3.0/ld.bfd: cannot find -lgcc
| collect2: error: ld returned 1 exit status
| make[2]: *** [Makefile:456: /mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/build-arm-poky-linux-gnueabi/elf/librtld.map] Error 1
| make[2]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git/elf'
| make[1]: *** [Makefile:278: elf/subdir_lib] Error 2
| make[1]: Leaving directory '/mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/git'
| make: *** [Makefile:9: all] Error 2
| WARNING: /mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/temp/run.do_compile.32663:1 exit 1 from 'exit 1'
| ERROR: Function failed: do_compile (log file is located at /mnt/vg1-oebuild/dss-oe/poky-devel-nopkg-build/build/work/armv7at2hf-neon-poky-linux-gnueabi/glibc/2.29-r0/temp/log.do_compile.32663)
NOTE: recipe glibc-2.29-r0: task do_compile: Failed
NOTE: recipe dsdata-git-r1: task do_packagedata: Started
ERROR: Task (/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/glibc/glibc_2.29.bb:do_compile) failed with exit code '1'
NOTE: recipe dsdata-git-r1: task do_packagedata: Succeeded
NOTE: recipe create-certificate-0.6.0-r7: task do_packagedata: Succeeded
NOTE: recipe linux-libc-headers-5.0-r0: task do_rm_work: Succeeded
NOTE: recipe synchwclock-0.3-r10: task do_package: Succeeded
NOTE: recipe qemu-native-3.1.0-r0: task do_rm_work: Succeeded
NOTE: recipe shared-mime-info-native-1.10-r0: task do_install: Succeeded
NOTE: recipe linux-5.1.7-5.1.7-r0: task do_kernel_configcheck: Succeeded
NOTE: Tasks Summary: Attempted 1878 tasks of which 1769 didn't need to be rerun and 1 failed.
NOTE: No commit since BUILDHISTORY_COMMIT != '1'
NOTE: Syncing deploy/images.
Summary: 1 task failed:
/mnt/vg1-oebuild/dss-oe/yocto/feedconfig/devel/poky/meta/recipes-core/glibc/glibc_2.29.bb:do_compile
Summary: There were 8 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
bitbake returned 1, manual interaction required!
[Sun Mar 15 03:46:25 CET 2020] Build failed
More information about the dSS-merge-requests
mailing list