Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

toggling monitor crashes kodi kiosk #275

Closed
mm1ke opened this issue Sep 10, 2023 · 3 comments
Closed

toggling monitor crashes kodi kiosk #275

mm1ke opened this issue Sep 10, 2023 · 3 comments

Comments

@mm1ke
Copy link

mm1ke commented Sep 10, 2023

Hi,

I hope this is the correct place to open this issue.

I'm using cage to start kodi-standalone on my TV (it's actually just a big monitor). The TV is connected via HDMI.
Usually i can start kodi-standalone with something like:
su kodi -c "XDG_RUNTIME_DIR=/home/kodi cage /usr/bin/kodi-standalone". This works as expected. In reality i'm using start-stop script to start kodi with the system.
However, my TV is rarely truned on. kodi however is usually running all the time. Now when i turn off my TV (via remote control), kodi crashes and i have to kill the process alongside with cage.

When i start kodi with the above command and turn off the monitor I see following in the terminal:

amdgpu: amdgpu_cs_ctx_create2 failed. (-13)
libva info: VA-API version 1.18.0
libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_18
libva info: va_openDriver() returns 0
amdgpu: amdgpu_cs_ctx_create2 failed. (-13)
--------> here is the monitor turned off
terminate called after throwing an instance of 'std::runtime_error'
  what():  poll() signalled error condition on Wayland socket
/usr/bin/kodi: line 186:  8298 Aborted                 ${KODI_BINARY} $SAVED_ARGS
Crash report available at /home/kodi/kodi_crashlog-20230910_124551.log
--------> that's were i killed it with strg+c
^C
Session terminated, killing shell...^C ...killed.                

s2 ~ # terminate called after throwing an instance of 'std::system_error'
  what():  wl_display_roundtrip_queue: Connection reset by peer
/usr/bin/kodi: line 186:  8427 Aborted                 ${KODI_BINARY} $SAVED_ARGS
Crash report available at /home/kodi/kodi_crashlog-20230910_124626.log
terminate called after throwing an instance of 'std::runtime_error'
  what():  Could not connect to Wayland display server via name
/usr/bin/kodi: line 186:  8463 Aborted                 ${KODI_BINARY} $SAVED_ARGS
Crash report available at /home/kodi/kodi_crashlog-20230910_124626.log
/usr/bin/kodi --standalone --chdir /home/kodi --pidfile /var/run/kodi.pid --user kodi --background --make-pidfile -- has exited in an unclean state 3 times in the last 56 seconds.
Something is probably wrong

Until now i've used the x11 backend from kodi and started it with xinit. With the x11 backend, turning off/on my TV worked flawless.

It would be great if that could be archived with wayland/cage too as i obliviously don't want to run my TV all the time :)

Cage version 0.1.5

@joggee-fr
Copy link
Collaborator

Hi @mm1ke,
Did you try the current HEAD version of Cage or the last release (0.1.5)?

@mm1ke
Copy link
Author

mm1ke commented Sep 10, 2023

Latest release (0.1.5)
Give me a few minutes, then i can test current HEAD

@mm1ke
Copy link
Author

mm1ke commented Sep 10, 2023

@joggee-fr
It works (Cage version 0.1.5-a769943 (branch 'HEAD'))! I suggest making a new release. :)

@mm1ke mm1ke closed this as completed Sep 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants