Bug 83113 - SIGSEGV in widget_destroy: Touch events during widget destroy cause weston-terminal crash
Summary: SIGSEGV in widget_destroy: Touch events during widget destroy cause weston-te...
Status: RESOLVED MOVED
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: unspecified
Hardware: Other All
: medium critical
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-26 21:02 UTC by Anu Reddy
Modified: 2018-06-08 23:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
gdb-backtrace (7.08 KB, text/plain)
2014-08-26 21:02 UTC, Anu Reddy 		Details
View All

Description Anu Reddy 2014-08-26 21:02:35 UTC 
Created attachment 105303 [details]
gdb-backtrace

Steps to reproduce:
1. Launch weston
2. Run weston-terminal
3. Right-click on weston-terminal (menu/widget activated)
4. Touch the terminal's black surface with two fingers
6. Now, remove fingers from terminal's black surface
5. observe that terminal is destroyed with segmentation fault

Software stack:
wayland (HEAD) remotes/origin/HEAD-0-g6d0f298
drm (HEAD) heads/master-16-gd686160
mesa (HEAD) remotes/origin/10.2-0-gd82ca4e
libva (HEAD) libva-1.3.1-0-g053f70f
intel-driver (HEAD) 1.3.1-0-ga720bc8
cairo (HEAD) heads/1.12-0-g59e2a93
libinput (HEAD) heads/master-163-gbb10ec8
weston (HEAD) remotes/origin/master-0-g652c794
Comment 1 Yong Bakos 2016-04-21 23:17:18 UTC 
Sent the bug submitter a personal request to test again with recent builds of libinput, etc, and to update this bug.
Comment 2 GitLab Migration User 2018-06-08 23:52:20 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/42.

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.