#15633: Single Launch Flag Ignored for Symbolic Linked Executables
-------------------------------------------------+-------------------------
Reporter: AGMS | Owner: jscipione
Type: bug | Status: new
Priority: normal | Milestone:
| Unscheduled
Component: Applications/Deskbar | Version:
Keywords: B_SINGLE_LAUNCH Symbolic Link | R1/Development
Executable | Blocked By:
Blocking: | Has a Patch: 0
Platform: All |
-------------------------------------------------+-------------------------
As described in https://www.haiku-os.org/legacy-docs/bebook/BRoster.html
executables with this flag should only have one instance running if
started from the same executable file. Running that program a second time
should just send the existing instance a BMessage with some startup
parameters. For example, with StyledEdit, if you run it a second time by
double clicking on it in /boot/system/apps/StyledEdit, you get a window
named "Untitled 2".
However, if you run the program through a symbolic link, the system
doesn't see it as being the same program and starts it running a second
time. This happens if you use the Deskbar menu, which is essentially a
list of symbolic links to the real executables. For example, running
StyledEdit a second time from the menu brings up another "Untitled 1"
window, and there are two StyledEdits listed in ProcessController.
The weird thing is that symbolic links work in Terminal. If you use
`/boot/system/data/deskbar/menu/Applications/StyledEdit &` to start it up,
it works properly.
So, could be a bug in DeskBar, or in BRoster's launching method, or
something else. Possibly somewhere where the code doesn't follow a
symbolic link to its target when seeing if it is the same executable file
as the running program with the same signature.
--
Ticket URL: <https://dev.haiku-os.org/ticket/15633>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
