https://bugs.kde.org/show_bug.cgi?id=492398
--- Comment #2 from muel...@online.de --- (In reply to Antonio Rojas from comment #1) > What do you mean by "in a functional state"? I'm sorry, that was not very precise :-( Let's go into more detail: I had a working environment but no projects under Version 5.14.240502 (24.05.2) After my archlinux upgraded to Version 6.0.240800 (24.08.0) I could not create new projects because the "Open Project" file browser would not accept *.pro files. Therefore I downgraded again to regenerate the project there (which worked as I was used to). After upgrading again kdevelop started with the files open as I left it, but with empty Project window and no Build Sequences. Also it showed the above-mentioned error message. Options to set up launch configurations were greyed-out and I was effectively "locked out" of my programming environment. This is what I called "nonfunctional". (As a side-note: also my kdevelop 5.7 cannot load kdevastyle.so, so this seems to be unrelated but not very harmful.) So to answer your question in more detail, I thoroughly rinsed everything that could be reproduced/auto-generated: I deleted all *.kdev4, Makefile.* , build/ and even ~/.local/share/kdevelop and then regenerated a working environment from a *.pro . After that I manually upgraded to 6.0.240800. Since then, when I start kdevelop, the session starts as it did before. So I have to apologize: apparently something(???) confused kdevelop which does not happen from a really clean environment. For reasons beyond my understanding now also the option *.pro is offered again when I do the wiping for a fresh start. Unfortunately, I probably cannot fully reproduce the cluttered state because I do not backup caches and config files inside GIT. Un- and reinstalling different versions and working-stages a number of times seems to have fixed whatever was cluttered. At the moment kdevelop seems to work again as expected. Therefore, the initial bug report can probably be closed. Sorry for the bedevilment! -- You are receiving this mail because: You are watching all bug changes.
