[SOLVED] systemview systemview-2.52.1.x86_64.rpm is a broken install

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] systemview systemview-2.52.1.x86_64.rpm is a broken install

    After (successfully) installing systemview-2.52.1.x86_64.rpm, application won't run because:

    SystemView: error while loading shared libraries: libQtGui.so.4: cannot open shared object file: No such file or directory

    (This library seems included in JLink & ozone installation packages, unlike ..)

    The post was edited 1 time, last by v01d ().

  • Hello,

    Thank you for your inquiry.
    We tried to replicate the described behaviour in a Fedora 27 VM.
    First we installed the J-Link software RPM package, then SystemView.
    After that SystemView could be launched over CL or per double click without any issues.
    Picture is attached.

    Could you describe step by step how you installed the software and in what order?

    Best regards,
    Nino
    Images

    • Capture.PNG

      403.2 kB, 1,686×848, viewed 760 times
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hello,

    As far as I see in my original install log:


    1 JLink_Linux_V630a_x86_64.rpm

    2 ozone-2.54.2.x86_64.rpm

    3 JLink_Linux_V630b_x86_64.rpm ozone-2.56.x86_64.rpm systemview-2.52.1.x86_64.rpm



    Can I ask, how is systemview suppose to run if it does not include it's own Qt libraries, and the host system may or not have them?
    As RPM does not spec that dependency.

    Could you paste the output of ldd SystemView?

    The post was edited 1 time, last by v01d ().

  • Hello,

    Can I ask, how is systemview suppose to run if it does not include it's own Qt libraries, and the host system may or not have them?

    We are currently working on a Linux white list for Linux distributions that fulfill the needed requirements.

    Could you paste the output of ldd SystemView?

    Source Code

    1. ldd '/opt/SEGGER/SystemView/SystemView'
    2. linux-vdso.so.1 (0x00007ffd30ffc000)
    3. libQtGui.so.4 => /lib64/libQtGui.so.4 (0x00007fca5de9d000)
    4. libQtCore.so.4 => /lib64/libQtCore.so.4 (0x00007fca5d999000)
    5. libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fca5d77a000)
    6. libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fca5d3f4000)
    7. libm.so.6 => /lib64/libm.so.6 (0x00007fca5d09f000)
    8. libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fca5ce88000)
    9. libc.so.6 => /lib64/libc.so.6 (0x00007fca5caa5000)
    10. librt.so.1 => /lib64/librt.so.1 (0x00007fca5c89d000)
    11. libdl.so.2 => /lib64/libdl.so.2 (0x00007fca5c699000)
    12. libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007fca5c497000)
    13. libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007fca5c183000)
    14. libpng16.so.16 => /lib64/libpng16.so.16 (0x00007fca5bf50000)
    15. libz.so.1 => /lib64/libz.so.1 (0x00007fca5bd39000)
    16. libfreetype.so.6 => /lib64/libfreetype.so.6 (0x00007fca5ba84000)
    17. libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007fca5b831000)
    18. libSM.so.6 => /lib64/libSM.so.6 (0x00007fca5b629000)
    19. libICE.so.6 => /lib64/libICE.so.6 (0x00007fca5b40d000)
    20. libXi.so.6 => /lib64/libXi.so.6 (0x00007fca5b1fc000)
    21. libXrender.so.1 => /lib64/libXrender.so.1 (0x00007fca5aff2000)
    22. libXrandr.so.2 => /lib64/libXrandr.so.2 (0x00007fca5ade7000)
    23. libXfixes.so.3 => /lib64/libXfixes.so.3 (0x00007fca5abe1000)
    24. libXcursor.so.1 => /lib64/libXcursor.so.1 (0x00007fca5a9d6000)
    25. libXinerama.so.1 => /lib64/libXinerama.so.1 (0x00007fca5a7d3000)
    26. libfontconfig.so.1 => /lib64/libfontconfig.so.1 (0x00007fca5a58e000)
    27. libXext.so.6 => /lib64/libXext.so.6 (0x00007fca5a37c000)
    28. libX11.so.6 => /lib64/libX11.so.6 (0x00007fca5a03e000)
    29. /lib64/ld-linux-x86-64.so.2 (0x00007fca5ebc4000)
    30. libpcre.so.1 => /lib64/libpcre.so.1 (0x00007fca59dcb000)
    31. libbz2.so.1 => /lib64/libbz2.so.1 (0x00007fca59bba000)
    32. libffi.so.6 => /lib64/libffi.so.6 (0x00007fca599b2000)
    33. libuuid.so.1 => /lib64/libuuid.so.1 (0x00007fca597ad000)
    34. libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fca5957b000)
    35. libxcb.so.1 => /lib64/libxcb.so.1 (0x00007fca59353000)
    36. libXau.so.6 => /lib64/libXau.so.6 (0x00007fca5914f000)
    Display All


    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Nino,

    Thanks for that list. Coupled with the other discussion we had under J-Link forum, my thread on incomplete RPM spec, this issue is exhausted now and can be closed.

    I still believe Segger needs to fix the RPM specs, so that packages can actually be installed correctly out-the-box.

    Regards

  • Hello,

    Thank you for your feedback.
    We will consider this case as solved now.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.