Summary: | SIGSEGV in weston-keyboard_set_focus during change_workspace when output seat is specified | ||
---|---|---|---|
Product: | Wayland | Reporter: | Anu Reddy <anasuyax.r.nannuri> |
Component: | weston | Assignee: | Wayland bug list <wayland-bugs> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
seat_gdbbacktrace
unlock_gdb_backtrace |
Description
Anu Reddy
2014-05-06 17:50:13 UTC
Created attachment 98576 [details]
seat_gdbbacktrace
This is another way to reproduce SIGSEGV in weston_keyboard_set_focus. When output seat is specified in weston.ini, unlock screen causes weston to crash with segmentation fault in weston_keyboard_set_focus. Steps: ====== 1. Describe output seat in Weston.ini Example: Output name=HDMI2 seat=back0 2. Launch Weston: weston-launch -- –i5 3. Allow weston to lock 4. Unlock screen. Observe Weston crash with Segmentation fault. See attached unlock_gdb_backtrace. Created attachment 98700 [details]
unlock_gdb_backtrace
I sent a patch to the mailing list to fix this bug: http://lists.freedesktop.org/archives/wayland-devel/2014-May/014659.html commit 6e56ab41d99197ca2b562b5bc1315800065763ae Author: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com> Date: Wed May 7 11:57:28 2014 +0300 shell: Fix crash when restoring focus state during workspace change The check to avoid calling weston_keyboard_set_focus() for a seat that didn't have a keyboard in restore_focus_state() was cheking the wrong seat (the one from the previous loop). That caused a crash when switching workspaces if there was an extra seat that didn't have a keyboard. https://bugs.freedesktop.org/show_bug.cgi?id=78349 |
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.