Tuesday, April 24th 2018, 8:42am UTC+2

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

v01d

Beginner

Date of registration: Feb 29th 2016

Posts: 110

1

Sunday, February 4th 2018, 3:05am

[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 ..)



This post has been edited 1 times, last edit by "v01d" (Feb 4th 2018, 3:06am)


v01d

Beginner

Date of registration: Feb 29th 2016

Posts: 110

2

Sunday, February 4th 2018, 6:12am

libQTGui from latest jlink (jlink-6.30.1-1.x86_64) /ozone package doesn't work,

but the libQT files included in ozone-ubuntu-2.30.4.x86_64.rpm work (SystemView starts )

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 949

3

Thursday, March 8th 2018, 1:43pm

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
SEGGER - Nino has attached the following image:
  • Capture.PNG
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
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 contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/


v01d

Beginner

Date of registration: Feb 29th 2016

Posts: 110

4

Friday, March 9th 2018, 10:55am

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?

This post has been edited 1 times, last edit by "v01d" (Mar 9th 2018, 11:05am)


SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 949

5

Wednesday, March 14th 2018, 4:11pm

Hello,

Quoted

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.

Quoted

Could you paste the output of ldd SystemView?

Source code

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


Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
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 contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/


v01d

Beginner

Date of registration: Feb 29th 2016

Posts: 110

6

Yesterday, 2:53am

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

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 949

7

Yesterday, 9:09am

Hello,

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

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
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 contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/