![]() ![]() Thread 5 "qTox Database" received signal SIGSEGV, Segmentation fault.Ġx00007ffff3c2f75d in EVP_EncryptUpdate ()įrom /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 persistence/settings.cpp:494 : Debug: "Saving global settings at /home/martin/.config/tox/qtox.ini" persistence/settings.cpp:2383 : Debug: Creating new profile settings in "/home/martin/.config/tox//test.ini" ipc.cpp:77 : Debug: Attaching to the global shared memory ![]() persistence/settings.cpp:137 : Debug: "Loading settings from :/conf/qtox.ini" persistence/settings.cpp:133 : Debug: No settings file found, using defaults Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Reading symbols from qtox.(no debugging symbols found).done. Here is one of the backtraces from qTox copied from my upstream bug report: The bug happens with qtox package, with qtox-alpha package and with selfĬompiled qtox from git 6b51381980e4d742efff0905a697040efbcce049įor now I will pin the libsqlcipher0 package to the older version. You do not need to compile qTox yourself, but can install packages as Related to the transition to openssl 1.1.ġ) rm -r ~/.config/tox (make backup first!)ģ) Create new profile, I used user "test" with password "12" So it appears to me that this is a distribution side issue which may be Sqlcipher library myself (which failed on my system for 3.4.0), I found that This may have been shortly before Christmas and may relateĪnd after several attempts with compiling qTox myself and trying to compile Sometime ago qTox started crashing after entering profile password on myĭebian setup. This could be severity grave, but as I did not verify whether otherĪpplications using libsqlcipher0 crash, I am setting it to important for ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |