--debug-log=SOME.LOG
(thats a soft hint to tell us what your system is when you post such a message).
I have laz 2.0.10 on deb 11.5.
- the IDE closes without any notification / no error dialog
Could you start the IDE in gdb please?
NOTE, if your IDE is build without debug info, you need to rebuild it with -gw.
- check the size of your lazarus executable. If it is greater 100mb, then it likely has debug info
- to rebuild go menu: Tools > "Configure build lazarus", and in the memo "custom options" enter/add: -gw
then press build
gdb -ex r -ex bt lazarus > somefile.txt
I guess in your case "gdb -ex r -ex bt /usr/bin/lazarus-ide" => so long as lazarus-ide is linked to "lazarus", but not to "startlazarus" (the startlazarus that comes with the installation)
If the IDE crashes "somefile.txt" should (towards the very end) contain a stacktrace.
It should contain
- address (in hex)
- file/unit names and linenumbers.
If it has a stacktrace, but address only (no files/lines) then debug info was missing.
Wenn done, gdb will still be running. (and with it the dead lazarus process)
Since you have no command line to it, you need to "kill -9" the gdb process.
To avoid gdb hanging around you can try
gdb -ex "set confirm off" -ex r -ex bt -ex kill -ex q lazarus > somefile.txt
It seems to open up his windows for a moment, along with the startup lpi, but then all them close. The splash screen remains visible, and eventually it also closes itself after a while
- check the size of your lazarus executable. If it is greater 100mb, then it likely has debug info
I hadn't paid attention to 2.0.12
You should really upgrade.