Jump to content
  • 0

Waveform 3.8.2 crasches on Debian 10 x64


nolange79

Question

Hello,

I get a crash in libusb, which is related to the version of libftd2xx from the adept runtime. replacing the shared library with version 1.4.8 fixes the issue. please update the adept runtime package.

further, I get the following warnings when starting [/usr/bin/]waveforms:

qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: QSslSocket: cannot resolve SSLeay_version
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function sk_num
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init


Supposedly mean I am not able to use SSL (for whatever). Adopting the /usr/bin/waveforms to not change the Library load path fixed the issue.
perhaps a package just using (recent enough) system libraries would make sence?

Link to comment
Share on other sites

8 answers to this question

Recommended Posts

Hi @nolange79

In WaveForms v3.8.2 update checking is modified to use HTTPS, which requires some SSL libraries.
Could you give me a link to download Debian 10?

Please try digilent.waveforms_3.8.6_amd64.deb
https://forum.digilentinc.com/topic/8908-waveforms-beta-download/
In this version Update check option is added with default value of Never.

 

Link to comment
Share on other sites

Hi @nolange79

This disablation of auto update check is just a temporal solution, in order you to be able to use the application, until the problem is solved.

The libftd2xxx.so.1.0.4 in the latest Adept Runtime 2.17.1 is not working under Debian 10 ?
https://reference.digilentinc.com/reference/software/adept/start
Adding  @malexander to this this topic...

Link to comment
Share on other sites

1 hour ago, attila said:

Hi @nolange79

This disablation of auto update check is just a temporal solution, in order you to be able to use the application, until the problem is solved.

The libftd2xxx.so.1.0.4 in the latest Adept Runtime 2.17.1 is not working under Debian 10 ?
https://reference.digilentinc.com/reference/software/adept/start
Adding  @malexander to this this topic...


I can run waveforms nicely with the system libraries (QT5 et al), no need for workarounds.

And as said, I copied libftd2xxx.so.1.4.8 over the version from Adept Runtime 2.17.1 to fix the following crash.

Thread 7 "waveforms" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff4ec55700 (LWP 29137)]
0x00007fffee27e73a in libusb_close () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
(gdb) bt
#0  0x00007fffee27e73a in libusb_close () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#1  0x00007fff4da3992d in CloseDevice () from /usr/lib64/digilent/adept/libftd2xx.so
#2  0x00007fff4da3ac91 in OpenDevice () from /usr/lib64/digilent/adept/libftd2xx.so
#3  0x00007fff4da3b1ed in FTCommonOpen () from /usr/lib64/digilent/adept/libftd2xx.so
#4  0x00007fff4da3b33e in FT_OpenEx () from /usr/lib64/digilent/adept/libftd2xx.so
#5  0x00007ffff1ba4cae in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2
#6  0x00007ffff1b9f1b3 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2
#7  0x00007ffff1b9b6f8 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2
#8  0x00007ffff1b993d6 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2
#9  0x00007ffff1b988dc in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2
#10 0x00007ffff36b05aa in start_thread (arg=0x7fff4ec55700) at pthread_create.c:463
#11 0x00007ffff4850cbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95


 

Link to comment
Share on other sites

I will install Debian 10 in VM here but I trust that the solution to this issue is to update the installers to include libftd2xx.so.1.4.8. Before we can do that we will need to test that version of the library in all of the other distributions that we have to support.

Thanks,
Michael

Link to comment
Share on other sites

On 7/14/2018 at 12:12 AM, malexander said:

@nolange79

Thank you for reporting this issue. Adept Runtime 2.18.3 has been published and it includes version 1.4.8 of the FTDI driver. The installers can be found here:

https://reference.digilentinc.com/reference/software/adept/start

Thanks, that fixed the USB troubles.

I am still running Waveforms with the Qt5 libs from debian though, this is no problem to do but the packet uses the bundled libs by default which have the warnings mentioned above

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...