Error recognizing org.asamk.Signal

[nikkindev]

When I run the receive.py file, I get the following error

File "/home/user/miniconda3/envs/signal/lib/python3.9/site-packages/pydbus/proxy.py", line 44, in get ret = self.con.call_sync( gi.repository.GLib.Error: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.asamk.Signal was not provided by any .service files (2)

But the signa-cli had been started in daemon mode prior to this
./signal-cli -u <My-no.> daemon

[mh-g]

signal-cli can be run as dbus or system-dbus. The above starts it using normal dbus. Please take a look at https://github.com/AsamK/signal-cli/wiki/DBus-service#system-bus

[nikkindev]

Even after start is as system-dbus, I get this error
Now, at least it recognizes the service

raceback (most recent call last):
  File "receive.py", line 15, in <module>
    signal = bus.get('org.asamk.Signal')
  File "/home/user/miniconda3/lib/python3.7/site-packages/pydbus/proxy.py", line 47, in get
    0, timeout_to_glib(timeout), None)
gi.repository.GLib.Error: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.asamk.Signal': timed out (service_start_timeout=25000ms) (20)

[mh-g]

How powerful is your machine? Years ago, I tried signal-cli on a Raspberry Pi 3 and similar smaller platforms and found that signal-cli took too long to initialize. Often, the second call would work.

Have you tried other DBus clients?

Which version of signal-cli are you using? I have very similar code running with signal-cli 0.6.2.

[fbarbe00]

Even after start is as system-dbus, I get this error
Now, at least it recognizes the service

raceback (most recent call last):
  File "receive.py", line 15, in <module>
    signal = bus.get('org.asamk.Signal')
  File "/home/user/miniconda3/lib/python3.7/site-packages/pydbus/proxy.py", line 47, in get
    0, timeout_to_glib(timeout), None)
gi.repository.GLib.Error: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.asamk.Signal': timed out (service_start_timeout=25000ms) (20)

Make sure you have the config files configured correctly, that is: you either made a user called "signal-cli", or changed the user values in the different configuration files, and tread this:
Mind the fact that signal.service executes the signal-cli with "--config /var/lib/signal-cli". If you registered with user signal-cli, remove the config option.