Summary: | Spectacle screenshot | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Manuel <manuelserranomtz24> |
Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | kdelibs-bugs, nate |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.80.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Manuel
2021-03-21 02:39:10 UTC
#6 QImage::copy(QRect const&) const (this=0x7ffc71b884c0, r=...) at image/qimage.cpp:1182 #7 0x00007f5fa11a11ac in () at /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #8 0x00007f5f9f9806fe in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc71b88640, r=0x557546cc4600, this=0x557546af4820) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate<false>(QObject*, int, void**) (sender=0x5575451ab590, signal_index=25, argv=0x7ffc71b88640) at kernel/qobject.cpp:3886 #10 0x00007f5f9ee7fed8 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () at /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #11 0x00007f5f9ee8052d in KIO::TransferJob::slotData(QByteArray const&) () at /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #12 0x00007f5f9f9806fe in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc71b887f0, r=0x5575451ab590, this=0x557546afa200) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate<false>(QObject*, int, void**) (sender=0x5575453d4270, signal_index=3, argv=0x7ffc71b887f0) at kernel/qobject.cpp:3886 #14 0x00007f5f9ee41706 in KIO::SlaveInterface::data(QByteArray const&) () at /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 Something in KIO is not happy about the image that was saved, but it's hard to tell anything more without debug symbols for KIO. I notice that you have debug symbols for Qt; can you install them for kio too and attach a new, fully symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29for instructions. Thanks! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |