Red Hat Bugzilla – Bug 1302870
[abrt] plasma-workspace: QByteArray::reallocData(): plasmashell killed by SIGSEGV
Last modified: 2017-08-08 08:42:58 EDT
Description of problem:
I was attempting to find out what was causing the plasmashell app to crash, so I create a testing user with only empty, standard, directories in it.
Then I did a "dnf erase plasma* kde*", reinstall fresh KDE/Plasma programs.
When I booted "plasma" from the login screen, the plasma shell aborted again.
I suspect that one of the plasma system directories is misconfigured, but haven't a clue why.
Version-Release number of selected component:
cmdline: /usr/bin/plasmashell --shut-up
runlevel: N 5
Thread no. 1 (10 frames)
#3 QByteArray::reallocData at tools/qbytearray.cpp:1619
#4 QByteArray::resize at tools/qbytearray.cpp:1575
#5 QUtf8::convertFromUnicode at codecs/qutfcodec.cpp:231
#6 QUtf8Codec::convertFromUnicode at codecs/qutfcodec.cpp:659
#7 QTextCodec::fromUnicode at ../../src/corelib/codecs/qtextcodec.h:105
#8 QString::toLocal8Bit_helper at tools/qstring.cpp:4579
#9 QString::toLocal8Bit() const & at ../../src/corelib/tools/qstring.h:517
#10 QFile::encodeName at ../../src/corelib/io/qfile.h:82
#11 QFileSystemEntry::resolveNativeFilePath at io/qfilesystementry.cpp:162
#12 QFileSystemEntry::nativeFilePath at io/qfilesystementry.cpp:130
Created attachment 1119281 [details]
Created attachment 1119282 [details]
Created attachment 1119283 [details]
Created attachment 1119284 [details]
Created attachment 1119285 [details]
Created attachment 1119286 [details]
Created attachment 1119287 [details]
Created attachment 1119288 [details]
Created attachment 1119289 [details]
Created attachment 1119290 [details]
Created attachment 1119291 [details]
Created attachment 1119292 [details]
Created attachment 1119293 [details]
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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'
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 24 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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
Thank you for reporting this bug and we are sorry it could not be fixed.