https://bugs.kde.org/show_bug.cgi?id=403717
--- Comment #4 from Jonathan Gilbert <c6kargn...@liamekaens.com> --- Agreed :-) Any case where communication with an external process is not precise enough to guarantee that the instance that launches it is the one that connects to it should be considered a bug, and if there are any other cases where an action assumes that a system resource (such as a file path) can simply be used in way that causes two concurrent instances to collide with each other should be considered a bug. An approach used by many other programs is to put the process ID into the path somewhere (e.g. a separate directory per process) so that it is completely impossible for two instances to interfere with each other. Imagine if Microsoft was like, "Well, you can run multiple instances of Microsoft Word if you _want_, but if you tell the first one to print, you might actually get the second one sent to the printer" or something. :-P -- You are receiving this mail because: You are watching all bug changes.
