Hi,
I'm trying to run python-validity on arch. I am having some issues which I am not able to pinpoint yet, but was trying to stop the service and running "systemctl stop python3-validity" is causing the service to restart.
This is the systemd and dbus messages I get:
jun 18 23:44:44 pf1pwlth systemd[1]: Stopping python-validity driver dbus service...
jun 18 23:44:44 pf1pwlth systemd[1]: python3-validity.service: Deactivated successfully.
jun 18 23:44:44 pf1pwlth systemd[1]: Started python-validity driver dbus service.
jun 18 23:44:44 pf1pwlth dbus-service[33272]: /usr/lib/python-validity/dbus-service:33: PyGIDeprecationWarning: Since version 3.11, calling threads_init is no longer needed. See: https://wiki.gnome.org/PyGObject/Threading
jun 18 23:44:44 pf1pwlth dbus-service[33272]: GLib.threads_init()
On the actual debug prints of python-validity I don't see much that seems related to this, apart from these lines:
jun 18 23:44:44 pf1pwlth python3[32710]: INFO:root:Caught signal 2. Stopping...
jun 18 23:44:44 pf1pwlth python3[32710]: DEBUG:root:In atexit handler
jun 18 23:44:44 pf1pwlth DEBUG:root:atexit[32710]: forcing reboot
I am not sure but the forcing reboot part is about the usb device? or is it related to the service?
Regards
José
Hi,
I'm trying to run python-validity on arch. I am having some issues which I am not able to pinpoint yet, but was trying to stop the service and running "systemctl stop python3-validity" is causing the service to restart.
This is the systemd and dbus messages I get:
On the actual debug prints of python-validity I don't see much that seems related to this, apart from these lines:
I am not sure but the forcing reboot part is about the usb device? or is it related to the service?
Regards
José