Bug 1465352

Summary: [abrt] plasma-workspace: KCrash::defaultCrashHandler(): plasmashell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: a.thiaville
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: 25CC: jgrulich, kde-sig, me, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d294e3047633aed62e29d91424d59204a8f01020
Whiteboard: abrt_hash:b29e3b75677c666db528f74012b8f9e3d2668d58;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:31:40 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 a.thiaville 2017-06-27 09:37:40 UTC
Description of problem:
plasmashell graphical launcher: launching plasma (same whith any application). systematic with this account

Version-Release number of selected component:
plasma-workspace-5.9.5.1-1.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/bin/plasmashell
crash_function: KCrash::defaultCrashHandler
executable:     /usr/bin/plasmashell
global_pid:     2880
kernel:         4.11.6-201.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 KCrash::defaultCrashHandler at /usr/src/debug/kcrash-5.34.0/src/kcrash.cpp:434
 #3 __memmove_sse2_unaligned_erms at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:479
 #4 memcpy at /usr/include/bits/string3.h:53
 #5 QByteArray::QByteArray at tools/qbytearray.cpp:1586
 #6 DBPostingIterator::DBPostingIterator at /usr/src/debug/baloo-5.34.0/src/engine/postingdb.cpp:176
 #7 Baloo::PostingDB::iter at /usr/src/debug/baloo-5.34.0/src/engine/postingdb.cpp:169
 #8 Baloo::Transaction::postingIterator at /usr/src/debug/baloo-5.34.0/src/engine/transaction.cpp:294
 #9 Baloo::SearchStore::constructQuery at /usr/src/debug/baloo-5.34.0/src/lib/searchstore.cpp:190
 #11 Baloo::SearchStore::exec at /usr/src/debug/baloo-5.34.0/src/lib/searchstore.cpp:76
 #12 Baloo::Query::exec at /usr/src/debug/baloo-5.34.0/src/lib/query.cpp:210

Comment 1 a.thiaville 2017-06-27 09:37:48 UTC
Created attachment 1292233 [details]
File: backtrace

Comment 2 a.thiaville 2017-06-27 09:37:50 UTC
Created attachment 1292234 [details]
File: cgroup

Comment 3 a.thiaville 2017-06-27 09:37:52 UTC
Created attachment 1292235 [details]
File: core_backtrace

Comment 4 a.thiaville 2017-06-27 09:37:54 UTC
Created attachment 1292236 [details]
File: dso_list

Comment 5 a.thiaville 2017-06-27 09:37:56 UTC
Created attachment 1292237 [details]
File: environ

Comment 6 a.thiaville 2017-06-27 09:37:57 UTC
Created attachment 1292238 [details]
File: limits

Comment 7 a.thiaville 2017-06-27 09:38:02 UTC
Created attachment 1292239 [details]
File: maps

Comment 8 a.thiaville 2017-06-27 09:38:04 UTC
Created attachment 1292240 [details]
File: mountinfo

Comment 9 a.thiaville 2017-06-27 09:38:06 UTC
Created attachment 1292241 [details]
File: namespaces

Comment 10 a.thiaville 2017-06-27 09:38:07 UTC
Created attachment 1292242 [details]
File: open_fds

Comment 11 a.thiaville 2017-06-27 09:38:09 UTC
Created attachment 1292243 [details]
File: proc_pid_status

Comment 12 a.thiaville 2017-06-27 09:38:11 UTC
Created attachment 1292244 [details]
File: var_log_messages

Comment 13 a.thiaville 2017-06-27 10:13:49 UTC
severity very high almost critical almost because plasma desktop is broken and i have to kill the X server of this account. Session lost !!!

Comment 14 Rex Dieter 2017-06-27 12:40:40 UTC
You should be able to restart plasmashell (no need for session lost).

ALT-F2: plasmashell

Comment 15 a.thiaville 2017-07-04 06:43:43 UTC
Similar problem has been detected:

enter any text in plasmashell fedora graphical launcher. crash is now systematic .

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/bin/plasmashell
crash_function: KCrash::defaultCrashHandler
executable:     /usr/bin/plasmashell
global_pid:     23400
kernel:         4.11.7-200.fc25.x86_64
package:        plasma-workspace-5.9.5.1-1.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         plasmashell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1001

Comment 16 Fedora End Of Life 2017-11-16 15:18:48 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 17 Fedora End Of Life 2017-12-12 10:31:40 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.