Reproduction steps:
1. Extract the attached “IN-150096” project
2. Run “unity pipeline install --project-path <project>”
3. Edit the paths at the top of the “repro-duplicate-editor-instances.sh”
4. Run the script through a terminal
5. Open the “~/repro-output.log” log file
6. Compare the “PHASE A” and “PHASE B” sections of the output log
Actual result: 3 Editor instances reported when 1 is running
Expected result: 1 Editor instance reported
Reproducible with: 1.0.0-beta.3, 1.0.0-beta.4, 1.0.0-beta.5 (6000.0.82f1, 6000.3.23f1, 6000.5.10f1, 6000.6.0b10, 6000.7.0a5)
Reproducible on: Ubuntu 25.04, Ubuntu 24.04.4 (user)
Not reproducible on: No other environments tested
Notes:
- Affects both unity editors running and unity pipeline list. All three duplicate rows carry identical project name, project path, Editor version, and port 7800
- Cause: xvfb-run is a shell script and dbus-run-session is a session launcher. Both receive the Unity command line as their own arguments, and both must outlive the Editor to tear down Xvfb and the session bus respectively. The Unity invocation string is therefore present in three processes' argv at once, so argv-based discovery returns three hits for one Editor
- Severity differs by version. On beta.3 the duplicates block unity command eval outright with an ambiguity error and exit 6. On beta.4 and beta.5 eval resolves correctly and returns 4 despite the three rows, leaving an incorrect count as the remaining impact