Forum

Ethernet connection and UI crashed after close some built in application

Hi,
I have build webos recently. after install it to raspberrypi 4 B, it starts fine. it get crashed when I close some built in application (e.g. iotivity).
also I have connected a ethernet cable but it is not recognised as well.

I have attached the log of building. may be it helped.

webos@ares:~/mpoint/build-webos$ bitbake webos-image-devel

Parsing recipes: 100% |#############################################################################################################
Parsing of 2601 .bb files complete (0 cached, 2601 parsed). 3616 targets, 374 skipped, 44 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.40.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-18.04"
TARGET_SYS = "arm-webos-linux-gnueabi"
MACHINE = "raspberrypi4"
DISTRO = "webos"
DISTRO_VERSION = "1.0.g"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7"
TARGET_FPU = "hard"
WEBOS_DISTRO_RELEASE_CODENAME = "webos-master"
WEBOS_DISTRO_BUILD_ID = "unofficial"
WEBOS_DISTRO_TOPDIR_REVISION = "aec2e3ff82330bae9042b6e2a9375e52f47a7544"
WEBOS_DISTRO_TOPDIR_DESCRIBE = "v2.2.0"
DATETIME = "20200121094525"
meta-security = "thud:31dc4e7532fa7a82060e0b50e5eb8d0414aa7e93"
meta-webos-smack
meta-webos-virtualization
meta-webos-updater
meta-webos-raspberrypi = "master:4a41c96912f4ff12de2005064c716f9779372248"
meta-raspberrypi = "thud:4e5be97d75668804694412f9b86e9291edb38b9d"
meta-webos
meta-webos-backports-2.8
meta-webos-backports-2.7 = "master:4a41c96912f4ff12de2005064c716f9779372248"
meta-qt5 = "warrior:171871280307126c94faeeb90fb635a26495459d"
meta-virtualization = "thud:7685c7d415e0002c448007960837ae8898cd57a5"
meta-updater = "thud:0b087a34b708bfd808a013b3656f543d2709692e"
meta-filesystems
meta-python
meta-networking
meta-multimedia
meta-oe = "thud:446bd615fd7cb9bc7a159fe5c2019ed08d1a7a93"
meta = "thud:cd7cf933b3235560ec71576d8f3836dff736a39f"

Initialising tasks: 100% |##########################################################################################################
Sstate summary: Wanted 2479 Found 78 Missed 2401 Current 438 (3% match, 17% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: g-media-pipeline-1.0.0-21-r4 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-Add-raspberrypi4-and-raspberrypi4-64-targets.patch
patching file CMakeLists.txt
Hunk #1 succeeded at 34 with fuzz 1.

Now at patch 0001-Add-raspberrypi4-and-raspberrypi4-64-targets.patch
WARNING: connman-1.35-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0011-Provide-station-information-when-AP-mode.patch
patching file gsupplicant/gsupplicant.h
patching file gsupplicant/supplicant.c
patching file include/technology.h
patching file plugins/wifi.c
Hunk #1 succeeded at 3286 (offset -1 lines).
Hunk #2 succeeded at 3525 (offset -1 lines).
patching file src/connman.h
patching file src/manager.c
patching file src/technology.c
Hunk #1 succeeded at 2074 (offset -44 lines).
patching file src/tethering.c
Hunk #1 succeeded at 29 with fuzz 1.
Hunk #2 succeeded at 52 (offset -2 lines).
Hunk #3 succeeded at 63 (offset -2 lines).
Hunk #4 succeeded at 80 (offset -2 lines).
Hunk #5 succeeded at 749 (offset -2 lines).
Hunk #6 succeeded at 772 (offset -2 lines).

Now at patch 0011-Provide-station-information-when-AP-mode.patch
Currently 4 running tasks (4472 of 8085) 55% |####################################################################################WARNING: webos-image-devel-1.0-r2 do_image: Android repo tool not found; manifest not copied.
WARNING: webos-image-devel-1.0-r2 do_image_ostreepush: SOTA_PACKED_CREDENTIALS not set. Please add SOTA_PACKED_CREDENTIALS.
NOTE: Tasks Summary: Attempted 8085 tasks of which 2191 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Build completion summary:
NOTE: do_populate_sysroot: 0.0% sstate reuse(0 setscene, 395 scratch)
NOTE: do_package_qa: 6.1% sstate reuse(26 setscene, 399 scratch)
NOTE: do_package: 0.0% sstate reuse(0 setscene, 399 scratch)
NOTE: do_packagedata: 6.1% sstate reuse(26 setscene, 399 scratch)
NOTE: do_package_write_ipk: 6.1% sstate reuse(26 setscene, 399 scratch)
NOTE: do_populate_lic: 0.0% sstate reuse(0 setscene, 398 scratch)

Summary: There were 4 WARNING messages shown.

Thanks in advanced

Hi, @sas05,

Could you give the following informations?

Thanks

commit aec2e3ff82330bae9042b6e2a9375e52f47a7544
Ubuntu 19.04

I have only 100mbps ethernet connection, does it has any relation?

thanks

@sas05,

Sorry for the late reply (we had a lunar new year holiday.)

  • Unfortunately, we don't support the errors on Ubuntu 19.04. Could you do the same job with 18.04 or 16.04? (for the system requirements, see System Requirements.
    • If you suffer the same error with the 18.04 and 16.04, then we can discusss this issue with our dev team. Please understand our internal policy.
  • In my opinion, 100mbps ethernet is enough.

@sas05, Could you give us the following information?

  • How can we reproduce your issue? Can you describe it in detail?
  • Does the ethernet issue relate to the built-in application issue? Or is it independent with it?

Thanks

@NERGI,
I have build images on docker container. could it be a reason? I will try it on another network.

Regards

@sas05,
Did you solve this problem?
Docker might be a problem. Because we did not test webOS OSE on Docker.

Thanks,

No I couldn't try in another network.