Red Hat Bugzilla – Bug 894278
[abrt] bacula-console-bat-5.2.12-3.fc17: QHashNode: Process /usr/sbin/bat was killed by signal 11 (SIGSEGV)
Last modified: 2013-08-01 01:37:11 EDT
Version-Release number of selected component:
libreport version: 2.0.18
cmdline: /usr/sbin/bat -c /etc/bacula/bat.conf
:Thread no. 1 (10 frames)
: #0 QHashNode at /usr/include/QtCore/qhash.h:253
: #1 QHash<int, DirComm*>::duplicateNode at /usr/include/QtCore/qhash.h:532
: #2 QHashData::detach_helper2 at tools/qhash.cpp:239
: #3 QHash<int, DirComm*>::detach_helper at /usr/include/QtCore/qhash.h:584
: #4 detach at /usr/include/QtCore/qhash.h:303
: #5 QHash<int, DirComm*>::remove at /usr/include/QtCore/qhash.h:788
: #6 Console::newDirComm at console/console.cpp:926
: #7 Console::populateLists at console/console.cpp:156
: #8 MainWin::popLists at mainwin.cpp:122
: #9 QMetaObject::activate at kernel/qobject.cpp:3539
Created attachment 676746 [details]
Created attachment 676747 [details]
Created attachment 676748 [details]
Created attachment 676749 [details]
Created attachment 676750 [details]
Created attachment 676752 [details]
Created attachment 676753 [details]
Created attachment 676754 [details]
Created attachment 676755 [details]
Created attachment 676756 [details]
Created attachment 676757 [details]
Created attachment 676758 [details]
I am trying to simulate that one bug but it failed with the same reason as
Please provide me steps and how did you run the bat command either from console
or from GUI.
Did you run that from KDE or from Gnome?
What steps have been run before running BAT?
Where there configured any database (like postresql or sqlite).
Where there run any jobs?
It seems that it is relevant to QLibraries problem.
How to reproduce that problem?
Bat was running on a different machine than the director (director is a Debian, in a different subnet). Started from GNOME application list.
The director is running more or less error-free for a year now, with an SQLite backend.
I can't remember if there were running jobs, at that time usually there are none.
I can't reproduce the problem.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora
'version' of '17'.
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 prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.
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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Thank you for reporting this bug and we are sorry it could not be fixed.