Bug 1392242

Summary: [abrt] gnome-shell: _clutter_input_device_evdev_get_seat(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Peter Robinson <pbrobinson>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: fedora, fmuellner, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: armv7l   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/29e1a22e25c9635a54c25b46adc2c4ed58e41b6c
Whiteboard: abrt_hash:1f37680d6c9d01189a4167d289024083230c0c7d;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:39:47 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: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Peter Robinson 2016-11-06 17:39:53 UTC
Description of problem:


Version-Release number of selected component:
gnome-shell-3.22.1-2.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: _clutter_input_device_evdev_get_seat
executable:     /usr/bin/gnome-shell
global_pid:     880
kernel:         4.8.6-300.fc25.armv7hl
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            42

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 _clutter_input_device_evdev_get_seat at evdev/clutter-input-device-evdev.c:240
 #1 clutter_event_dispatch at evdev/clutter-device-manager-evdev.c:822
 #6 meta_run at core/main.c:572

Comment 1 Peter Robinson 2016-11-06 17:39:59 UTC
Created attachment 1217771 [details]
File: backtrace

Comment 2 Peter Robinson 2016-11-06 17:40:01 UTC
Created attachment 1217772 [details]
File: cgroup

Comment 3 Peter Robinson 2016-11-06 17:40:02 UTC
Created attachment 1217773 [details]
File: core_backtrace

Comment 4 Peter Robinson 2016-11-06 17:40:04 UTC
Created attachment 1217774 [details]
File: dso_list

Comment 5 Peter Robinson 2016-11-06 17:40:05 UTC
Created attachment 1217775 [details]
File: environ

Comment 6 Peter Robinson 2016-11-06 17:40:06 UTC
Created attachment 1217776 [details]
File: exploitable

Comment 7 Peter Robinson 2016-11-06 17:40:08 UTC
Created attachment 1217777 [details]
File: limits

Comment 8 Peter Robinson 2016-11-06 17:40:10 UTC
Created attachment 1217778 [details]
File: maps

Comment 9 Peter Robinson 2016-11-06 17:40:11 UTC
Created attachment 1217779 [details]
File: mountinfo

Comment 10 Peter Robinson 2016-11-06 17:40:13 UTC
Created attachment 1217780 [details]
File: namespaces

Comment 11 Peter Robinson 2016-11-06 17:40:14 UTC
Created attachment 1217781 [details]
File: open_fds

Comment 12 Peter Robinson 2016-11-06 17:40:15 UTC
Created attachment 1217782 [details]
File: proc_pid_status

Comment 13 Peter Robinson 2016-11-06 17:40:17 UTC
Created attachment 1217783 [details]
File: var_log_messages

Comment 14 Christian Stadelmann 2017-04-12 11:56:01 UTC
*** Bug 1441640 has been marked as a duplicate of this bug. ***

Comment 15 Christian Stadelmann 2017-04-12 11:57:50 UTC
I think I can reproduce this bug by following these steps:
1. on gdm login screen, log in to your gnome (wayland) session
2. as soon as possible, switch to another tty

My theory: This will result in the gnome-shell tty losing access to its input devices, which causes the crash.

Comment 16 Fedora End Of Life 2017-11-16 14:33:15 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 17 Christian Stadelmann 2017-11-23 12:57:40 UTC
(In reply to Christian Stadelmann from comment #15)
> I think I can reproduce this bug by following these steps:
> 1. on gdm login screen, log in to your gnome (wayland) session
> 2. as soon as possible, switch to another tty
> 
> My theory: This will result in the gnome-shell tty losing access to its
> input devices, which causes the crash.

Reproducing these steps now leads to bug #1516859 on Fedora 27.

Comment 18 Fedora End Of Life 2017-12-12 10:39:47 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.