Bug 1303541

Summary: [abrt] plasma-systemsettings: QXcbWindow::handleClientMessageEvent(xcb_client_message_event_t const*)(): systemsettings5 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Robin Green <greenrd>
Component: plasma-systemsettingsAssignee: Rex Dieter <rdieter>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: andr.fenaroli, jgrulich, ltinkl, me, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/40d02e1e6537819f7dc6b0a6dfbdbc8c73319273
Whiteboard: abrt_hash:5d9d26a3265a6fed8e0ff24aec5d96c70c98de5a;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 18:21:44 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:
Bug Depends On: 1313811    
Bug Blocks:    
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 Robin Green 2016-02-01 09:12:47 UTC
Description of problem:
At the same time, I enabled my external display, disabled my laptop display, and changed the scale factor from 1.5 to 2.

Version-Release number of selected component:
plasma-systemsettings-5.5.4-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/systemsettings5
crash_function: QXcbWindow::handleClientMessageEvent(xcb_client_message_event_t const*)
executable:     /usr/bin/systemsettings5
global_pid:     3260
kernel:         4.3.3-303.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 Robin Green 2016-02-01 09:12:54 UTC
Created attachment 1120026 [details]
File: backtrace

Comment 2 Robin Green 2016-02-01 09:12:56 UTC
Created attachment 1120027 [details]
File: cgroup

Comment 3 Robin Green 2016-02-01 09:12:57 UTC
Created attachment 1120028 [details]
File: core_backtrace

Comment 4 Robin Green 2016-02-01 09:12:59 UTC
Created attachment 1120029 [details]
File: dso_list

Comment 5 Robin Green 2016-02-01 09:13:00 UTC
Created attachment 1120030 [details]
File: environ

Comment 6 Robin Green 2016-02-01 09:13:02 UTC
Created attachment 1120031 [details]
File: exploitable

Comment 7 Robin Green 2016-02-01 09:13:03 UTC
Created attachment 1120032 [details]
File: limits

Comment 8 Robin Green 2016-02-01 09:13:05 UTC
Created attachment 1120033 [details]
File: maps

Comment 9 Robin Green 2016-02-01 09:13:07 UTC
Created attachment 1120034 [details]
File: mountinfo

Comment 10 Robin Green 2016-02-01 09:13:08 UTC
Created attachment 1120035 [details]
File: namespaces

Comment 11 Robin Green 2016-02-01 09:13:10 UTC
Created attachment 1120036 [details]
File: open_fds

Comment 12 Robin Green 2016-02-01 09:13:11 UTC
Created attachment 1120037 [details]
File: proc_pid_status

Comment 13 Robin Green 2016-02-01 09:13:13 UTC
Created attachment 1120038 [details]
File: var_log_messages

Comment 14 Robin Green 2016-02-15 16:49:26 UTC
Similar problem has been detected:

The previous time I ran systemsettings, I had enabled my laptop display (which I had previously disabled) and disabled my external display, so that I could safely unplug it.  But this reset the resolution of the laptop display to something too small, so I re-ran systemsettings to try to fix that. But I could not because I could not select the laptop display because the representation of it in systemsettings was offscreen and there was no horizontal scrollbar to access it. After I quit systemsettings again, the crash happened.

reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/bin/systemsettings5
crash_function: QXcbWindow::handleClientMessageEvent(xcb_client_message_event_t const*)
executable:     /usr/bin/systemsettings5
global_pid:     18993
kernel:         4.3.5-300.fc23.x86_64
package:        plasma-systemsettings-5.5.4-1.fc23
reason:         systemsettings5 killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Fedora End Of Life 2016-11-24 15:19:43 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 16 Fedora End Of Life 2016-12-20 18:21:44 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.