Created attachment 903273 [details] text file holding the report from the crash handler I tried to use the KCrash Handler, everything fine up to the end when it says that it is unable to send the report due to some version mismatch. I am attaching the file holding the report as attachment. However, briefly: whenever I construct a locus in kig everything seems fine till the end of the construction, but the kig crashes as soon as I move the mouse. Fedora 20, kig version 1.0, kig-4.12.5-1.fc20.i686.rpm architecture i386, kernel_PAE.
Forgot to add that the bug is not present when compiling kig from the latest git source
I don't have time to file a bug against the "bug reporting tool" (seems amusing). However here is the content of the last panel: Crash Reporting Assistant Sending the Crash Report Error sending the crash report: /Received unexpected error code 32,000 from bugzilla. Error message was: The version value 'v1.0' is not active../ (seems related to the version number that kig reports: v1.0)
The problem is still there. Locus does not work with version kig-4.13.3-1.fc20.i686 kig is quite *unusable* like this! "locus" is an essential feature of kig Note that compiling from latest git source resolves the problem.
"latest git" means? master/ branch ? Maybe upstream forgot to backport some fix(es). (And reporting kcrashes upstream to bugs.kde.org is preferable, the backtrace is seen by the right people in a position to fix things best).
Oh, I see comment #2 where drkonqi reporting seems to have failed. That's too bad. :(
(In reply to Rex Dieter from comment #4) > "latest git" means? master/ branch ? Maybe upstream forgot to backport > some fix(es). > > (And reporting kcrashes upstream to bugs.kde.org is preferable, the > backtrace is seen by the right people in a position to fix things best). master
After lenghty debugging it seems that compiler option "-fstack-protector-strong" is responsible for the crash (or more likely, it exposes a problem in the kig sources). I tried to compile from git "master" sources as follows: export CXXFLAGS="-fstack-protector-strong" cmake . -DCMAKE_INSTALL_PREFIX=/usr make sudo make install --> kig crashes when creating a locus ======== the mentioned "-fstack-protector-strong" option is one of the options included by the rpm macro %{cmake_kde4} We also tried with -fstack-protector-all -> CRASH -fstack-protector -> NO CRASH so now how should we proceed?
Per comment #4, best course of action is to inform upstream devs about it, ideally via bug report @ bugs.kde.org thanks for the detective-work!
Allright. I filed a bugreport upstream
Mind sharing the bug # (so we can link this report, and continue tracking progress there)?
(In reply to Rex Dieter from comment #10) > Mind sharing the bug # (so we can link this report, and continue tracking > progress there)? Sure, silly me! I opened a bug report on bugs.kde.org, the link is: https://bugs.kde.org/show_bug.cgi?id=338978
Proposed patch from upstream: https://git.reviewboard.kde.org/r/120129/
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.