Found Plinth Error in Logs (FB 23.19)

1

Hello,

I noticed an error in my FreedomBox logs about the Plinth service. This was from before the latest update (the error belongs to version 23.19).

The thing is, this error only popped up once. I’m not sure if it’s a big deal or if it’ll happen again. I didn’t get a chance to report this before the update.

I just wanted to share this information but wasn’t sure to report it because it looks like a one-time error.

Thanks!

Error log:

/usr/bin/plinth
Error: Operation: diagnostics: Running diagnostics, 'list' object has no attribute 'result'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/plinth/operation.py", line 63, in _catch_thread_errors
    self.return_value = self.target(*self.args, **self.kwargs)
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/plinth/modules/diagnostics/__init__.py", line 272, in _run_diagnostics
    if check.result != Result.PASSED:
       ^^^^^^^^^^^^
AttributeError: 'list' object has no attribute 'result'

CODE_ARGS
    (<plinth.operation.Operation object at 0xb18572b0>, AttributeError("'list' object has no attribute 'result'"))
CODE_FILE
    /usr/lib/python3/dist-packages/plinth/operation.py
CODE_FUNC
    _catch_thread_errors
CODE_LINE
    65
EXCEPTION_INFO
    (<class 'AttributeError'>, AttributeError("'list' object has no attribute 'result'"), <traceback object at 0xb186f548>)
EXCEPTION_TEXT
    Traceback (most recent call last): File "/usr/lib/python3/dist-packages/plinth/operation.py", line 63, in _catch_thread_errors self.return_value = self.target(*self.args, **self.kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/plinth/modules/diagnostics/__init__.py", line 272, in _run_diagnostics if check.result != Result.PASSED: ^^^^^^^^^^^^ AttributeError: 'list' object has no attribute 'result'
LOGGER
    plinth.operation
PRIORITY
    3
PROCESS_NAME
    MainProcess
SYSLOG_IDENTIFIER
    /usr/bin/plinth
THREAD_NAME
    Thread-450 (_catch_thread_errors)
_BOOT_ID
    124968d6737746cc813798406da3ab56
_CAP_EFFECTIVE
    0
_CMDLINE
    /usr/bin/python3 /usr/bin/plinth
_COMM
    plinth
_EXE
    /usr/bin/python3.11
_GID
    120
_HOSTNAME
    freedombox
_MACHINE_ID
    88e610466a674d4abb282a0ac902dbdd
_PID
    14787
_RUNTIME_SCOPE
    system
_SELINUX_CONTEXT
    unconfined 
_SOURCE_REALTIME_TIMESTAMP
    1698560131225392
_SYSTEMD_CGROUP
    /system.slice/plinth.service
_SYSTEMD_INVOCATION_ID
    38c289ea28624478bdab86de530c9771
_SYSTEMD_SLICE
    system.slice
_SYSTEMD_UNIT
    plinth.service
_TRANSPORT
    journal
_UID
    115
__CURSOR
    s=e6637ef7c1d34b9eaecae24ee9a9b495;i=d87c;b=124968d6737746cc813798406da3ab56;m=cce1146816;t=608d4d94057dc;x=9a5fda8c3a551d35
__MONOTONIC_TIMESTAMP
    879949539350
__REALTIME_TIMESTAMP
    1698560131225564
2

Thanks for reporting this. I believe it is due to a diagnostic check in the Date & Time app:

If that’s the case, then it should be fixed in 23.20.

1 Like