Bug 506302

Summary:	KDevelop crash during reopening projects
Product:	[Applications] kdevelop	Reporter:	guidedorphas10
Component:	general	Assignee:	kdevelop-bugs-null
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	gravikrimnov, kdedev
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=506248
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description guidedorphas10 2025-06-28 03:28:23 UTC

Application: kdevelop (5.12.230805 (23.08.5))
 (Compiled from sources)
Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.11.0-28-generic x86_64
Windowing System: X11
Distribution: Ubuntu 24.04.2 LTS
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
KDevelop configuration for c++ is unclear which leads to potential user error crashes due to garbage launch config.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault

[KCrash Handler]
#4  0x00005825e00bf570 in ??? ()
#5  0x000070c39a933fd9 in ??? () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/512/kdevclangsupport.so
#6  0x000070c39a935032 in ??? () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/512/kdevclangsupport.so
#7  0x000070c42008941c in KDevelop::BackgroundParser::parseDocuments() () at /lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.512
#8  0x000070c422706343 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x000070c42336bd45 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x000070c4226d8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x000070c4226db94b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x000070c422735c0f in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x000070c41e5145c5 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x000070c41e573737 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x000070c41e513a63 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x000070c422735279 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x000070c4226d6a7b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x000070c4226df3e8 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x000058259e13448c in ??? ()
#20 0x000070c421c2a1ca in __libc_start_call_main (main=main@entry=0x58259e12f890, argc=argc@entry=1, argv=argv@entry=0x7ffec49569c8) at ../sysdeps/nptl/libc_start_call_main.h:58
#21 0x000070c421c2a28b in __libc_start_main_impl (main=0x58259e12f890, argc=1, argv=0x7ffec49569c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffec49569b8) at ../csu/libc-start.c:360
#22 0x000058259e134fd5 in ??? ()
[Inferior 1 (process 7120) detached]

The reporter indicates this bug may be a duplicate of or related to bug 476616, bug 477827, bug 480162, bug 480526, bug 482001, bug 485163, bug 486932, bug 487378, bug 488397, bug 489290, bug 491620, bug 491807, bug 492221, bug 492864, bug 492880, bug 493410, bug 493906, bug 495261, bug 501411, bug 503730, bug 503813, bug 504104.

Reported using DrKonqi

Comment 1 TraceyC 2025-06-30 22:32:54 UTC

I'm afraid Plasma 5.27.11 and kdevelop 5.12 are unfortunately no longer eligible for support or maintenance from KDE.

If you need support for Plasma 5.27.11, or older versions of kdevelope, please contact your distribution, who bears the responsibility of providing support for older software in their "long-term support" releases.

If this issue is still reproducible in Plasma 6.4.1 (the latest released version), feel free to re-open this bug report.

Thanks for understanding.

Comment 2 Igor Kushnir 2025-07-05 06:17:42 UTC

*** Bug 506591 has been marked as a duplicate of this bug. ***