Bug 12138

Summary: [master] the icon on the connection manager appears without connection in Eclipse Plugin
Product: [Build System, Metadata & Runtime] OE-Core Reporter: oscar lopez arandas <oscarx.lopez.arandas>
Component: connectivityAssignee: David Reyna <david.reyna>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: Medium CC: brian.avery, ioanax.grigoropol, javierx.zepeda.murguia, meta.mr.watcher, meta.watcher, randy.macleod, yp.bsp.watcher, yp.ep.watcher, yp.watcher
Version: 2.4   
Target Milestone: 4.99   
Hardware: x86   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
qemux86 desktop
none
connman connection icon , top right corner, to the left of the time none

Description oscar lopez arandas 2017-09-28 16:49:08 UTC 
Created attachment 4033 [details]
qemux86 desktop

launch the eclipse plugin for qemux86, there is the icon in X for "Connection Manager", but it can connect to network.

BUILD:2.4 M4: rc1-592c3449697ce39bf07864fafd7f0a61ca230561
ENVIRONMENT: ubuntu 1604

https://autobuilder.yocto.io/pub/releases/yocto-2.4.rc1/machines/qemu/qemux86/core-image-sato-sdk-qemux86-20170926152146.rootfs.tar.bz2

STEPS:
   1.  Set the Yocto ADT's toolchain root location, sysroot location and kernel, in the menu Window -> Preferences -> Yocto ADT.
  2.  wget  autobuilder.yoctoproject.org/pub/releases/<yocto-version>/machines/qemu/qemux86/qemu (ex:core-image-sato-sdk-qemux86-date-rootfs-tar-bz2)

source /opt/poky/version/environment-setup-i585-poky-linux

Extract qemu with runqemu-extract-sdk /home/user/file(ex.core-image-sato-qemux86.bz2) /home/user/qemux86-sato

(a)Point to the Toolchain:
If you are using a stand-alone pre-built toolchain, you should be pointing to the /opt/poky/{test-version} directory as Toolchain Root Location. This is the default location for toolchains installed by the ADT Installer or by hand. If ADT is installed in other location, use that location as Toolchain location.
If you are using a system-derived toolchain, the path you provide for the Toolchain Root Location field is the Yocto Project's build directory.
           E.g:”/home/user/yocto/poky/build”
(b)Specify the Sysroot Location:
Sysroot Location is the location where the root filesystem for the target hardware is created on the development system by the ADT Installer (SYSROOT in step 2 of the case ADT installer Installation).   
         Local :     e.g: “/home/user/qemux86-sato”
Using ADT : e.g :/home/”user”/test-yocto/qemux86

   1. (c)Select the Target Architecture:
    The target architecture is the type of hardware you are going to use or emulate. Use the pull-down Target Architecture menu to make your selection.

    (d) QEMU:
    Select this option if you will be using the QEMU emulator. Specify the Kernel matching the QEMU architecture you are using.
     2.     wget  autobuilder.yoctoproject.org/pub/releases/<yocto-version>/machines/qemu/qemux86/bzImage-qemux86.bin 

      e.g:” /home/$USER/yocto/adt-installer/download_image/bzImage-qemux86.bin”

(e) select OK to save the settings.

    1.In the Eclipse toolbar, expose the Run -> External Tools menu. Your image should appear as a selectable menu item.

   2. Select your image in the navigation pane to launch the emulator in a new window.

   3. If needed, enter your host root password in the shell window at the prompt. This sets up a Tap 0 connection needed for running in user-space NFS mode.

EXPECTED OUTCOME:
Qemu can be lauched normally.

ACTUAL OUTCOME:
Qemu can be started normally, but the icon in the connection manager appears offline, it is possible to have connection only the ico error appears in X.

NOTES:
qemux86 desktop in attachment
Comment 1 brian avery 2017-10-05 14:35:06 UTC 
could you clarify what icon you are referring too? I'm not following.
Comment 2 oscar lopez arandas 2017-10-05 15:01:00 UTC 
(In reply to comment #1)
> could you clarify what icon you are referring too? I'm not following.

when launching the eclipse plugin, within eclipse opens qemux86, and the icon in X for "Connection Manager", but if it can be connected to the network. open the images in the attachment there it looks clear
Comment 3 Javier Zepeda 2017-10-10 20:05:52 UTC 
I came across with the same bug as well. It is being shown when qemu is using a NFS configuration.

yocto-2.4.rc2
HEAD: da05a01423a60a23cd1073eb0ad3776e5bf4f2a8

To reproduce, check the procedure below:
https://wiki.yoctoproject.org/wiki/Yocto_QEMU_UNFS_test_procedure

Note: Once qemu is up, it has IP and it's able to do a ping correctly on CLI, but the connection manager seems to be unable graphically.
Comment 4 brian avery 2017-10-16 23:18:17 UTC 
How do you access the connection manager? I am not sure what you mean by "connection manager" but i do not use it in my testing.  Menu->XXX???

I'm still confused as to what icon we are talking about. if the icon appears on the picture could you please circle it and attach the circled image?

I typically just start qemu with external tools run as. then I make a new ssh connection with the appropriate ip address.

Was this neon? oxygen?
Comment 5 brian avery 2017-10-17 00:57:45 UTC 
clarification:
For connection manager, you mean ConnMan inside of qemu, yes?

Furthermore, by icon,  do you mean the red circle with the slash though it that is inside the QEMU window to the left of the clock reading 16:48? The red circle overlays the icon that looks like a mouse or a ethernet jack, is that correct?

If it is, then we should start a unfsd session from the command line, verify that the bug still occurs, and file it against connman. Since it is then a general connman bug wrt a unfsd qemu setup.
Comment 6 oscar lopez arandas 2017-10-17 15:46:18 UTC 
(In reply to comment #5)
> clarification:
> For connection manager, you mean ConnMan inside of qemu, yes?
> 
> Furthermore, by icon,  do you mean the red circle with the slash though it
> that is inside the QEMU window to the left of the clock reading 16:48? The
> red circle overlays the icon that looks like a mouse or a ethernet jack, is
> that correct?
> 
> If it is, then we should start a unfsd session from the command line, verify
> that the bug still occurs, and file it against connman. Since it is then a
> general connman bug wrt a unfsd qemu setup.

yes is correct, For connection manager, i  mean ConnMan inside of qemu, im goin traid to reproduce start a unfsd session from the command line
Comment 7 brian avery 2017-10-31 21:09:50 UTC 
Created attachment 4111 [details]
connman connection icon , top right corner, to the left of the time

Shows the broken connman connection icon in a closeup. the connection icon has a ghostbusters (red circle with a slash) on top of it.
Comment 8 brian avery 2017-10-31 21:13:38 UTC 
Changing to an oe-core bug. The broken connection icon occurs when starting up core-image-sato under userspace nfs.

To replicate from the command line:
runqemu-extract-sdk core-image-sato-sdk-qemux86-64.tar.bz2 myrootfs
unset DEPLOY_DIR_IMAGE; 
runqemu bzImage-qemux86-64.bin myrootfs
Comment 9 brian avery 2017-11-01 17:08:42 UTC 
changed importance to undecided so it can be retriaged.
Comment 10 Armin Kuster 2019-05-23 15:00:16 UTC 
eclipse has been dropped.
Comment 11 Armin Kuster 2019-05-23 15:06:58 UTC 
closing