Read the statement by Michael Teeuw here.
Issue with latest build of Karsten’s docker labwc container?
-
Apologies if the title is an incorrect conclusion.
As using MagicMirrorOs that uses Karsten’s docker build.
Noticed my screen at a tty login prompt instead of displaying my configuration that has been running a couple of weeks.
After investigating a little, I can see the labwc container keeps restarting with the below error messages in the logs.
It looks like it did pull of the latest version of the container ~3 hours ago, and I see that is when a new version of the content was published.
- Is there an issue with th*e latest version of the labwc container?
- Or any suggestions on troubleshooting?
scottwalsh@calendar:/opt/mm/run $ docker images REPOSITORY TAG IMAGE ID CREATED SIZE karsten13/labwc latest 8e88d2ea284a 3 hours ago 475MB karsten13/magicmirror fat 4e817d6adb5a 2 days ago 1.59GB karsten13/magicmirror latest 1d9d652de531 2 days ago 1.01GB karsten13/mmpm latest 44cfa75bf098 5 days ago 841MB containrrr/watchtower latest a157fa84f431 15 months ago 14MB scottwalsh@calendar:/opt/mm/run $ docker logs labwc sudo: seatd: command not found 00:00:00.523 [ERROR] [libseat] [libseat/backend/logind.c:621] Could not get primary session for user: No data available 00:00:00.601 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied 00:00:00.602 [ERROR] [libseat] [seatd/seat.c:70] Could not open tty0 to update VT: Permission denied 00:00:00.602 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied 00:00:00.602 [ERROR] [libseat] [seatd/seat.c:80] Could not open terminal for VT 0: Permission denied 00:00:00.602 [ERROR] [libseat] [seatd/seat.c:544] Could not open VT for client 00:00:00.602 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied 00:00:00.602 [ERROR] [libseat] [seatd/seat.c:94] Could not open terminal to clean up VT 0: Permission denied 00:00:10.606 [ERROR] [backend/backend.c:105] Timeout waiting session to become active 00:00:10.606 [ERROR] [backend/backend.c:407] Failed to start a DRM session 00:00:10.652 [ERROR] [../src/server.c:463] unable to create backend Some friendly trouble-shooting help =================================== If a seat could not be created, this may be caused by lack of permission to the seat, input and video groups. If you are using a systemd setup, try installing polkit (sometimes called policykit-1). For other setups, search your OS/Distro's documentation on how to use seatd, elogind or similar. This is likely to involve manually adding users to groups. If the above does not work, try running with `WLR_RENDERER=pixman labwc` in order to use the software rendering fallback 00:00:11.825 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied 00:00:11.825 [ERROR] [libseat] [seatd/seat.c:94] Could not open terminal to clean up VT 0: Permission denied sudo: seatd: command not found 00:00:00.038 [ERROR] [libseat] [libseat/backend/logind.c:621] Could not get primary session for user: No data available 00:00:00.044 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied 00:00:00.044 [ERROR] [libseat] [seatd/seat.c:70] Could not open tty0 to update VT: Permission denied 00:00:00.044 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied 00:00:00.044 [ERROR] [libseat] [seatd/seat.c:80] Could not open terminal for VT 0: Permission denied 00:00:00.044 [ERROR] [libseat] [seatd/seat.c:544] Could not open VT for client 00:00:00.045 [ERROR] [libseat] [common/terminal.c:162] Could not open target tty: Permission denied 00:00:00.045 [ERROR] [libseat] [seatd/seat.c:94] Could not open terminal to clean up VT 0: Permission denied 00:00:10.054 [ERROR] [backend/backend.c:105] Timeout waiting session to become active 00:00:10.054 [ERROR] [backend/backend.c:407] Failed to start a DRM session 00:00:10.061 [ERROR] [../src/server.c:463] unable to create backend
-
fixed now, you can restart the pi (it will need some time to pull the new image before working) or
cd /opt/mm/run docker compose pull docker compose up -d
-
Thanks for the finding.
The labwc image is built weekly and after a first look in the logs (comparing to the week before) it seams
seatd
is not installed anymore.Have to dig deeper …
-
fixed now, you can restart the pi (it will need some time to pull the new image before working) or
cd /opt/mm/run docker compose pull docker compose up -d
-