Description of problem:
Opening the C++ Helper settings causes a segmentation fault. The bug is already mentioned (including the fix) in the review request:
This is the important part of the backtrace. I can install full debuginfo and provide the full trace but this is enough to show pretty conclusively that the linked problem is what this is:
Thread 1 (Thread 0x7f515d2d48c0 (LWP 2151)):
#5 0x00007f5150185f2a in kate::CppHelperPluginConfigPage::findBinary(QString const&) const () from /usr/lib64/kde4/katecpphelperplugin.so
#6 0x00007f515018a2f1 in kate::CppHelperPluginConfigPage::CppHelperPluginConfigPage(QWidget*, kate::CppHelperPlugin*) () from /usr/lib64/kde4/katecpphelperplugin.so
#7 0x00007f515019be09 in kate::CppHelperPlugin::configPage(unsigned int, QWidget*, char const*) () from /usr/lib64/kde4/katecpphelperplugin.so
Version-Release number of selected component (if applicable):
(note the above kate version is from kde-redhat but the current Fedora version doesn't make any difference)
Steps to Reproduce:
1. Open kate.
2. Enable C++ Plugin (Settings -> Configure Kate -> Application -> Plugins).
3. Switch to C++ Helper settings.
This bug should have been fixed when it was mentioned in the review request, *BEFORE* releasing it on the users.
kate-plugin-cpphelper-0.9.6-1.fc19 has been submitted as an update for Fedora 19.
kate-plugin-cpphelper-0.9.6-1.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kate-plugin-cpphelper-0.9.6-1.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
kate-plugin-cpphelper-0.9.6-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
kate-plugin-cpphelper-0.9.6-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.