Bug 1329978

Summary: [abrt] gnome-shell: meta_monitor_config_make_persistent(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Bastiaan Jacques <bastiaan>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: fmuellner, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0f0a699bca9cb778d5cc9f728406548e4ff819b9
Whiteboard: abrt_hash:88da27a2db1559fb8208c44216bf038db36494ae;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 20:07:57 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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Bastiaan Jacques 2016-04-25 08:32:02 UTC 
Description of problem:
Opened gnome display settings and attempted to disabled the builtin monitor. There was some flickering and then I was logged out and presented with gdm.

FRT, I was using a gnome shell theme, I think gs-metalX-gnome3.2.

There is an interesting entry in 'messages' about too many open files.



Version-Release number of selected component:
gnome-shell-3.18.4-1.fc23

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 3
cmdline:        /usr/bin/gnome-shell --wayland --display-server
crash_function: meta_monitor_config_make_persistent
executable:     /usr/bin/gnome-shell
global_pid:     2131
kernel:         4.4.7-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 meta_monitor_config_make_persistent
 #1 ffi_call_unix64 at ../src/x86/unix64.S:76
 #2 ffi_call at ../src/x86/ffi64.c:525
 #3 gjs_invoke_c_function(JSContext*, Function*, JSObject*, unsigned int, jsval*, jsval*, GArgument*) at gi/function.cpp:997
 #4 function_call(JSContext*, unsigned int, jsval*) at gi/function.cpp:1319
 #5 js::Invoke(JSContext*, JS::CallArgs, js::MaybeConstruct) at /usr/src/debug/mozjs-24.2.0/js/src/jscntxtinlines.h:321
 #7 Interpret(JSContext*, js::RunState&) at /usr/src/debug/mozjs-24.2.0/js/src/vm/Interpreter.cpp:2298
 #8 js::RunScript(JSContext*, js::RunState&) at /usr/src/debug/mozjs-24.2.0/js/src/vm/Interpreter.cpp:438
 #9 js::Invoke(JSContext*, JS::CallArgs, js::MaybeConstruct) at /usr/src/debug/mozjs-24.2.0/js/src/vm/Interpreter.cpp:500
 #10 js_fun_apply(JSContext*, unsigned int, JS::Value*) at /usr/src/debug/mozjs-24.2.0/js/src/jsfun.cpp:982
Comment 1 Bastiaan Jacques 2016-04-25 08:32:07 UTC 
Created attachment 1150283 [details]
File: backtrace
Comment 2 Bastiaan Jacques 2016-04-25 08:32:08 UTC 
Created attachment 1150284 [details]
File: cgroup
Comment 3 Bastiaan Jacques 2016-04-25 08:32:10 UTC 
Created attachment 1150285 [details]
File: core_backtrace
Comment 4 Bastiaan Jacques 2016-04-25 08:32:11 UTC 
Created attachment 1150286 [details]
File: dso_list
Comment 5 Bastiaan Jacques 2016-04-25 08:32:12 UTC 
Created attachment 1150287 [details]
File: environ
Comment 6 Bastiaan Jacques 2016-04-25 08:32:14 UTC 
Created attachment 1150288 [details]
File: exploitable
Comment 7 Bastiaan Jacques 2016-04-25 08:32:15 UTC 
Created attachment 1150289 [details]
File: limits
Comment 8 Bastiaan Jacques 2016-04-25 08:32:17 UTC 
Created attachment 1150290 [details]
File: maps
Comment 9 Bastiaan Jacques 2016-04-25 08:32:18 UTC 
Created attachment 1150291 [details]
File: mountinfo
Comment 10 Bastiaan Jacques 2016-04-25 08:32:20 UTC 
Created attachment 1150292 [details]
File: namespaces
Comment 11 Bastiaan Jacques 2016-04-25 08:32:21 UTC 
Created attachment 1150293 [details]
File: open_fds
Comment 12 Bastiaan Jacques 2016-04-25 08:32:22 UTC 
Created attachment 1150294 [details]
File: proc_pid_status
Comment 13 Bastiaan Jacques 2016-04-25 08:32:24 UTC 
Created attachment 1150295 [details]
File: var_log_messages
Comment 14 Fedora End Of Life 2016-11-25 07:27:56 UTC 
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 15 Fedora End Of Life 2016-12-20 20:07:57 UTC 
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.