https://bugs.kde.org/show_bug.cgi?id=482819
--- Comment #16 from Matt Fagnani <matt.fagn...@bell.net> --- Yes, my system is fully updated with the updates-testing repo enabled. I ran those steps with the qca 2.3.8 build with your patch which gave me the following output. privateKey.context() appeared to have a non-null pointer. qmake6 && make && ./test Info: creating stash file /programs/qca/test/.qmake.stash [2]+ Done kate test.pro g++ -c -pipe -g -Wall -Wextra -D_REENTRANT -DQT_GUI_LIB -DQT_CORE_LIB -I. -I. -I/usr/include/qt6/QtCrypto -I/usr/include/qt6 -I/usr/include/qt6/QtGui -I/usr/include/qt6/QtCore -I. -I/usr/lib64/qt6/mkspecs/linux-g++ -o main.o main.cpp g++ -Wl,-rpath-link,/usr/lib64 -o test main.o -lqca-qt6 /usr/lib64/libQt6Gui.so /usr/lib64/libQt6Core.so -lpthread -lGLX -lOpenGL opensslQCAPlugin::MyPKeyContext(0xc34710) -- You are receiving this mail because: You are watching all bug changes.
