Bug 478755

Summary:	Flatpak KDevelop "Problems" page does not display anything
Product:	[Applications] kdevelop	Reporter:	Lassi Väätämöinen <lassi.vaatamoinen>
Component:	general	Assignee:	kdevelop-bugs-null
Status:	CONFIRMED ---
Severity:	major	CC:	neon-bugs-null
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Lassi Väätämöinen 2023-12-20 09:30:43 UTC

SUMMARY
The "problems " view at the bottom of the screen does not display anything. Before updating to the Snap/Flatpak version a week ago, it worked fine.

STEPS TO REPRODUCE
1.  Install Kdevelop from Snap store
2. Run kdevelop
3. Open existing project with TODO and FIXME notes

OBSERVED RESULT
No TODO or FIXME lines shown in "Problems view"
(Or any other known problems, either.)

EXPECTED RESULT
TODO, FIXME and other known problems should be shown.

SOFTWARE/OS VERSIONS
snap-id: vF7qHQJ3SMpORQX952464X4FQhbnh6gu
channels:
  latest/stable:    5.12.230804 2023-12-10 (77) 763MB classic
  latest/candidate: 5.12.230804 2023-12-09 (77) 763MB classic

ADDITIONAL INFORMATION
 ~/.var/app/org.kde.kdevelop/cache/kdevduchain was cleared with 'rm', and projects rescanned. Did not help.

Comment 1 Lassi Väätämöinen 2023-12-20 09:44:14 UTC

Not sure if this has anything to do with it, but 'cppcheck' also fails, as the Flatpack KDevelop cannot find 'libpcre'.

It shows this in the 'Test' view, when executing cppcheck

> /run/user/1000/doc/84a72681/cppcheck --xml-version=2 --enable=style --enable=performance --enable=portability --enable=information --enable=unusedFunction --enable=missingInclude --inconclusive --force --check-config /home/vaatala/projects/navtech-radar
/run/user/1000/doc/84a72681/cppcheck: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory
Elapsed time: 0.09 s.
*** Failure: Exit code 127 ***

But in my system, libpcre.so.3 is present:

$ dpkg-query -L libpcre3
/.
/lib
/lib/x86_64-linux-gnu
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
/usr
/usr/bin
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libpcreposix.so.3.13.3
/usr/sbin
/usr/share
/usr/share/doc
/usr/share/doc/libpcre3
/usr/share/doc/libpcre3/AUTHORS
/usr/share/doc/libpcre3/NEWS.gz
/usr/share/doc/libpcre3/README.Debian
/usr/share/doc/libpcre3/README.gz
/usr/share/doc/libpcre3/changelog.Debian.gz
/usr/share/doc/libpcre3/copyright
/usr/share/man
/usr/share/man/man3
/usr/share/man/man3/pcrepattern.3.gz
/lib/x86_64-linux-gnu/libpcre.so.3
/usr/lib/x86_64-linux-gnu/libpcreposix.so.3


So to me it looks like the Flatpack'ed KDevelop cannot see any binaries outside its sandbox.
(For clazy, I also needed to manually set clazy executable path, etc..)

Comment 2 Lassi Väätämöinen 2023-12-20 10:01:21 UTC

I guess Kdevelop package should install all the plugins dependencies, or the Flatpak should be setup so that it can access the system libraries?

Comment 3 Lassi Väätämöinen 2023-12-20 11:43:46 UTC

I managed to install the "native" Kdevelop back, and it displays the "Problem" items again properly. So definitely a Flatpak'd Kdevelop issue.