Bug 1478927

Summary: [abrt] gnome-shell: meta_monitor_manager_get_logical_monitor_from_number(): gnome-shell killed by signal 6
Product: [Fedora] Fedora Reporter: Nikita Goncharuk <nmg921>
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: fmuellner, otaylor, steven.sheehy
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/bffd3736df2132258dac2fe7a9656814a1d2ba8b
Whiteboard: abrt_hash:3b2d1ff2e58ef51682ab7857a52db5d6dc302631;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:48:55 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Nikita Goncharuk 2017-08-07 13:59:27 UTC
Description of problem:
I unpluged the second monitor (HDMI) in Wayland Session.

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: meta_monitor_manager_get_logical_monitor_from_number
executable:     /usr/bin/gnome-shell
journald_cursor: s=f86958fcb99b472092caaaa90b0d6a75;i=6e8a8;b=2a8ab6a22d8e46719e0a713950fb2134;m=8183b3bcc;t=5562a3abcf3e4;x=976ef493321999ca
kernel:         4.11.11-300.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 meta_monitor_manager_get_logical_monitor_from_number at backends/meta-monitor-manager.c:1435
 #5 meta_workspace_get_work_area_for_monitor at core/workspace.c:1104
 #6 ffi_call_unix64 at ../src/x86/unix64.S:76
 #7 ffi_call at ../src/x86/ffi64.c:525
 #8 gjs_invoke_c_function(JSContext*, Function*, JS::HandleObject, JS::HandleValueArray const&, mozilla::Maybe<JS::MutableHandle<JS::Value> >&, GIArgument*) at gi/function.cpp:1021
 #9 function_call(JSContext*, unsigned int, JS::Value*) at gi/function.cpp:1340
 #10 js::CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), JS::CallArgs const&) at /usr/src/debug/mozilla-esr38/js/src/jscntxtinlines.h:226
 #11 js::Invoke(JSContext*, JS::CallArgs, js::MaybeConstruct) at /usr/src/debug/mozilla-esr38/js/src/vm/Interpreter.cpp:498
 #12 js::Invoke(JSContext*, JS::Value const&, JS::Value const&, unsigned int, JS::Value const*, JS::MutableHandle<JS::Value>) at /usr/src/debug/mozilla-esr38/js/src/vm/Interpreter.cpp:554
 #13 js::jit::InvokeFunction(JSContext*, JS::Handle<JSObject*>, unsigned int, JS::Value*, JS::Value*) at /usr/src/debug/mozilla-esr38/js/src/jit/VMFunctions.cpp:75

Comment 1 Nikita Goncharuk 2017-08-07 13:59:33 UTC
Created attachment 1310077 [details]
File: backtrace

Comment 2 Nikita Goncharuk 2017-08-07 13:59:35 UTC
Created attachment 1310078 [details]
File: cgroup

Comment 3 Nikita Goncharuk 2017-08-07 13:59:37 UTC
Created attachment 1310079 [details]
File: core_backtrace

Comment 4 Nikita Goncharuk 2017-08-07 13:59:39 UTC
Created attachment 1310080 [details]
File: cpuinfo

Comment 5 Nikita Goncharuk 2017-08-07 13:59:41 UTC
Created attachment 1310082 [details]
File: dso_list

Comment 6 Nikita Goncharuk 2017-08-07 13:59:42 UTC
Created attachment 1310083 [details]
File: environ

Comment 7 Nikita Goncharuk 2017-08-07 13:59:44 UTC
Created attachment 1310085 [details]
File: limits

Comment 8 Nikita Goncharuk 2017-08-07 13:59:47 UTC
Created attachment 1310088 [details]
File: maps

Comment 9 Nikita Goncharuk 2017-08-07 13:59:49 UTC
Created attachment 1310090 [details]
File: open_fds

Comment 10 Nikita Goncharuk 2017-08-07 13:59:50 UTC
Created attachment 1310092 [details]
File: proc_pid_status

Comment 11 Nikita Goncharuk 2017-08-07 13:59:52 UTC
Created attachment 1310094 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2018-05-03 08:23:21 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 13 Fedora End Of Life 2018-05-29 11:48:55 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.