Red Hat Bugzilla – Bug 1254125
[abrt] trojita: QObject::disconnect(): trojita killed by SIGSEGV
Last modified: 2016-07-19 13:31:58 EDT
Description of problem:
I've tried to send an email. It seems that trojita lost connection during the operation. After some time, I got timeout message and then it crashed.
Version-Release number of selected component:
cmdline: /bin/trojita -session 102911f2196210000143461264700000212270016_1434959607_307830
runlevel: N 5
Thread no. 1 (10 frames)
#1 QObject::disconnect at kernel/qobject.cpp:2936
#2 disconnect at /usr/include/qt5/QtCore/qobject.h:359
#3 Imap::Mailbox::Model::killParser at /usr/src/debug/trojita-0.5/src/Imap/Model/Model.cpp:1474
#4 Imap::Mailbox::Model::handleState at /usr/src/debug/trojita-0.5/src/Imap/Model/Model.cpp:309
#5 Imap::Mailbox::Model::responseReceived at /usr/src/debug/trojita-0.5/src/Imap/Model/Model.cpp:245
#7 Imap::Mailbox::Model::qt_static_metacall at /usr/src/debug/trojita-0.5/build/moc_Model.cpp:322
#8 QObject::event at kernel/qobject.cpp:1245
#9 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3720
#10 QApplication::notify at kernel/qapplication.cpp:3503
#11 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:935
Created attachment 1063712 [details]
Created attachment 1063713 [details]
Created attachment 1063714 [details]
Created attachment 1063715 [details]
Created attachment 1063716 [details]
Created attachment 1063717 [details]
Created attachment 1063718 [details]
Created attachment 1063719 [details]
Created attachment 1063720 [details]
Created attachment 1063721 [details]
Created attachment 1063722 [details]
Created attachment 1063723 [details]
This looks like a strange bug in QtCore.
FTBFS in rawhide. I've to fix that first.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
Thank you for reporting this bug and we are sorry it could not be fixed.