Red Hat Bugzilla – Bug 905309
[abrt] bacula-console-bat-5.2.12-6.fc18: e_msg: Process /usr/sbin/bat was killed by signal 11 (SIGSEGV)
Last modified: 2013-02-15 19:55:35 EST
Version-Release number of selected component:
cmdline: /usr/sbin/bat -c /etc/bacula/bat.conf
Thread no. 1 (10 frames)
#0 e_msg at message.c:1233
#1 Console::populateLists at console/console.cpp:157
#2 MainWin::popLists at mainwin.cpp:122
#3 QMetaObject::activate at kernel/qobject.cpp:3539
#4 QSingleShotTimer::timerEvent at kernel/qtimer.cpp:317
#5 QObject::event at kernel/qobject.cpp:1156
#6 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:4562
#7 QApplication::notify at kernel/qapplication.cpp:4423
#8 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:946
#9 sendEvent at kernel/qcoreapplication.h:231
Potential duplicate: bug 842035
Created attachment 689583 [details]
Created attachment 689584 [details]
Created attachment 689585 [details]
Created attachment 689586 [details]
Created attachment 689587 [details]
Created attachment 689588 [details]
Created attachment 689589 [details]
Created attachment 689590 [details]
Created attachment 689591 [details]
Created attachment 689592 [details]
I have created thread in bacula bug report database (http://bugs.bacula.org/view.php?id=1981#c6595)
BugFix is corrected so that instead of generation segmentation fault
SIGABRT is generated.
Step to test that fix:
1) run command /usr/sbin/bat -c /etc/bacula/bat.conf on the system where is NOT configured BACULA.
2) When you receive message "bat: ABORT due to ERROR in console/console.cpp:157 Failed to connect to bacula-dir for populateLists"
then program have to finished with return code but NOT with segmentation fault
3) Return code should be 2
bacula-5.2.12-7.fc18 has been submitted as an update for Fedora 18.
SCM for rawhide: http://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20130204/941902.html
SCM for f17: http://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20130204/941932.html
bacula-5.2.12-7.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing bacula-5.2.12-7.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
bacula-5.2.12-7.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
bacula-5.2.12-7.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.