SUMMARY A way to have Kile running a session for each opened project is to add "--new" to the desktop file command opening files: kile --new %U. While this was working well prior to Kile 3, the beta version now results in freezes in Dolphin when a session of Kile is opened and I click on another project. The freeze stops when I close the second Kile session with the following error: > Impossible for KDEInit to run "/usr/bin/kile" STEPS TO REPRODUCE 1. Add "--new" to the command run when clicking on Kile projects so that a new session is started each time you click on a project file (*.kilepr). 2. Click a first time on any project file. Kile starts as intended. 3. Click on a second project file. OBSERVED RESULT When the second Kile session starts, Dolphin freezes. When closing the second Kile session, Dolphin's freeze stops and an error is triggered stating "Impossible for KDEInit to run '/usr/bin/kile'" (loose translation from French). EXPECTED RESULT Dolphin should not freeze and the error message should not appear. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap/Tumbleweed (tested on both) KDE Plasma : 5.14.3 Qt : 5.11.2 KDE Frameworks : 5.52.0
An update on this bug with 2.9.93: the bug doesn't translate into Dolphin freeze anymore. Yet, it still exists on a different flavour. Now, using the "--new" option in the desktop file and opening a new project generates an issue where Kile doesn't close properly: the window is closed as expected, but the process is still active and can only be killed with "killall -9 kile". As long as the kile process is active, opening new projects does not work: clicking on a project file does nothing. Killing kile restores the ability to open projects.
Looking at old bug reports: this issue is now fixed.