https://bugs.kde.org/show_bug.cgi?id=490624

Nate Graham <n...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |NEEDSINFO
                 CC|                            |n...@kde.org
         Resolution|---                         |WAITINGFORINFO

--- Comment #1 from Nate Graham <n...@kde.org> ---
Thank you for the bug report! Unfortunately I can't reproduce the crash myself
on current git master, and the backtrace is incomplete and missing debug
symbols for the following lines that we need to figure out exactly what's going
wrong:

#4  0x00007f2824db9640 in ??? () at
/usr/lib64/qt6/qml/org/kde/plasma/private/kicker/libkickerplugin.so
#5  0x00007f2824dba750 in ??? () at
/usr/lib64/qt6/qml/org/kde/plasma/private/kicker/libkickerplugin.so
#6  0x00007f2824dbb7f5 in ??? () at
/usr/lib64/qt6/qml/org/kde/plasma/private/kicker/libkickerplugin.so
#7  0x00007f2824d9f120 in ??? () at
/usr/lib64/qt6/qml/org/kde/plasma/private/kicker/libkickerplugin.so

Could you please install debug symbols and attach a new symbolicated backtrace
generated by using `coredumpctl gdb` in a terminal window? 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.

Reply via email to