| Summary: | Quite much "kf.kio.core: An error occurred during write" output in syslog | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | nttkde <watisthispoo> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | 4wy78uwh, dolphin-bugs-null, meven29 |
| Priority: | NOR | ||
| Version First Reported In: | 24.05.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=486697 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
nttkde
2024-06-12 23:04:48 UTC
Looks like the error is printed from from SlaveBase::send() in frameworks/kio/src/core/slavebase.cpp. Printing cmd and arr when the error is printed seem to every time have values cmd: 102 and arr seems to contain string "Cannot create thumbnail for directory". Looking a bit more carefully into the source of the error, SlaveBase::send seems to call -> Connection::send() [kio/src/core/connection.cpp] -> Connection::sendnow() -> ConnectionBackend::sendCommand() [kio/src/core/connectionbackend.cpp] which then sometimes returns false with socket->state() being QLocalSocket::UnconnectedState. And newer Dolphin/KIO now logs a PeerClosedError right before the 'write' error: kioworker[329483]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError kioworker[329483]: kf.kio.core: An error occurred during write. The worker terminates now. This issue is most common with the thumbnail:/ kioworker. Since it can be a slow worker, it has a tendency to be interrupted abruptly when refreshing a directory for instance. Those warnings points out this could be handled gracefully instead of having outside of expectation result devs should be wary of (what warnings are for). (In reply to nttkde from comment #2) > And newer Dolphin/KIO now logs a PeerClosedError right before the 'write' > error: If of any use, https://forum.qt.io/post/664235 provides some insight into the cause. A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/2035 |