Comment 11 for bug 1963762

Revision history for this message
Alexander (ak71vie) wrote :

I did as I said: I rebooted the ubuntu machine, opened sudo timekpra, and it works for strange reasons.

systemctl status timekpr

timekpr.service - Timekpr-nExT daemon service
     Loaded: loaded (/lib/systemd/system/timekpr.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-03-07 18:33:34 CET; 2h 9min ago
       Docs: file:/etc/timekpr/timekpr.conf
   Main PID: 1995 (timekprd)
      Tasks: 3 (limit: 18946)
     Memory: 19.3M
     CGroup: /system.slice/timekpr.service
             └─1995 /usr/bin/python3 /usr/lib/python3/dist-packages/timekpr/server/timekprd.py /usr/bin/timekprd

mar 07 18:33:34 server systemd[1]: Started Timekpr-nExT daemon service.

ps -ef | grep time*

root 1995 1 0 18:33 ? 00:00:15 /usr/bin/python3 /usr/lib/python3/dist-packages/timekpr/server/timekprd.py /usr/bin/timekprd
alex 3138 2741 0 18:34 ? 00:00:00 /usr/libexec/gsd-datetime
alex 3180 2993 0 18:34 ? 00:00:05 /usr/bin/python3 /usr/lib/python3/dist-packages/timekpr/client/timekprc.py /usr/bin/timekprc
alex 36390 3923 0 20:44 pts/0 00:00:00 grep --color=auto time*

no, I did not do sudo apt-get update after timekpr has hung up. Anyhow, thank you again.