triggercmdagent : Depends: nodejs-legacy but it is not installable

Hi, my first post and first time installation attemop on Ubuntu 17.10 with cinnamion desktop.

pete@ten:~/_batch$ sudo apt install ./triggercmdagent_1.0.1_amd64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'triggercmdagent' instead of './triggercmdagent_1.0.1_amd64.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
triggercmdagent : Depends: nodejs-legacy but it is not installable
E: Unable to correct problems, you have held broken packages.
pete@ten:~/_batch$ sudo apt install nodejs-legacy
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package nodejs-legacy is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
nodejs:i386 nodejs

E: Package 'nodejs-legacy' has no installation candidate
pete@ten:~/_batch$ sudo apt install nodejs

nodejs installs fine but I still get the same error on "sudo apt install ./triggercmdagent_1.0.1_amd64.deb"

Can anyone assist ?
Thanks
Pete

Russ

@superpan, thanks for letting me know I have this problem. I'll install a fresh Ubuntu 17.10 vm with Cinnamion desktop to see if I can reproduce this. I think the latest I tested on was 16.04.

@russ Thank-you

Russ

@superpan, I installed Ubuntu 17 and reproduced the problem. I'll try to fix it tomorrow. It should be easy to switch the dependency to the newer nodejs version. Thank you so much for telling me.

@russ Again.. Thank-you.

Russ

@superpan, please try again. I replaced the node-legacy dependency with nodejs.

I had to do "apt remove triggercmdagent" to remove the old one that depends on node-legacy before I could install the new version.

@russ I can confirm that the fix works.
I removed node-js and then installed triggercmdagent which automatically included node-js

I now need to work out why...
triggercmdagent.service: Failed at step EXEC spawning /usr/bin/ps: No such file or directory
A quick "whereis ps" shows it is in /bin/ps

I updated the triggercmdagent.service to change the

ExecStop=/usr/bin/ps aux ........
ExecStop=/bin/ps aux .....

The agent now seems to work and I can reboot my machine from the website but syslog has the following error when I use
systemctl stop triggercmdagent ...

Jan 23 15:55:19 ten systemd[1]: Stopping TRIGGERcmd Agent...
Jan 23 15:55:19 ten ps[2695]: error: garbage option
Jan 23 15:55:19 ten ps[2695]: Usage:
Jan 23 15:55:19 ten ps[2695]: ps [options]
Jan 23 15:55:19 ten ps[2695]: Try 'ps --help <simple|list|output|threads|misc|all>'
Jan 23 15:55:19 ten ps[2695]: or 'ps --help <s|l|o|t|m|a>'
Jan 23 15:55:19 ten ps[2695]: for additional help text.
Jan 23 15:55:19 ten ps[2695]: For more details see ps(1).
Jan 23 15:55:19 ten systemd[1]: triggercmdagent.service: Control process exited, code=exited status=1
Jan 23 15:55:19 ten systemd[1]: Stopped TRIGGERcmd Agent.
Jan 23 15:55:19 ten systemd[1]: triggercmdagent.service: Unit entered failed state.
Jan 23 15:55:19 ten systemd[1]: triggercmdagent.service: Failed with result 'exit-code'.

This is now beyond my amateur knowledge. Can I ignore this or is there something else to fix ?

Cheers
Pete

Russ

@superpan, thanks again for reporting a bug.

You can safely ignore that garbage option error. That ExecStop line doesn't even need to be in there. I'm building a new version right now that gets rid of that line, which gets rid of that error.

I noticed two other problems with the Linux agent. I had hardcoded /root/.TRIGGERcmdData as your data folder, but if you install the background service as a no-root user it should be /home/youruser/.TRIGGERcmdData. I fixed that.

The other problem is in Ubuntu 17 the tray icon doesn't show up unless you run this before running triggercmdagent:

export XDG_CURRENT_DESKTOP=Unity

I'll see if I can fix that tomorrow.

Hi Russ...
Ref: export XDG_CURRENT_DESKTOP=Unity

I am unsure whether this is relevant but...
Ubuntu 17.10 no longer uses UNITY, it now uses GNOME.

Russ

@superpan, the TRIGGERcmd agent is based on Electron, and there's an open bug in Electron that's preventing the icon from showing in Ubuntu now that it uses Gnome. I'm going to have to wait until the Electron developers fix this before I can put out a new version of the TRIGGERcmd agent that fixes this. In the meantime, that "export XDG_CURRENT_DESKTOP=Unity" command fixes it for me.

Here's more info about this bug:
https://github.com/electron/electron/issues/10887
https://github.com/electron/electron/issues/9046

@russ I could not get the "export XDG_CURRENT_DESKTOP=Unity" to resolve the icon issue. I read the two articles and others reported that it didn't work for them.

Another thought occurred to me, I had to change from Wayland to X11 to fix other 17.10 issues. Were you running Wayland or X11 ?
My test:
pete@ten:$ env | grep -i wayland
pete@ten:$ echo $XDG_SESSION_TYPE
x11
pete@ten:$

Russ

@superpan, you can see here I'm using wayland:

TRIGGERcmd Ubuntu