https://bugs.kde.org/show_bug.cgi?id=416895
Bug ID: 416895
Summary: kdeinit5 crashes after return from suspend
Product: frameworks-kio
Version: 5.66.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: HTTP
Assignee: kdelibs-b...@kde.org
Reporter: frank-fisc...@shadow-soft.de
Target Milestone: ---
Created attachment 125511
--> https://bugs.kde.org/attachment.cgi?id=125511&action=edit
backtrace of crash
Whenever I return my laptop from suspension (after a few minutes), kdeinit5
crashes with the attached backtrace. I think this is related to Bug 402646, but
in my case the culprit seems to be from a http/dav connection (it could be a
synchronization connection in the background for a calendar).
I've tried to track down the bug a little. It seems that the function
KIO::SlaveBase::waitForAnswer hits a qFatal if the received response type (or
"command") is not the expected one. In particular, the syslog says
kdeinit5[9992]: Fatal Error: Got cmd 77, while waiting for an answer!
If I understand the code correctly, 77 means CMD_SPECIAL, which is not one of
the expected commands checked by the call to "isSubcommand", hence the qFatal
is hit.
I can only speculate what the reason is, but I would suspect some kind of race
condition (caused by the suspend), the received message belongs to some other
request or so.
Anyway, the main question to me is in this case ... why is there this qFatal?
If the received message originates from a (potentially) external source (please
forgive me if this assumption is wrong, I am not really familiar with the kio
code), then any received message could contain garbage for whatever reason. So
wouldn't it more sensible to return with an error instead of crashing the
program? (i.e. replace the call to qFatal by "return -1" or so, so that it is
the task of the caller to handle the error correctly)
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66
Qt Version: 5.14.0
--
You are receiving this mail because:
You are watching all bug changes.
