https://bugs.kde.org/show_bug.cgi?id=476113
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Version|5.27.9 |5.111.0
Component|general |general
Target Milestone|1.0 |---
Product|plasmashell |frameworks-kactivities-stat
| |s
Assignee|plasma-b...@kde.org |ivan.cu...@kde.org
Resolution|--- |WAITINGFORINFO
CC| |n...@kde.org,
| |plasma-b...@kde.org
--- Comment #2 from Nate Graham <n...@kde.org> ---
Thank you for the bug report! Unfortunately the backtrace is incomplete and
missing debug symbols for the following lines that we need to figure out
exactly what's going wrong:
Thread 1 (Thread 0x7f891e32a640 (LWP 2606)):
[KCrash Handler]
#6 0x00007f8925e18e66 in () at
/lib/x86_64-linux-gnu/libKF5ActivitiesStats.so.1
#7 0x00007f894ccdc253 in () at /lib/x86_64-linux-gnu/libstdc++.so.6
#8 0x00007f894c894ac3 in start_thread (arg=<optimized out>) at
./nptl/pthread_create.c:442
#9 0x00007f894c926a40 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Could you please install debug symbols for the kactivitiesstats framework, and
attach a new symbolicated backtrace generated using the `coredumpctl`
command-line program? See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
for details about how to do this.
Thanks again!
--
You are receiving this mail because:
You are watching all bug changes.
