Summary: | switching from weston to a VT and back, mouse crashes X applications | ||
---|---|---|---|
Product: | Wayland | Reporter: | James <james> |
Component: | weston | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | annotated weston log showing Xwayland crash |
Description
James
2015-02-01 14:05:16 UTC
Created attachment 113025 [details]
annotated weston log showing Xwayland crash
I have attached output from "weston > westonlog 2>&1", with the following stages annotated: 1 start weston and weston-terminal 2 start dillo 3 switch to Xorg 4 switch back to weston 5 mouse-over dillo and crash Xwayland, weston-terminal continues normally 6 access the panel and crash weston An alternative sequence, switching to Xorg and back _before_ starting dillo, and _then_ starting dillo after the switch and back, "ps" will say that dillo and Xwayland are running, but no dillo window will be seen. In contrast, at the same time, weston-terminal can still be started and presents a normal window. Often, but not always, the first attempt at "Ctrl-Alt-F1" to switch to xorg will fail. This "probabilistic" control response means something is wrong. Often, but not always, accessing the panel after Xwayland has crashed, will also crash weston. When Xwayland has _not_ crashed, and then terminating weston, Xwayland does not seem to terminate "gracefully", showing: (EE) Fatal server error: (EE) failed to dispatch Wayland events: Broken pipe (EE) Can't open display: :1 but I suppose that that is a separate issue. Please see the attached log. I have tested this on weston 1.7.0, actually github.com/giucam/weston#branch=libweston, wayland 1.7.0, and libinput 0.10.0, and am no longer seeing the problem. It seems to be fixed. |
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.