Indeed. Xara LX creates a lock file when it starts so it knows whether another copy of LX is around if you double click on a .xar file (to avoid running a second copy, the new copy then just tells the old copy to load the file). The lock file is removed when the program exits. However, if the program crashes, the lock file doesn't get removed, so when you start it again, it thinks the old program is about, tries (and fails) to communicate with it, and reports the problem. It's possibly being a bit OTT in reporting it, but it's sometimes useful to know if LX is not exiting cleanly (for instance if it crashes during shutdown).