Reaper's "Show REAPER resource path in finder/explorer" button is non-functional

[pancaek]

Describe the bug

The "Show REAPER resource path in finder/explorer" button under Options does not launch a file manager.

Steps To Reproduce

Steps to reproduce the behavior:

1. Open a Reaper project
2. Click "Show REAPER resource path in finder/explorer" under Options in the top menu
3. See that no file manager is opened.

Expected behavior

I would expect my configured file manager (Files/Nautilus, since I'm using gnome) to open.

Additional context

I attempted to run reaper from the terminal to capture relevant errors, but clicking the button just silently fails.

Notify maintainers

@ilian @orivej @uniquepointer @viraptor

Metadata

Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

[pancaek@pancake-pc:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.45, NixOS, 24.05 (Uakari), 24.05.20240815.c3d4ac7`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.5`
 - nixpkgs: `/nix/store/7sprarsdfz9qcd7859phvr9nvhi14mri-source`

---

Add a 👍 reaction to issues you find important.

[viraptor]

I don't think I'll have time to debug this for a few days, but if you can provide more information then running reaper through strace -f and capturing what exactly happens when you click that button would be really useful. If you're not up for that, I'll try to check soon.

[pancaek]

For sure, I'll get back to you later today.

[pancaek]

I'm way out of my depth to narrow down the log to a particular section myself, but I made the full log into a gist so there's something to look through.
Hopefully I did this right: https://gist.githubusercontent.com/pancaek/ba3bbac10208850e3691e5dc0fbc6f0e/raw/741cdf4f7b538fc8af973704a103e669ece92d0f/gistfile1.txt

Sorry for the giant file 😔

[viraptor]

It looks like the xdg-open is hardcoded and not found:

27172 execve("/usr/bin/xdg-open", ["/usr/bin/xdg-open", "/home/pancaek/.config/REAPER"], 0x7ffd718c7b38 /* 100 vars */ <unfinished ...>
...
27172 <... execve resumed>)             = -1 ENOENT (No such file or directory)

Since you're on nixos that may be tricky to solve. We could try something like buildFHSEnv, but in practice reaper should solve this by not hardcoding the path.

I'll play with this later.

[viraptor]

Reported at https://forum.cockos.com/showthread.php?p=2808822

[pancaek]

This code is pretty awful but I managed to make a libswell package and patch it with what was given on the cockos forum, and it appears to work when I override reaper's installPhase and replace the distributed libSwell.so.

libswell.zip

I'm not comfortable enough maintaining packages to maintain this myself, but perhaps it could be incorporated somehow?

[orivej]

@viraptor or @pancaek, could you reply at https://forum.cockos.com/showthread.php?p=2808822 that this works and ask for this change to be committed? Then we could keep using libswell that comes with Reaper

[orivej]

I have had a need for this too - xdg-open is used to open the plot after render - but I had linked /run/current-system/sw/bin/xdg-open to /usr/bin/xdg-open to work around this.

[pancaek]

(I would ask for it to be committed but the forum registration is being strange so I don't think I can do it)

[pancaek]

How long do we want to wait to hear back from the reaper forum before handling the patch? I've cleaned up the original slapdash derivation I wrote, significantly. I could put that in a draft PR, at least, if that's useful.

[viraptor]

I gave it another go at justinfrankel/WDL#26 since some PRs seem to be merged from the mirror.
If it doesn't get an answer this week, could you post your nix file, please? We'll need to figure out which version was used for specific reaper version we're releasing.

[pancaek]

libswell.zip
Here you are! I was just recently playing with sparse checkout to avoid unnecessarily huge downloads, and it seems to work fine, other than that its very standard (I'm not familiar enough with C++ to say if this might cause other issues somehow so maybe it's better to do full checkout?).

The commit I picked to build at the moment is a little arbitrary, I'm not sure how to figure that part out properly.