Can't install Qradiolink

[sk9la]

Hi,

After updating my kali packages, I can't install the new version of qradiolink, here is what I got:

apt install ./Qradiolink.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'qradiolink' instead of './Qradiolink.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgsl25 : Depends: libgslcblas0 (= 2.6+dfsg-2) but 2.7.1+dfsg-5 is to be installed
 libgsl27 : Breaks: libgsl25 but 2.6+dfsg-2 is to be installed
 qradiolink : Depends: libsoapysdr0.7 (>= 0.7.2) but it is not installable
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Any idea to fix this issue ?

[kantooon]

libsoapysdr is the only direct dependency of qradiolink from that list. I'm not sure what depends on libgsl but I don't think it's related. SoapySDR version 0.8 should be usable with qradiolink, so I'm not sure what your package manager is complaining about.

Have you tried installing with dpkg? If all dependencies are already satisfied by installing version 0.8.9 of qradiolink previously, you should not need apt. Nevertheless, you have some conflicting packages there, but I'm not familiar with Kali so can't give much useful advice in this matter.

[sk9la]

Ok I successfully tried installing the deb file after tinkering with dependencies, but I still have a Segmentation Fault.

The appimage works great though

[kantooon]

The segmentation fault points to a problem, either in the application itself, or in one of the dependencies. I'm not aware of any bug that would lead to a segmentation fault, so I'd like to ask you to start qradiolink with gdb:
gdb qradiolink
then type r
and when the segmentation fault occurs, type bt and post the complete result here so I can take a look.
Thanks.

[sk9la]

Sure, here it is

#0  0x00007ffff3aa80fc in ?? () from /usr/lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff3a5a472 in raise () from /usr/lib/x86_64-linux-gnu/libc.so.6
#2  0x00007ffff3a444b2 in abort () from /usr/lib/x86_64-linux-gnu/libc.so.6
#3  0x00007ffff3ca09db in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00007ffff3cafffa in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x00007ffff3cb0065 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x00007ffff3cb02b8 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x00007ffff7329069 in ?? () from /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.8.2
#8  0x00007ffff738019a in gr::configure_default_loggers(log4cpp::Category*&, log4cpp::Category*&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) ()
   from /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.8.2
#9  0x00007ffff73d9fc8 in ?? () from /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.8.2
#10 0x00007ffff73dd40c in ?? () from /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.8.2
#11 0x00007ffff73d7aeb in ?? () from /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.8.2
#12 0x00007ffff7333e34 in ?? () from /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so.3.8.2
#13 0x00007ffff7fcfe2e in ?? () from /lib64/ld-linux-x86-64.so.2
#14 0x00007ffff7fcff14 in ?? () from /lib64/ld-linux-x86-64.so.2
#15 0x00007ffff7fe5170 in ?? () from /lib64/ld-linux-x86-64.so.2
#16 0x0000000000000001 in ?? ()
#17 0x00007fffffffdb31 in ?? ()
#18 0x0000000000000000 in ?? ()

By the way, I have two versions of libgnuradio-runtime on kali, both runtimes 3.10.7 and 3.8.2

[kantooon]

Sorry, there does not appear to be enough information from the backtrace. It is possible the issue occurs in gnuradio but I can't tell for sure based on the backtrace. If you start qradiolink from the command line, can you provide the output on stdout and stderr if there is any?
A possible cause can be in gr::configure_default_loggers but since I can't reproduce this at all in Debian, I assume it has something to do with your specific local environment.

[sk9la]

I have pretty much the same error while launching qradiolink from terminal

terminate called after throwing an instance of 'std::runtime_error'
  what():  logger_set_level: Bad level type.

Aborted (core dumped)

It's ok, I'm not using it actively. I'll probably wait for the next version to get released, otherwise will go with the AppImage version

[kantooon]

Unfortunately I can't help much here. That error is related to your gnuradio or gr-osmosdr install and I can't reproduce it on Debian at all. See this issue which looks very much related to yours: gnuradio/gnuradio#6757
This also means there will not be a fix in the next release, since the issue can't be fixed in qradiolink.