Bug 1031798

Summary: [abrt] gnome-shell-3.10.2-1.fc20: strcmp: Process /usr/bin/gnome-shell-wayland was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fmuellner, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d259282e1b80cff0174549008dfda32d478c73e2
Whiteboard: abrt_hash:5489a7fdb200ff87049974c9adfe6ce93cb61208
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:59:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Mikhail 2013-11-18 19:37:50 UTC 
Description of problem:
Start gnome with wayland

Version-Release number of selected component:
gnome-shell-3.10.2-1.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        gnome-shell-wayland --wayland
crash_function: strcmp
executable:     /usr/bin/gnome-shell-wayland
kernel:         3.12.0-2.fc21.x86_64+debug
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 strcmp at ../sysdeps/x86_64/strcmp.S:210
 #1 find_device_by_udev_device at evdev/clutter-device-manager-evdev.c:957
 #2 evdev_remove_device at evdev/clutter-device-manager-evdev.c:975
 #3 on_uevent at evdev/clutter-device-manager-evdev.c:998
 #8 monitor_event at ../src/gudev/gudevclient.c:103
 #13 meta_run at core/main.c:564
Comment 1 Mikhail 2013-11-18 19:37:59 UTC 
Created attachment 825798 [details]
File: backtrace
Comment 2 Mikhail 2013-11-18 19:38:03 UTC 
Created attachment 825799 [details]
File: cgroup
Comment 3 Mikhail 2013-11-18 19:38:08 UTC 
Created attachment 825800 [details]
File: core_backtrace
Comment 4 Mikhail 2013-11-18 19:38:12 UTC 
Created attachment 825801 [details]
File: dso_list
Comment 5 Mikhail 2013-11-18 19:38:16 UTC 
Created attachment 825802 [details]
File: environ
Comment 6 Mikhail 2013-11-18 19:38:20 UTC 
Created attachment 825803 [details]
File: exploitable
Comment 7 Mikhail 2013-11-18 19:38:24 UTC 
Created attachment 825804 [details]
File: limits
Comment 8 Mikhail 2013-11-18 19:38:28 UTC 
Created attachment 825805 [details]
File: maps
Comment 9 Mikhail 2013-11-18 19:38:32 UTC 
Created attachment 825806 [details]
File: open_fds
Comment 10 Mikhail 2013-11-18 19:38:35 UTC 
Created attachment 825807 [details]
File: proc_pid_status
Comment 11 Fedora End Of Life 2015-05-29 09:47:52 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 12 Fedora End Of Life 2015-06-29 12:59:00 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.