Bug 492398

Summary:	After upgrade from 5.7 to 6.0 kdevelop starts in nonfunc state and cannot open *.pro files anymore
Product:	[Applications] kdevelop	Reporter:	muellag
Component:	general	Assignee:	kdevelop-bugs-null
Status:	RESOLVED DOWNSTREAM
Severity:	grave	CC:	igorkuo
Priority:	NOR
Version First Reported In:	6.0.240800
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description muellag 2024-08-30 09:10:17 UTC

After (automatic) upgrading my archlinux I got kdevelop 8.0.240800 installed. Since then It does not start anymore (in a functional state) and complains:
" Could not load project management plugin KDevQMakeManager.
Check that the required programs are installed, or see console output for more information."
The console complains:
"kf.coreaddons: "Could not load plugin from /usr/lib/qt6/plugins/kdevplatform/60/kdevastyle.so: Cannot load library /usr/lib/qt6/plugins/kdevplatform/60/kdevastyle.so"
I cannot find any kdevastyle in neither archlinux-packages nor UserRepository (AUR) and a search for "KDevQMakeManager" only delivers hits from a decade ago.

Possibly related: starting a new session through "Open Project" does not offer anymore to read QT's *.pro files.

After reinstalling version 5.14.240502 (24.05.2) everything works again as before, meaning the problems are not caused by something being accidentally deinstalled.

Comment 1 Antonio Rojas 2024-08-30 09:35:16 UTC

What do you mean by "in a functional state"?

Comment 2 muellag 2024-08-30 12:45:02 UTC

(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!

Comment 3 Igor Kushnir 2024-08-30 14:22:44 UTC

*Building* KDevQMakeManager requires kdevelop-pg-qt version 2.3 or later. Looks like https://gitlab.archlinux.org/archlinux/packaging/packages/kdevelop/-/commit/376b17582443bd7a55715dc1c261f649ad7c391f fixed the Arch packaging issue today.

Install the optional astyle dependency of the kdevelop package if you want to use the kdevastyle formatting plugin.