Bug 1485786

Summary: [abrt] gnome-shell: init_output(): gnome-shell killed by signal 11
Product: [Fedora] Fedora Reporter: Robert Hancock <hancockrwd>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: alon1.dotan, fmuellner, geoff.mcqueen, kaustubhghadge, kyogesh91, mrjojo, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9fe114fa550a67ce0560bf23819ea99142fc12ae
Whiteboard: abrt_hash:a26d4124544f4c737803251925aac4e809d6023c;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:31:12 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: cpuinfo
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
File: var_log_messages none

Description Robert Hancock 2017-08-28 06:00:28 UTC
Description of problem:
Likely caused by HDMI hotplug event

Version-Release number of selected component:
gnome-shell-3.24.3-1.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: init_output
executable:     /usr/bin/gnome-shell
journald_cursor: s=398e3ae8c47c4dda9b07285235d6daa0;i=139fb0;b=3315fdd8f01f4ad89b9b1fb345f5ec02;m=e33178d91;t=557c9e78d8b7c;x=4524d147c12447f0
kernel:         4.12.8-300.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 init_output at backends/native/meta-monitor-manager-kms.c:829
 #1 init_outputs at backends/native/meta-monitor-manager-kms.c:1175
 #2 meta_monitor_manager_kms_read_current at backends/native/meta-monitor-manager-kms.c:1213
 #3 meta_monitor_manager_read_current_state at backends/meta-monitor-manager.c:1719
 #4 handle_hotplug_event at backends/native/meta-monitor-manager-kms.c:1608
 #5 on_uevent at backends/native/meta-monitor-manager-kms.c:1624
 #10 monitor_event at gudev/gudevclient.c:104
 #15 meta_run at core/main.c:648

Potential duplicate: bug 1421882

Comment 1 Robert Hancock 2017-08-28 06:00:35 UTC
Created attachment 1318911 [details]
File: backtrace

Comment 2 Robert Hancock 2017-08-28 06:00:36 UTC
Created attachment 1318912 [details]
File: cgroup

Comment 3 Robert Hancock 2017-08-28 06:00:37 UTC
Created attachment 1318913 [details]
File: core_backtrace

Comment 4 Robert Hancock 2017-08-28 06:00:38 UTC
Created attachment 1318914 [details]
File: cpuinfo

Comment 5 Robert Hancock 2017-08-28 06:00:40 UTC
Created attachment 1318915 [details]
File: dso_list

Comment 6 Robert Hancock 2017-08-28 06:00:41 UTC
Created attachment 1318916 [details]
File: environ

Comment 7 Robert Hancock 2017-08-28 06:00:42 UTC
Created attachment 1318917 [details]
File: exploitable

Comment 8 Robert Hancock 2017-08-28 06:00:43 UTC
Created attachment 1318918 [details]
File: limits

Comment 9 Robert Hancock 2017-08-28 06:00:45 UTC
Created attachment 1318919 [details]
File: maps

Comment 10 Robert Hancock 2017-08-28 06:00:46 UTC
Created attachment 1318920 [details]
File: open_fds

Comment 11 Robert Hancock 2017-08-28 06:00:47 UTC
Created attachment 1318921 [details]
File: proc_pid_status

Comment 12 Robert Hancock 2017-08-28 06:00:48 UTC
Created attachment 1318922 [details]
File: var_log_messages

Comment 13 geoff.mcqueen 2017-10-06 21:27:45 UTC
Similar problem has been detected:

I think I'd just finished with a Zoom call and suspended the machine, and when I came back from suspend at my desk it was crashed.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: init_output
executable:     /usr/bin/gnome-shell
journald_cursor: s=c07eebba50a34e9eafd8373ae8e34136;i=12f63;b=c0b9a79921e34a5084d93f483624c93b;m=43ee8e056;t=55ae5c3691f34;x=cc9d3194790a91f
kernel:         4.13.4-200.fc26.x86_64
package:        gnome-shell-3.24.3-2.fc26
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Pawel J 2017-10-19 23:42:09 UTC
*** Bug 1504313 has been marked as a duplicate of this bug. ***

Comment 15 Robert Hancock 2017-11-02 02:27:37 UTC
Similar problem has been detected:

Triggered by HDMI device disconnect

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: init_output
executable:     /usr/bin/gnome-shell
journald_cursor: s=398e3ae8c47c4dda9b07285235d6daa0;i=160da1;b=5d31089d802d436399f870eac854a01a;m=51d4bace8;t=55cf68afbaac1;x=8d91ed1d8250957d
kernel:         4.13.10-200.fc26.x86_64
package:        gnome-shell-3.24.3-2.fc26
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 16 Robert Hancock 2017-11-02 02:35:45 UTC
Reported upstream with GNOME Bugzila as 789797.

Comment 17 kaustubh ghadge 2017-12-05 19:48:17 UTC
*** Bug 1521101 has been marked as a duplicate of this bug. ***

Comment 18 kyogesh91 2018-02-10 11:35:16 UTC
*** Bug 1544118 has been marked as a duplicate of this bug. ***

Comment 19 Fedora End Of Life 2018-05-03 08:06:33 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 20 Fedora End Of Life 2018-05-29 11:31:12 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.