Summary: | weston-launch freezes the system | ||
---|---|---|---|
Product: | Wayland | Reporter: | iquequeisso |
Component: | weston | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | 1.2.1 | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
iquequeisso
2014-01-25 01:28:04 UTC
Could you try to capture the weston log with something like: weston-launch -- --log=weston.log I don't recall the quality of weston-launch in 1.2.1... but I know it was in a state of flux/experimental for a while. Could you try a newer version? FWIW, Weston just released 1.4.0. Also I won't be able to help much for an AMD + gentoo setup, but someone else might have more knowledge of it than I. tried weston-launch -- --log=weston.log and weston-launch --log=weston.log neither worked (for some reason the freezing prevents the log being created/saved) I was trying this version because it's last in official tree. But I'll follow your advice and add x11 overlay to try weston-1.3.91 with wayland-1.4 Seems like the problem is in my weston.ini, for some reason weston-launch works for keymap_layout=us but it doesn't for keymap_layout=br or keymap_layout=br-abnt2 (I tested in weston 1.3.91 and there is the same problem Looks like Weston does the wrong thing if it can't compile the specified keymap. I just sent a patch to the mailing list that should make it handle the failure without crashing. But given the fact that the 'br' layout fails to compile for you indicates that there might be something wrong with your installation. Perhaps libxkbcommon wasn't configured to look for the xkb files in the right place. Ander Conselvan de Oliveira, I removed weston 1.2.1 and installed 1.4. In this version I'm able to set any keyboard layout I want so I think it's a 1.2.1 problem. commit 4d363cfcf6025db2277005845957e0b0e956ebd0 Author: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com> Date: Fri Jan 31 17:35:45 2014 +0200 input: Fix weston_seat_init_keyboard() error path The pointer seat->keyboard was set before some possible error returns. That pointer was left unchanged in case of failure, pointing to an uninitialized keyboard struct (that was also leaked). If a client sent a wl_seat::get_keyboard request, that would cause Weston to crash. Fix this by setting the seat->keyboard pointer only after the keymap initialization is done and there is no more possibilities for failure. Also plug the memory leaks on the error path. https://bugs.freedesktop.org/show_bug.cgi?id=74035 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.