Can someone confirm?

René J.V. Bertin rjvbertin at gmail.com
Sat Apr 11 10:04:57 BST 2020


On Friday April 10 2020 17:11:44 Leon Pollak wrote:

If you can, just make the project available and file a bug report in which you describe exactly how you set things up and what you observe. That recipe should be based on a new session into which you import the project, of course.

Other things to try:
- download the KDevelop AppImage from kdevelop.org and open your session in that version of the application. If your issue does NOT occur there you have identified a problem with the version from your distribution, and you should report the bug there.
Otherwise:
- use more standard paths for your work directory, i.e. not something under the root rather for instance $HOME/Project . This will increase the chance that people will actually try to follow your recipe. If that solves your issue it is still a bug in KDevelop, IMHO.
- follow your own recipe after writing it down
- follow it once more, but now using the KDevelop AppImage downloaded from kdevelop.org and with your own $HOME/.config/kdeveloprc moved (backed up and deleted) so that you test using a virgin KDevelop install.

R.


More information about the KDevelop mailing list