Bug 1193051

Summary: [abrt] gnome-shell: wl_closure_marshal(): gnome-shell killed by SIGABRT
Product: [Fedora] Fedora Reporter: mchalupa
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: fmuellner, kem, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/59edc6d7d4585ec758619b946ff8142940cffb72
Whiteboard: abrt_hash:53d505728388ccd0b1cf9676918eaa003fe4a221
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 09:06:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description mchalupa 2015-02-16 13:29:47 UTC 
Description of problem:
I was switching tty

Version-Release number of selected component:
gnome-shell-3.14.3-1.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell --wayland --display-server
crash_function: wl_closure_marshal
executable:     /usr/bin/gnome-shell
kernel:         3.18.6-200.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 wl_closure_marshal at src/connection.c:568
 #3 wl_resource_post_event_array at src/wayland-server.c:130
 #4 wl_resource_post_event at src/wayland-server.c:159
 #5 wl_keyboard_send_keymap at /usr/include/wayland-server-protocol.h:1826
 #6 meta_wayland_keyboard_create_new_resource at wayland/meta-wayland-keyboard.c:625
 #7 ffi_call_unix64 at ../src/x86/unix64.S:76
 #8 ffi_call at ../src/x86/ffi64.c:525
 #9 wl_closure_invoke at src/connection.c:934
 #10 wl_client_connection_data at src/wayland-server.c:334
 #11 wl_event_loop_dispatch at src/event-loop.c:419
Comment 1 mchalupa 2015-02-16 13:29:50 UTC 
Created attachment 992173 [details]
File: backtrace
Comment 2 mchalupa 2015-02-16 13:29:51 UTC 
Created attachment 992174 [details]
File: cgroup
Comment 3 mchalupa 2015-02-16 13:29:53 UTC 
Created attachment 992175 [details]
File: core_backtrace
Comment 4 mchalupa 2015-02-16 13:29:55 UTC 
Created attachment 992176 [details]
File: dso_list
Comment 5 mchalupa 2015-02-16 13:29:56 UTC 
Created attachment 992177 [details]
File: environ
Comment 6 mchalupa 2015-02-16 13:29:57 UTC 
Created attachment 992178 [details]
File: limits
Comment 7 mchalupa 2015-02-16 13:29:59 UTC 
Created attachment 992179 [details]
File: maps
Comment 8 mchalupa 2015-02-16 13:30:00 UTC 
Created attachment 992180 [details]
File: open_fds
Comment 9 mchalupa 2015-02-16 13:30:01 UTC 
Created attachment 992181 [details]
File: proc_pid_status
Comment 10 mchalupa 2015-02-16 13:30:03 UTC 
Created attachment 992182 [details]
File: var_log_messages
Comment 11 mchalupa 2015-02-27 13:49:05 UTC 
This happens due to a race when switching VT. When a get_keyboard request is pending on a queue and we switch VT, the get_keyboard is processed after that. But switching VT releases all devices so get_keyboard is handled with invalid data. (wl_closure_marshal call abort due to bad filedescriptor).

I can't reproduce it on master gnome-shell, though looking into the code, the race is still there, but with little different behavior. get_keyboard handler now can not be called with released keyboard (mutter commit 2aa6dcd9d) , so gnome-shell won't crash. But if the request is pending as described, then client will expect that the keyboard resource was created (but it was not) and then libwayland will hit invalid id error. But as I said - I cannot reproduce it on master anymore.
Comment 12 mchalupa 2015-03-05 08:29:58 UTC 
There are some attempts to fix this race in wayland:
http://lists.freedesktop.org/archives/wayland-devel/2015-February/020276.html
Comment 13 Fedora End Of Life 2015-11-04 13:18:31 UTC 
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Fedora End Of Life 2015-12-02 09:06:54 UTC 
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.