@Russ Hi Russ! I have created new commands for testing purposes but only the ones that are marked as "foreground" were showing up on the website... So I used the option "remove background services" and then "install background services" and right after that the background commands appeared on website.... Not sure what happened, maybe something was stuck and cleared by itself after the reinstall...anyway, it's working properly now!! Thank you for all quick support, really appreciate that!
Best regards

@santana2196, oh that's true. Sorry. Please use one of the other conversational skills.

I think I'd recommend the TC skill in this case.

Also, please check out the portuguese documentation page about the conversational actions.

b2136dcf-8fc8-42ab-9492-d60585f744a0-image.png

f4e88fbc-ee18-4224-86a0-95546bf87f6c-image.png

@Russ thanks you now works

Thanks @Spiritus-Umbrarum. I'm working on updating the TRIGGERcmd .deb linux installer so it won't depend on libgconf-2-4 or libgconf2-4 anymore, but thank you for sharing the work-around in the meantime.

EDIT: I updated the Ubuntu agent so it no longer requires libgconf-2-4.

@Steve-Lee I use ubuntu 23.04 and default gnome 44. the strangest thing is that it only occurs when I configure some applications to open through triggercmd.
for example, I have configured a gnome-text-editor, which is in the screenshot, when I open it through alexa/triggercmd the error occurs, but nothing happens if I open it manually through the gnome menu. it also occurs with an application I wrote in python/gtk4 and another in python/gtk3, however the error does not occur when I open vscode

@Russ It's working! 👏🏿 👏🏿 Thank you very much!! 💪🏿

@Russ thanks Russ. I'm a super beginner with Linux but will give this a shot.

@Michael-Figueroa,

I see @Andy-Kutruff posted one here.

@russ

I'm using chrome and it worked with the following:

google-chrome /home/dmcnaugh/Downloads/Alarm_Arm.html

Thank you, Russ!

@PedroMartins, good. Sorry about the incompatibility.

Thanks @pirates. I just fixed it.

@Kelvin-Ferraz, awesome. I'm glad it's working.

@William-Mendes, you prefix your command with sudo to run it as root. Like this:

sudo /usr/local/bin/yourscript.sh

You'll need to add a line like this to your /etc/sudoers file so the TRIGGERcmd foreground agent can run the commands with sudo without a password prompt:

wmendes ALL = NOPASSWD: /bin/systemctl restart httpd.service, /bin/kill, /usr/local/bin/yourscript.sh

This article does a good job of explaining the sudoers file.

@Tiago-Mártires Pretty much the same thing but I added this line to crontab:

@reboot node /usr/share/triggercmdagent/resources/app/src/agent.js &

If you want this to load at system boot - be sure to enable the triggercmdagent,service

sudo systemctl enable triggercmdagent,service

@knipknap, nice! That's progress.

I'm not sure why the icon isn't showing. Can you think of anything that's not standard about your xwindows install? It show up for me and I took defaults when I installed Ubuntu Desktop v18

For now you can use some other editor to edit commands.json.

@dil-photos, not yet, but I'll look into building a 32bit deb file. Stay tuned.

EDIT 12/17/18:
@dil-photos, sorry but I found that they stopped making a 32bit NodeJS version. NodeJS is a dependency for the TRIGGERcmd agent. https://nodejs.org/en/download/

This method has no GUI, but one thing you could try is this. It worked for me.

sudo apt install nodejs-legacy git clone https://github.com/rvmey/TRIGGERcmd-Agent.git cd TRIGGERcmd-Agent node ./src/agent.js --console