[Bug]: Codelite crashing when opening

[RainersV98]

What happened?

Using F41, after updates "sudo dnf update" codelite opens up and crashes which freezes my laptop. It takes few minutes to Force quit it and after that my keyboard stops working. Tried to read logs from journalctl, but couldn't find anything interesting there. I'm a beginner on Linux and Fedora is my first distro so I don't really know how to troubleshoot something like this yet. It was working fine few days before.

Codelite was installed using RPM following Codelite guide: https://docs.codelite.org/downloads/download/#codelite-rpms

Version

17.0.0

Operating system

Linux

Steps to reproduce

No response

Relevant log output

No response

[UffeJakobsen]

Maybe systemd has recorded the codedump for you...

Try the following commands:
coredumpctl list
coredumpctl list codelite
coredumpctl info codelite

[eranif]

which CodeLite version?

Can you launch codelite from a terminal and under a debugger?

[RainersV98]

Maybe systemd has recorded the codedump for you...

Try the following commands: coredumpctl list coredumpctl list codelite coredumpctl info codelite

Showing that no Core Dumps were found when using "coredumpctl list codelite" but the coredumpctl list shows Codelite workspaces being present.

[RainersV98]

which CodeLite version?

Can you launch codelite from a terminal and under a debugger?

17.0-1 which I downloaded from here https://repos.codelite.org/rpms-17.0/fedora/41/.

I'm running codelite from terminal, but don't know how to run it from a debugger. Although i'm not getting any error logs on Gnome log app which are related to Codelite.

[UffeJakobsen]

Maybe systemd has recorded the codedump for you...
Try the following commands: coredumpctl list coredumpctl list codelite coredumpctl info codelite

Showing that no Core Dumps were found when using "coredumpctl list codelite" but the coredumpctl list shows Codelite workspaces being present.

I'm not really sure what you mean by "Codelite workspaces being present" - can you provide parts of output from coredumpctl listas an example ?

[RainersV98]

Maybe systemd has recorded the codedump for you...
Try the following commands: coredumpctl list coredumpctl list codelite coredumpctl info codelite

Showing that no Core Dumps were found when using "coredumpctl list codelite" but the coredumpctl list shows Codelite workspaces being present.

I'm not really sure what you mean by "Codelite workspaces being present" - can you provide parts of output from coredumpctl listas an example ?

"Sun 2024-12-29 09:48:59 EET 12224 1000 1000 SIGABRT present /home/rainersv/cpp-workspaces/eka-cpp-md/build-Debug/bin/eka-cpp-md-3 35.2K
Sun 2024-12-29 09:49:19 EET 12301 1000 1000 SIGABRT present /home/rainersv/cpp-workspaces/eka-cpp-md/build-Debug/bin/eka-cpp-md-3 35.2K
Sun 2024-12-29 09:51:33 EET 12667 1000 1000 SIGABRT present /home/rainersv/cpp-workspaces/eka-cpp-md/build-Debug/bin/eka-cpp-md-3 35.2K"
These are workspaces created in codelite, but I don't know if they are related to codelite crashing. Also I don't get any errors in "Problem Reporting" app.

[UffeJakobsen]

Maybe systemd has recorded the codedump for you...
Try the following commands: coredumpctl list coredumpctl list codelite coredumpctl info codelite

Showing that no Core Dumps were found when using "coredumpctl list codelite" but the coredumpctl list shows Codelite workspaces being present.

I'm not really sure what you mean by "Codelite workspaces being present" - can you provide parts of output from coredumpctl listas an example ?

These are workspaces created in codelite, but I don't know if they are related to codelite crashing. Also I don't get any errors in "Problem Reporting" app.

Ah now I got it - these are crash reports of your own programs (projects) - they are not in any way related to the Codelite crashes

[RainersV98]

Maybe systemd has recorded the codedump for you...
Try the following commands: coredumpctl list coredumpctl list codelite coredumpctl info codelite

Showing that no Core Dumps were found when using "coredumpctl list codelite" but the coredumpctl list shows Codelite workspaces being present.

I'm not really sure what you mean by "Codelite workspaces being present" - can you provide parts of output from coredumpctl listas an example ?

These are workspaces created in codelite, but I don't know if they are related to codelite crashing. Also I don't get any errors in "Problem Reporting" app.

Ah now I got it - these are crash reports of your own programs (projects) - they are not in any way related to the Codelite crashes

Do you know how to open codelite under debugger as @eranif mentioned?

[RainersV98]

Okay, so, I managed to open codelite fron CLI with "codelite -w="random"" and everything seems fine until I try to open any of my workspaces. Then it stops responding and keyboard doesn't work. When my focus window is anything else and not Codelite then it comes back to working and I noticed a message in Gnome Logs seen in picture.

[UffeJakobsen]

Try this command from your terminal:

gdb -f -ex "run" -ex "thr apply all bt" -ex "inf thr" -ex "bt" -ex "quit" --args codelite

When CodeLite crashes thread overview and all thread stacks are dumped in your terminal

[RainersV98]

Try this command from your terminal:

gdb -f -ex "run" -ex "thr apply all bt" -ex "inf thr" -ex "bt" -ex "quit" --args codelite

When CodeLite crashes thread overview and all thread stacks are dumped in your terminal

Ran the code, opened codelite. When I open codelite, it tries to open a workspace straight away, could there be problem with my workspace?

[UffeJakobsen]

Try this command from your terminal:

gdb -f -ex "run" -ex "thr apply all bt" -ex "inf thr" -ex "bt" -ex "quit" --args codelite

When CodeLite crashes thread overview and all thread stacks are dumped in your terminal

Ran the code, opened codelite. When I open codelite, it tries to open a workspace straight away, could there be problem with my workspace?

I guess that option "Load last session at startup" is enabled ?

Menu path "Settings" / "Preferences" / "Misc" / "Load last session at startup"

Not sure how you can change this option if CL crashes immediately...
But you could edit file ~/.codelite/config/codelite.conf - look for option RestoreLastSession