This issue does not happen always. I captured this log when I saw this happen:
1710515395.253525 [INFO] No internet connection, showing WiFi onboarding.
1710515395.278330 [ERROR] Task failed
Traceback (most recent call last):
File "/opt/ubo/env/lib/python3.11/site-packages/ubo_app/utils/async_.py", line 44, in wrapper
await awaitable
RuntimeError: Task <Task pending name='Task-44' coro=<create_task.<locals>.wrapper() running at /opt/ubo/env/lib/python3.11/site-packages/ubo_app/utils/async_.py:44>> got Future <_GatheringFuture pending> attached to a different loop - extra: {
"awaitable": "<_GatheringFuture pending>"
}
1710515395.280860 [ERROR] Task failed
Traceback (most recent call last):
File "/opt/ubo/env/lib/python3.11/site-packages/ubo_app/utils/async_.py", line 44, in wrapper
await awaitable
RuntimeError: Task <Task pending name='Task-54' coro=<create_task.<locals>.wrapper() running at /opt/ubo/env/lib/python3.11/site-packages/ubo_app/utils/async_.py:44>> got Future <_GatheringFuture pending> attached to a different loop - extra: {
"awaitable": "<_GatheringFuture pending>"
}
1710515399.043631 [ERROR] Not able to connect to pulseaudio
Traceback (most recent call last):
File "/opt/ubo/env/lib/python3.11/site-packages/ubo_app/services/000-sound/audio_manager.py", line 62, in initialize_audio
with pulsectl.Pulse('set-default-sink') as pulse:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/ubo/env/lib/python3.11/site-packages/pulsectl/pulsectl.py", line 380, in __init__
try: self.connect(autospawn=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/ubo/env/lib/python3.11/site-packages/pulsectl/pulsectl.py", line 443, in connect
if self.connected is False: raise PulseError('Failed to connect to pulseaudio server')
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
pulsectl.pulsectl.PulseError: Failed to connect to pulseaudio server
1710515436.407206 [INFO] Opening audio file for playback - extra: {
"filename_": "/opt/ubo/env/lib/python3.11/site-packages/ubo_app/services/000-sound/sounds/done.wav"
}
This issue does not happen always. I captured this log when I saw this happen: