AFAI can see, it is the weston-launch which does the bad thing.
If i, being root, start weston directly, it does work fine.
If i, being root, start weston indirect via weston-launch, the process
never returns to console and I can't login from via other shells.
This behave is the same with 1.7.0 and 1.7.90.
The commands I used to start weston:
# Weston direct
openvt -c 7 -w -v -- weston --backend=drm-backend.so --use-pixman
--log=/home/root/weston.log
openvt -c 7 -w -v -- weston --backend=fbdev-backend.so
--log=${HOME}/weston.log
# Weston via weston-launch
openvt -c 7 -w -v -- weston-launch -- --backend=drm-backend.so
--use-pixman --log=${HOME}/weston.log
openvt -c 7 -w -v -- weston-launch -- --backend=fbdev-backend.so
--log=${HOME}/weston.log
Cheers,
Thilo
Am 18.03.2015 12:03, schrieb Thilo Cestonaro:
Hey!
with the master HEAD + Dereks patches for FBDev transformation fix and
mine for the right pixman type, I can't use the machine after hitting
Ctrl+Alt+Backspace in weston.
Doesn't matter what I want to do, open a new ssh session, editing a
file with vi, or doing a local login. It all just hangs there and does
nothing.
After a reboot or before exiting weston, all was working.
I tried DRM and FBDev backend, both the same behave.
weston is started via:
DRM:
openvt -c 7 -w -v -- weston-launch --tty /dev/tty7 --
--backend=drm-backend.so --use-pixman --log=${HOME}/weston.log
FBDev:
openvt -c 7 -w -v -- weston-launch --tty /dev/tty7 --
--backend=fbdev-backend.so --log=${HOME}/weston.log
No errors in the logs, but appended anyway.
I will try it with some early build to.
Cheers,
Thilo
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
