I use the appimage , and I get a SIGSEGV on startup. If I ignore it I do not have any problems, but I think this should not be done.
The Reply in the CommandLine is:
$ ./texstudio-3.0.1-x86_64.AppImage 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 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 SSLv23_client_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 SSLeay 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 BibTeX-File /home/jokalliau/ownCloud/Mang/LaTeX/falsification/bibtex.bib not loaded crashed with signal SIGSEGV in thread 00000000028d74d0 SIGSEGV forced kill in 00000000028d74d0 (TXS-Version 3.0.1 R ) SIGSEGV forced kill in 00000000028d74d0 (TXS-Version 3.0.1 R ) SIGSEGV forced kill in 00000000028d74d0 (TXS-Version 3.0.1 R ) SIGSEGV forced kill in 00000000028d74d0 (TXS-Version 3.0.1 R ) [bt] ./texstudio-3.0.1-x86_64.AppImage(_ZN12SimulatedCPU13set_from_realEv+0) [0x84c9d0] [bt] ./texstudio-3.0.1-x86_64.AppImage(_ZN12SimulatedCPU13set_from_realEv+0) [0x84c9d0] 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 ERR_free_strings QMutex: destroying locked mutex QObject::~QObject: Timers cannot be stopped from another thread Speicherzugriffsfehler (Speicherabzug geschrieben)
PS I use the appimage because I run into https://sourceforge.net/p/texstudio/bugs/1291/#d683 . But not with the appimage-version.
I fixed the missing bitex.bib-file and some others, and run it with pdflatex in command line.
It is somehow related to opened tex-files, because if all files are closed the issue does not occur.