Comment 1 for bug 1830348

Sebastien Bacher (seb128) wrote :

The isssue seems an incorrectly handler of error cases

'Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 604, in msg_reply_handler
    reply_handler(*message.get_args_list(**get_args_opts))
  File "/usr/lib/python3/dist-packages/softwareproperties/gtk/LivepatchPage.py", line 363, in _enabled_reply_handler
    timeout=1200)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 137, in __call__
    **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 584, in call_async
    message.append(signature=signature, *args)
TypeError: Expected a string or unicode object'

Looking at some of the reports their journal log have such errors

'canonical-livepatch[851]: cannot disable machine: cannot send request: Delete https://livepatch.canonical.com/api/machine-tokens: net/http: TLS handshake timeout
update-notifier.desktop[1556]: ERROR:dbus.connection:Unable to set arguments (True, None) according to signature 'bs': <class 'TypeError'>: Expected a string or unicode object'

or

'canonical-livepatch[1161]: error in livepatch check state: check-failed
canonical-livepatch[1161]: No payload available.
update-notifier.desktop[3255]: ERROR:dbus.connection:Unable to set arguments (False, None) according to signature 'bs': <class 'TypeError'>: Expected a string or unicode object'