Bug 106313

Summary:	weston freezes when mouse pointer moved to the left edge of the desktop on Intel Cherrytrail PC.
Product:	Wayland	Reporter:	anthony <ant8me>
Component:	weston	Assignee:	Wayland bug list <wayland-bugs>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium	CC:	daniel
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	weston stderr output

Description anthony 2018-04-29 17:51:24 UTC

Created attachment 139220 [details]
weston stderr output

When running weston-launch from a terminal, I get a freeze when the mouse pointer is moved to the left edge of the desktop. The desktop freezes, I can still use ctrl-alt-backspace to exit weston. The mouse is frozen and all screen drawing is frozen. This does not occur on the top right or bottom edges.

This seems to have been introduced since updating to weston 4.0. 

I am running a standard arch Linux x86_64 (fully up to date) on an Intel Cherrytrail PC box. There is no weston.ini file so all configuration settings are defaults. Gnome, KDE, X, etc are not installed, just Wayland and Mesa.

I can reproduce every time as follows:

on a console terminal:
weston-launch --verbose 2>weston.log <enter>

Move mouse over to left hand edge. Everything frozen. Press ctrl-alt-backspace to exit or kill process.

Any program like weston-simple-damage also freezes.

There is a line in the log that is output when weston freezes:
>>> atomic: couldn't commit new state: Invalid argument

I have attached a log file from the stderr pipe.

Some relevant packages installed:
wayland 1.14.0-1
wayland-protocols 1.13-1
weston 4.0.0-1
mesa 18.0.1-1
libdrm 2.4.91-3
libinput 1.10.5-1
linux 4.16.5-1

Comment 1 anthony 2018-05-09 18:31:40 UTC

As a temporary workaround to the problem set the environment variable WESTON_DISABLE_ATOMIC to "Y" before launching weston. This will disable atomic modesetting in the compositor. See compositor-drm.c.

I think this bug maybe specific to Intel Z8350 Cherrytrail PCs.

Comment 2 Daniel Stone 2018-06-04 06:52:44 UTC

I believe this should be fixed with coming patches, which more carefully take care of clipping the cursor area to the CRTC bounds.

Comment 3 GitLab Migration User 2018-06-08 23:56:15 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/107.

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.