• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
TRIGGERcmd
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Compatibility with Debian 12

General Discussion
2
4
199
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W
    william siqueira
    last edited by Aug 29, 2023, 9:13 PM

    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.![alt text](7af063be-c5bf-45a8-8d9c-adb186d0f44c-image.png image url)
    ![alt text](6cf47751-b3c7-4900-8e3b-d5051d91f7de-image.png image url)

    R 1 Reply Last reply Aug 30, 2023, 12:45 AM Reply Quote 0
    • R
      Russ @william siqueira
      last edited by Russ Aug 30, 2023, 1:32 AM Aug 30, 2023, 12:45 AM

      @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
      

      Russell VanderMey

      W 1 Reply Last reply Aug 30, 2023, 10:15 AM Reply Quote 0
      • W
        william siqueira @Russ
        last edited by Aug 30, 2023, 10:15 AM

        @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.

        ![alt text](6ff73ced-fe90-458e-b2fb-06285fa35d7d-image.png image ur)

        ![alt text](088e8d43-139b-4d68-8a5e-12870aa63208-image.png image url)

        ![alt text](53b421cb-32f3-4118-af67-7d33a1b95d97-image.png image url)

        R 1 Reply Last reply Aug 30, 2023, 11:58 AM Reply Quote 0
        • R
          Russ @william siqueira
          last edited by Russ Aug 30, 2023, 11:59 AM Aug 30, 2023, 11:58 AM

          @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.

          Russell VanderMey

          1 Reply Last reply Reply Quote 0
          1 out of 4
          • First post
            1/4
            Last post