tdrop doesn't work with programs in a firejail sandbox

[Schweber]

tdrop is unable to hide programs that launched with tdrop but run in a firejail sandbox. Instead, tdrop launches another instance of the program when the command is run again e.g. tdrop -Aam chromium.

I suspect that firejail shields the programs from some information/access that tdrop needs for its functionality.

I tried to adapt the workaround for Flatpaks:

tdrop -m -n chromium --class=chromium firejail chromium

But nothing happens when running this command.

If i run tdrop -m -n chromium --class=chromium chromium the default behaviour is happening (multiple instances are started).

Is there a way to fix this? Maybe change something in tdrop or whitelist something in the firejail profile in order to allow tdrop to interface with the program running in the firejail sandbox correctly?

[noctuid]

Running things in firejail or flatpack can complicate things quite a bit for applications that already need special handling. I will look into allowing this when I get a chance.

Note to self: it might be necessary to allow the user to specific program names in some cases instead of just taking "firejail" as the program name. There should be a distinction added between the program name (which should be used for identifying special handling) and the actual program/flags to run.

[Schweber]

Thank you! This is off topic but i'm so glad that i discovered tdrop. I always wanted to be able to hide and show applications with a keyboard shortcut and not just run another instance of them.