Created attachment 170120 [details] Generated Kioworker Crash Log SUMMARY STEPS TO REPRODUCE 1. Open Signal Desktop (tested on Flatpak and Deb installed via PPA; bug is reproducable and happens everytime) 2. Download File 3. Crash OBSERVED RESULT Hundreds of error messages EXPECTED RESULT Just download the file OS: TUXEDO OS 3 x86_64 6.5.0-10040-tuxedo Plasma 6.0.4 ADDITIONAL INFORMATION I got a PDF from a friend. The file is not corrupted and downloads on my Android phone in 1 second and can also be viewed. When I try to download it on Signal Desktop, Plasma sends me hundreds of "Kioworker closed unexpectedly" messages. Even before the file is downloaded, it sends the messages. When I choose the home directory for the download location in Dolphin, it doesn't download. When I chose a different folder like Downloads or Desktop, it downloads. The file has no problem and can be viewed. I downloaded the log and attached it. My system gets very loud and even shut down when this happened the first time. Absolute crazy bug I've never encountered before.
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: 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!
Created attachment 170130 [details] coredumpctl gdb
(In reply to David Redondo from comment #1) > 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: > 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! I'm not sure if I reported everything you wanted, may you look into the .txt and tell me if I need to do something else? 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!
The same exact issue happened to me right now - this time on my KDE Plasma 6.1 Desktop PC. This time, I had Signal installed as Snap, so the issue occured once with Flatpak and once with Snap, implying that it is 100% a KDE issue. In my opinion, this is a critical bug.
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!