Bug 1274094

Summary: [abrt] gnome-shell: output_key_equal(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: abkahrs
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: fmuellner, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f663cbf1139a9b73e760216e00a07cda857bf45c
Whiteboard: abrt_hash:6850c51d01353b086198b7a409e9d0cc987ab4aa;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:18:13 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: 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 abkahrs 2015-10-21 22:12:55 UTC 
Version-Release number of selected component:
gnome-shell-3.16.3-1.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: output_key_equal
executable:     /usr/bin/gnome-shell
global_pid:     1919
kernel:         4.1.10-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 output_key_equal at backends/meta-monitor-config.c:166
 #1 config_equal at backends/meta-monitor-config.c:206
 #2 g_hash_table_lookup_node at ghash.c:396
 #3 g_hash_table_lookup at ghash.c:1147
 #4 meta_monitor_config_get_stored at backends/meta-monitor-config.c:846
 #5 meta_monitor_config_apply_stored at backends/meta-monitor-config.c:1045
 #6 meta_monitor_manager_on_hotplug at backends/meta-monitor-manager.c:1280
 #7 meta_monitor_manager_xrandr_handle_xevent at backends/x11/meta-monitor-manager-xrandr.c:1233
 #8 handle_host_xevent at backends/x11/meta-backend-x11.c:276
 #9 x_event_source_dispatch at backends/x11/meta-backend-x11.c:336
Comment 1 abkahrs 2015-10-21 22:13:00 UTC 
Created attachment 1085336 [details]
File: backtrace
Comment 2 abkahrs 2015-10-21 22:13:01 UTC 
Created attachment 1085337 [details]
File: cgroup
Comment 3 abkahrs 2015-10-21 22:13:02 UTC 
Created attachment 1085338 [details]
File: core_backtrace
Comment 4 abkahrs 2015-10-21 22:13:03 UTC 
Created attachment 1085339 [details]
File: dso_list
Comment 5 abkahrs 2015-10-21 22:13:04 UTC 
Created attachment 1085340 [details]
File: environ
Comment 6 abkahrs 2015-10-21 22:13:05 UTC 
Created attachment 1085341 [details]
File: limits
Comment 7 abkahrs 2015-10-21 22:13:07 UTC 
Created attachment 1085342 [details]
File: maps
Comment 8 abkahrs 2015-10-21 22:13:08 UTC 
Created attachment 1085343 [details]
File: mountinfo
Comment 9 abkahrs 2015-10-21 22:13:09 UTC 
Created attachment 1085344 [details]
File: namespaces
Comment 10 abkahrs 2015-10-21 22:13:10 UTC 
Created attachment 1085345 [details]
File: open_fds
Comment 11 abkahrs 2015-10-21 22:13:11 UTC 
Created attachment 1085346 [details]
File: proc_pid_status
Comment 12 abkahrs 2015-10-21 22:13:12 UTC 
Created attachment 1085347 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:18:13 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.