Bug 1276522

Summary: [abrt] plasma-workspace: QXcbWindow::handleClientMessageEvent(): systemmonitor killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Bugzy <bugzylittle>
Component: plasma-workspaceAssignee: KDE SIG <kde-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jgrulich, kde-sig, ltinkl, me, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2f996e893fb8e5f1bec9653695b238c0cb4a6a8b
Whiteboard: abrt_hash:a2c80fcdc53a1a05582b545eb213cef887d48ed6;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:22:15 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: 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 Bugzy 2015-10-30 01:51:37 UTC 
Description of problem:
resuming from suspend on a dual motior machine

Version-Release number of selected component:
plasma-workspace-5.4.2-4.fc22

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /bin/systemmonitor
crash_function: QXcbWindow::handleClientMessageEvent
executable:     /usr/bin/systemmonitor
global_pid:     32725
kernel:         4.2.3-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 QXcbWindow::handleClientMessageEvent at qxcbwindow.cpp:1940
 #1 QXcbConnection::handleXcbEvent at qxcbconnection.cpp:1043
 #2 QXcbConnection::processXcbEvents at qxcbconnection.cpp:1487
 #3 QObject::event at kernel/qobject.cpp:1246
 #4 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3717
 #5 QApplication::notify at kernel/qapplication.cpp:3500
 #6 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:965
 #7 sendEvent at kernel/qcoreapplication.h:224
 #8 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1593
 #9 QCoreApplication::sendPostedEvents at kernel/qcoreapplication.cpp:1451
Comment 1 Bugzy 2015-10-30 01:51:42 UTC 
Created attachment 1087786 [details]
File: backtrace
Comment 2 Bugzy 2015-10-30 01:51:43 UTC 
Created attachment 1087787 [details]
File: cgroup
Comment 3 Bugzy 2015-10-30 01:51:44 UTC 
Created attachment 1087788 [details]
File: core_backtrace
Comment 4 Bugzy 2015-10-30 01:51:45 UTC 
Created attachment 1087789 [details]
File: dso_list
Comment 5 Bugzy 2015-10-30 01:51:46 UTC 
Created attachment 1087790 [details]
File: environ
Comment 6 Bugzy 2015-10-30 01:51:47 UTC 
Created attachment 1087791 [details]
File: limits
Comment 7 Bugzy 2015-10-30 01:51:49 UTC 
Created attachment 1087792 [details]
File: maps
Comment 8 Bugzy 2015-10-30 01:51:50 UTC 
Created attachment 1087793 [details]
File: mountinfo
Comment 9 Bugzy 2015-10-30 01:51:51 UTC 
Created attachment 1087794 [details]
File: namespaces
Comment 10 Bugzy 2015-10-30 01:51:52 UTC 
Created attachment 1087795 [details]
File: open_fds
Comment 11 Bugzy 2015-10-30 01:51:53 UTC 
Created attachment 1087796 [details]
File: proc_pid_status
Comment 12 Bugzy 2015-10-30 01:51:54 UTC 
Created attachment 1087797 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:22:15 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.