Red Hat Bugzilla – Bug 1010596
[abrt] calibre-0.9.42-1.fc19: QString::free: Process /usr/bin/python2.7 was killed by signal 6 (SIGABRT)
Last modified: 2015-02-18 06:28:57 EST
Version-Release number of selected component:
cmdline: python2 /usr/bin/calibre
runlevel: N 5
Thread no. 1 (10 frames)
#5 QString::free at tools/qstring.cpp:1235
#6 ~QString at ../../src/corelib/tools/qstring.h:880
#7 QDBusMessagePrivate::~QDBusMessagePrivate at qdbusmessage.cpp:72
#8 QDBusMessage::~QDBusMessage at qdbusmessage.cpp:537
#9 ~QDBusCallDeliveryEvent at qdbusintegrator_p.h:93
#10 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent at qdbusintegrator_p.h:93
#11 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1589
#12 QCoreApplication::sendPostedEvents at kernel/qcoreapplication.cpp:1466
#13 sendPostedEvents at kernel/qcoreapplication.h:236
#14 postEventSourceDispatch at kernel/qeventdispatcher_glib.cpp:280
Created attachment 800988 [details]
Created attachment 800989 [details]
Created attachment 800990 [details]
Created attachment 800991 [details]
Created attachment 800992 [details]
Created attachment 800993 [details]
Created attachment 800994 [details]
Created attachment 800995 [details]
Created attachment 800996 [details]
Created attachment 800997 [details]
What were you doing when this happened?
Can you duplicate the crash?
Does upgrading to the newest version from the side repo help:
yum clean all
yum update calibre
Calibre was idle after an automatic download (it downloads news nightly).
I cannot reproduce the bug unfortunately
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.