https://bugs.kde.org/show_bug.cgi?id=522306
Bug ID: 522306
Summary: KIO SMB fails to open files from TP-link Archer AX55
USB SMB share while directory browsing works and CIFS
mount correctly
Classification: I don't know
Product: kde
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
## Summary
KIO SMB is able to browse a USB SMB share exported by a TP-Link Archer AX55
router, but opening files through `smb://` is unreliable or fails, while the
same files work correctly when the share is mounted through CIFS.
The problem appears to be specific to KIO because:
* smbclient works correctly
* CIFS mount works correctly
* applications work correctly when accessing the mounted filesystem
---
## Environment
Distribution:
CachyOS (Arch Linux based)
Kernel:
Linux 7.1.1-2-cachyos
Desktop:
KDE Plasma 6.7.1
Frameworks:
6.27.0
Qt:
6.11.1
Applications:
* Dolphin 26.04.2
* Kate 26.04.2
* Ark 26.04.2
Router:
TP-Link Archer AX55 v1
Firmware:
1.5.10 Build 20251119 rel.50509(4555)
---
## Steps to reproduce
1. Open Dolphin.
2. Browse to:
smb://192.168.0.1/G
3. Browse folders.
4. Open a text file.
5. Open an ISO image using Ark.
---
## Expected result
Applications should open files directly from the SMB share.
---
## Actual result
Directory browsing works.
Opening files is unreliable:
* Kate reports that the file does not exist.
* Ark sometimes opens an empty archive or reports errors.
* KIO prints:
```
Socket not connected QLocalSocket::PeerClosedError
An error occurred during write. The worker terminates now.
```
Sometimes retrying works.
---
## Additional tests
The SMB server itself works correctly.
Verified:
* smbclient can browse files.
* smbclient can download large files.
* smbclient can upload files.
* CIFS mount works.
* Kate, Ark, Dolphin all work perfectly when using the mounted filesystem.
Example mount:
vers=2.0
Applications work normally through:
/mnt/router
This strongly suggests the issue is in KIO SMB interaction with this SMB server
rather than the server itself.
--
You are receiving this mail because:
You are watching all bug changes.
