After intentional weston crash, on relaunch it throws error "/dev/tty63 is already in graphics mode"
Currently, I am running Weston on arm32 (Linux version 5.0.1) board as a display server. On board I launched a docker container inside which X (X11) server will run. Once the docker container is stopped when I try to rerun Weston the following error occurs.
[01:12:12.777] /dev/tty63 is already in graphics mode, is another display server running?
[01:12:12.777] fatal: drm backend should be run using weston-launch binary, or your system should provide the logind D-Bus API.
[01:12:12.778] fatal: failed to create compositor backend
[01:12:12.779] Internal warning: debug scope 'drm-backend' has not been destroyed.
[01:12:12.780] Internal warning: debug scope 'key_drm_disable_hw_only_compositing' has not been destroyed.
[01:12:12.780] Internal warning: debug scope 'key_drm_swap_zpos_order' has not been destroyed.
Although it is not a bug in Weston, is there a way to reclaim tty from Weston itself?