Kdevelop: crash when opening the configuration dialog

Help
1

kdevelop 6.5.260403 (26.04.3) crashes when opening the configuration dialog. This happens in a new user session also.

This is in stdout on start:

kdevplatform.shell: Unable to find a plugin named ’ “kateprojectplugin” '!
qt.core.qobject.connect: QObject::connect(KateApp, KateTextHintManager): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(QObject, KTextEditorIntegration::MainWindow): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect: No such signal KDevelop::MainWindow::tabForToolViewAdded(QWidget *, QWidget *)
qt.core.qobject.connect: QObject::connect: (sender name: ‘MainWindow’)
qt.core.qobject.connect: QObject::connect(KateApp, DiagnosticsView): invalid nullptr parameter
kdevelop.plugins.qthelp: could not find QCH file in directory “/usr/share/doc/qt6”
cat: /home/user/.local/share/kdevelop/sessions/{638d4364-8923-4eee-8fac-33fb3f61167d}/default.sh: Aucun fichier ou dossier de ce nom

The following appears when it crashes:

kf.texteditor: mode “cppstyle” requires a different highlight style: highlighting “None” with style “” but script requires “C++”
Erreur de segmentation (core dumped)kdevelop

Can someone confirm it and suggest a fix?

Thank you.

Operating System: Arch Linux 
KDE Plasma Version: 6.7.2
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.1.3-arch1-2 (64-bit)
Graphics Platform: Wayland
2

Hi, which configuration dialog? Do you have a backtrace?

3

Hello,

Menu bar / Configuration / Configure kdevelop

and

Right click on a project / Open configuration

No. If you instruct how to do that, I’ll try to get one. It the release build of a standard Arch package.

4

I don’t know how arch handles debug symbols. The best I can do is point you to this page:
Debugging/Getting traces - ArchWiki

If you’re running a KDE plasma session, an automatic crash reporter should try handling the backtrace.

Also, looking at the logs: is there any chance you just updated and your system is in an inconsistent state?

5

I could get this backtrace after Configuration / Configure kdevelop menu:

Thread 1 “kdevelop” received signal SIGSEGV, Segmentation fault.
0x00007fffbcdf848c in AStylePlugin::predefinedStyles (this=)
at /usr/src/debug/kdevelop/kdevelop-26.04.3/plugins/astyle/astyle_plugin.cpp:297
297 createPredefinedStyle(QStringLiteral(“GNU”)),
(gdb) bt
#0 0x00007fffbcdf848c in AStylePlugin::predefinedStyles (this=)
at /usr/src/debug/kdevelop/kdevelop-26.04.3/plugins/astyle/astyle_plugin.cpp:297
Backtrace stopped: Cannot access memory at address 0x7fff00000008
(gdb)

I did update just before finding the crash indeed. I’ll try later on.

Thank you.

6

Check the update is complete, try logout/login and/or reboot.

7

This was done with no effect.

The disrupting update was done this morning, and repeated a few time throughout the day. The few more updated packages did not resolve the issue. I’ll keep trying in the coming days.

Thank you.

8

After removing the astyle package, the configuration dialog windows do not crash kdevelop. Since I don’t use these formatting utilities, it’s not a loss at all.

Thanks for you input throughout and regards.

9

Great that you figured it out. I checked: I have astyle installed, and can’t reproduce this crash. Hopefully “just” a packaging issue.

10

kdevelop 6.5.260403 (26.04.3) no longer crashes when the configuration dialogs are shown, with the astyle package installed.

Operating System: Arch Linux  
KDE Plasma Version: 6.7.3 
KDE Frameworks Version: 6.28.0 
Qt Version: 6.11.1 
Kernel Version: 7.1.4-arch1-1 (64-bit) 
Graphics Platform: Wayland