Hide Forgot
Description of problem: I was just quickly deleting messages. Version-Release number of selected component: trojita-0.7-3.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/trojita crash_function: gpgme_key_unref executable: /usr/bin/trojita global_pid: 18904 kernel: 4.8.0-0.rc7.git0.1.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gpgme_key_unref at key.c:321 #1 boost::detail::sp_counted_base::release at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:146 #3 boost::detail::shared_count::~shared_count at /usr/include/boost/smart_ptr/detail/shared_count.hpp:473 #4 boost::shared_ptr<_gpgme_key>::~shared_ptr at /usr/include/boost/smart_ptr/shared_ptr.hpp:336 #5 GpgME::Key::~Key at /usr/include/KF5/gpgme++/key.h:55 #6 Cryptography::GpgMePart::extractSignatureStatus at /usr/src/debug/trojita-0.7/src/Cryptography/GpgMe++.cpp:324 #7 Cryptography::GpgMeSigned::<lambda()>::operator()(void) const at /usr/src/debug/trojita-0.7/src/Cryptography/GpgMe++.cpp:681 #8 std::_Bind_simple<Cryptography::GpgMeSigned::handleDataChanged(const QModelIndex&, const QModelIndex&)::<lambda()>()>::_M_invoke<> at /usr/include/c++/6.1.1/functional:1400 #9 std::_Bind_simple<Cryptography::GpgMeSigned::handleDataChanged(const QModelIndex&, const QModelIndex&)::<lambda()>()>::operator() at /usr/include/c++/6.1.1/functional:1389 #10 std::__future_base::_Task_setter<std::unique_ptr<std::__future_base::_Result<void>, std::__future_base::_Result_base::_Deleter>, std::_Bind_simple<Cryptography::GpgMeSigned::handleDataChanged(const QModelIndex&, const QModelIndex&)::<lambda()>()>, void>::operator() at /usr/include/c++/6.1.1/future:1348
Created attachment 1207173 [details] File: backtrace
Created attachment 1207174 [details] File: cgroup
Created attachment 1207175 [details] File: core_backtrace
Created attachment 1207176 [details] File: dso_list
Created attachment 1207177 [details] File: environ
Created attachment 1207178 [details] File: exploitable
Created attachment 1207179 [details] File: limits
Created attachment 1207180 [details] File: maps
Created attachment 1207181 [details] File: mountinfo
Created attachment 1207182 [details] File: namespaces
Created attachment 1207183 [details] File: open_fds
Created attachment 1207184 [details] File: proc_pid_status
Created attachment 1207185 [details] File: var_log_messages
The provided backtrace lets guess a bug in kf5-gpgmepp or in boost. As the tests work for Trojita, I assume an issue with user configuration. #4 boost::shared_ptr<_gpgme_key>::~shared_ptr … at /usr/include/boost/smart_ptr/shared_ptr.hpp:336 #5 GpgME::Key::~Key … at /usr/include/KF5/gpgme++/key.h:55 #6 Cryptography::GpgMePart::extractSignatureStatus … at /usr/src/debug/trojita-0.7/src/Cryptography/GpgMe++.cpp:324 Maye your signature is b0rken? Can you reproduce this crash?
I'm occasionally getting this crash on my system, too, but I wasn't able to reproduce it reliably (including rebuilds with ASAN, UBSAN, TSAN, Valgrind).
Can you still reproduce? Please tell the installed versions of the following packages: gnupg2-smime kf5-gpgmepp gpgme libgpg-error boost mimetic pinentry
(In reply to Raphael Groner from comment #16) > Can you still reproduce? no ... trojitá crashes seem very random redirecting NEEDINFO to jkt if it happens to him too; however, if _he_ is not able to debug then we're most probably doomed :-)
Nope, I wasn't able to reproduce this, ever. It will get changed anyway to use stuff from the gpgme-1.7+ "soon" anyway.
Can we close here?
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.