Bug 1455293

Summary: [abrt] gnome-shell: real_assign_crtcs(): gnome-shell killed by signal 11
Product: [Fedora] Fedora Reporter: Satish Balay <balay>
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: a.ahanj, alexus_m, bugzilla, cben, fmuellner, fweimer, hp, jbirch, otaylor, redhat
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b13be3f2524d5248829d7426bb9985bebc3447c1
Whiteboard: abrt_hash:b89a99ae8f67156dd51c08ade0512d94c8473e4a;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:43:49 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 Satish Balay 2017-05-24 16:48:27 UTC
Version-Release number of selected component:
gnome-shell-3.24.2-1.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: real_assign_crtcs
executable:     /usr/bin/gnome-shell
journald_cursor: s=dda73f32a44949a38038fb669a994ec6;i=15c112;b=d7a439b6865641dfb81b257fe33b4f26;m=d21f5eda2;t=55047c74647b5;x=efdb22f5f3af36cc
kernel:         4.11.2-300.sb.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 real_assign_crtcs at backends/meta-monitor-config.c:1929
 #1 meta_monitor_config_assign_crtcs at backends/meta-monitor-config.c:1992
 #2 apply_configuration at backends/meta-monitor-config.c:873
 #3 turn_off_laptop_display at backends/meta-monitor-config.c:1577
 #4 power_client_changed_cb at backends/meta-monitor-config.c:1596
 #5 _g_closure_invoke_va at gclosure.c:867
 #13 g_object_notify_by_spec_internal at gobject.c:1157
 #22 up_exported_daemon_proxy_g_properties_changed at up-daemon-generated.c:1348
 #23 ffi_call_unix64 at ../src/x86/unix64.S:76
 #24 ffi_call at ../src/x86/ffi64.c:525

Potential duplicate: bug 1392423

Comment 1 Satish Balay 2017-05-24 16:48:32 UTC
Created attachment 1282026 [details]
File: backtrace

Comment 2 Satish Balay 2017-05-24 16:48:33 UTC
Created attachment 1282027 [details]
File: cgroup

Comment 3 Satish Balay 2017-05-24 16:48:35 UTC
Created attachment 1282028 [details]
File: core_backtrace

Comment 4 Satish Balay 2017-05-24 16:48:36 UTC
Created attachment 1282029 [details]
File: cpuinfo

Comment 5 Satish Balay 2017-05-24 16:48:37 UTC
Created attachment 1282030 [details]
File: dso_list

Comment 6 Satish Balay 2017-05-24 16:48:38 UTC
Created attachment 1282031 [details]
File: environ

Comment 7 Satish Balay 2017-05-24 16:48:40 UTC
Created attachment 1282032 [details]
File: exploitable

Comment 8 Satish Balay 2017-05-24 16:48:41 UTC
Created attachment 1282033 [details]
File: limits

Comment 9 Satish Balay 2017-05-24 16:48:42 UTC
Created attachment 1282034 [details]
File: maps

Comment 10 Satish Balay 2017-05-24 16:48:43 UTC
Created attachment 1282035 [details]
File: open_fds

Comment 11 Satish Balay 2017-05-24 16:48:44 UTC
Created attachment 1282036 [details]
File: proc_pid_status

Comment 12 Satish Balay 2017-05-24 16:48:45 UTC
Created attachment 1282037 [details]
File: var_log_messages

Comment 13 bugzilla 2017-08-08 03:46:03 UTC
*** Bug 1479129 has been marked as a duplicate of this bug. ***

Comment 14 Jason Birch 2017-08-14 21:34:29 UTC
*** Bug 1481438 has been marked as a duplicate of this bug. ***

Comment 15 Joseph Moragrega 2017-09-03 20:45:42 UTC
*** Bug 1487962 has been marked as a duplicate of this bug. ***

Comment 16 a.ahanj 2017-09-07 18:51:41 UTC
*** Bug 1489570 has been marked as a duplicate of this bug. ***

Comment 17 Joseph Moragrega 2017-10-25 22:59:57 UTC
*** Bug 1506406 has been marked as a duplicate of this bug. ***

Comment 18 Florian Weimer 2018-01-04 09:44:01 UTC
Still present with:

gnome-shell-3.24.3-2.fc26.x86_64
mutter-3.24.4-3.fc26.x86_64

Comment 19 Fedora End Of Life 2018-05-03 08:21:46 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:43:49 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.