Compatibility with Debian 12

[william siqueira]

Hello everyone, I hope you are doing well.

I did the test here as instructed, but I really think there is something that needs to be corrected in Triggercmd for Debian 12, because as you can see in the prints, by default it is already defining these commands, but in my account when I go to the option " View triggers", it only brings me to "Gnome Editor", if I change the name of it in the commands.json file it disappears from my account. So I assume this is really an incompatibility with Debian 12. Since it only brings a single command among the 4 defined in the file and if I change the name of the single command or even the command itself it disappears from my account.

[Russ]

@william-siqueira, the reason only Gnome Editor shows up is it's the only command with "ground":"foreground".

That's because you've only run the agent in foreground mode so far.

If you install the background agent, it will create triggers for those background commands too.

You can install the background agent with a command like this:

sudo sh /usr/lib/triggercmdagent/resources/app/src/installdaemon.sh

[william siqueira]

@Russ It still didn't work properly, only the "Gnome editor" shows up in my account.
Here are the installdaemon.sh installation prints, with the defined commands and the status up of my agent with the account.
If you don't have more options to solve the problem, I appreciate the help, I insisted on Trigger in debian because it was very useful when I was using it in Ubuntu 22.




[Russ]

@william-siqueira, thank you for the screenshots. That helps.

Notice the data folder for the background agent is in root's home folder, not your williams user.

/root/.TRIGGERcmdData

I also see No token exists. Login to request one. So you can probably fix it if you run:

sudo su -
triggercmdagent --console
(paste in your token)

Or you could copy your /home/william/.TRIGGERcmdData folder to /root/.TRIGGERcmdData so it won't create a second computer in your account because you already have a computerid.cfg file in /home/william/.TRIGGERcmdData and the background agent that will run as root will use that computer id.