Bug 1104595

Summary: [abrt] kde-workspace: Py_FatalError(): plasma-desktop killed by SIGABRT
Product: [Fedora] Fedora Reporter: kr1st0 <mail2kristophorus>
Component: kde-workspaceAssignee: Than Ngo <than>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dvratil, jgrulich, jreznik, kevin, ltinkl, mail2kristophorus, mbriza, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/85529eae2a4c47ddd5e9f8369bb1590f377fd94b
Whiteboard: abrt_hash:d62080d126d18006ee892742be9a5870a9a840c2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:56:42 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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description kr1st0 2014-06-04 09:37:11 UTC 
Version-Release number of selected component:
kde-workspace-4.11.9-4.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/plasma-desktop --nocrashhandler
crash_function: Py_FatalError
executable:     /usr/bin/plasma-desktop
kernel:         3.13.10-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 Py_FatalError at /lib64/libpython2.7.so.1.0
 #3 PyGILState_Release at /lib64/libpython2.7.so.1.0
 #4 sip_api_parse_result_ex at /usr/lib64/python2.7/site-packages/sip.so
 #5 sipVH_QtCore_18(PyGILState_STATE, void (*)(_sipSimpleWrapper*, PyGILState_STATE), _sipSimpleWrapper*, _object*, QObject*, QEvent*) at /usr/lib64/python2.7/site-packages/PyQt4/QtCore.so
 #6 sipPlasma_AppletScript::eventFilter(QObject*, QEvent*) at /usr/lib64/python2.7/site-packages/PyKDE4/plasma.so
 #7 QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) at /lib64/libQtCore.so.4
 #8 QApplicationPrivate::notify_helper(QObject*, QEvent*) at /lib64/libQtGui.so.4
 #9 QApplication::notify(QObject*, QEvent*) at /lib64/libQtGui.so.4
 #10 KApplication::notify(QObject*, QEvent*) at /lib64/libkdeui.so.5
 #11 QCoreApplication::notifyInternal(QObject*, QEvent*) at /lib64/libQtCore.so.4
Comment 1 kr1st0 2014-06-04 09:37:15 UTC 
Created attachment 902107 [details]
File: backtrace
Comment 2 kr1st0 2014-06-04 09:37:17 UTC 
Created attachment 902108 [details]
File: cgroup
Comment 3 kr1st0 2014-06-04 09:37:19 UTC 
Created attachment 902109 [details]
File: core_backtrace
Comment 4 kr1st0 2014-06-04 09:37:20 UTC 
Created attachment 902110 [details]
File: dso_list
Comment 5 kr1st0 2014-06-04 09:37:22 UTC 
Created attachment 902111 [details]
File: environ
Comment 6 kr1st0 2014-06-04 09:37:23 UTC 
Created attachment 902112 [details]
File: limits
Comment 7 kr1st0 2014-06-04 09:37:26 UTC 
Created attachment 902113 [details]
File: maps
Comment 8 kr1st0 2014-06-04 09:37:28 UTC 
Created attachment 902114 [details]
File: open_fds
Comment 9 kr1st0 2014-06-04 09:37:29 UTC 
Created attachment 902115 [details]
File: proc_pid_status
Comment 10 kr1st0 2014-06-04 09:37:30 UTC 
Created attachment 902116 [details]
File: var_log_messages
Comment 11 Kevin Kofler 2014-06-04 23:02:53 UTC 
This is crashing inside Python code, what Python widgets/applets/plasmoids do you have installed?
Comment 12 kr1st0 2014-06-05 03:49:34 UTC 
I install simple alarm clock and got that error when tried to put the alarm in systray.
Comment 13 kr1st0 2014-06-05 03:50:58 UTC 
(In reply to kr1st0 from comment #12)
> I install simple alarm clock and got that error when tried to put the alarm
> in systray.

I do remove the simple alarm clock widget manually and my KDE plasma working back.
Comment 14 Fedora End Of Life 2015-05-29 12:01:21 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 2015-06-29 20:56:42 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.