Bug 420527 - Unknown error condition in stat: Software caused connection abort
Summary: Unknown error condition in stat: Software caused connection abort
Status: RESOLVED DUPLICATE of bug 415436
Alias: None
Product: kio-extras
Classification: Frameworks and Libraries
Component: Samba (show other bugs)
Version: 19.12
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-24 21:30 UTC by Gregory Seaborn
Modified: 2020-04-27 09:40 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screen capture of Dolphin error and System Information (101.35 KB, application/pdf)
2020-04-24 21:30 UTC, Gregory Seaborn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gregory Seaborn 2020-04-24 21:30:52 UTC
Created attachment 127838 [details]
Screen capture of Dolphin error and System Information

SUMMARY
When I try to connect to a Samba share on one of my linux servers Dolphin fails with an error message.

Internal Error
Please send a full bug report at https://bugs.kde.org
Unknown error condition in stat: Software caused connection abort

STEPS TO REPRODUCE
1. click on Network in the Remote Section
2. click on Shared Folders (SMB) icon
3. on the smb title/url bar enter smb://XX.XX.XX.XX/Share name (in my case it was smb://192.168.1.11/Server1)

OBSERVED RESULT
red box pops up with the following:

Internal Error
Please send a full bug report at https://bugs.kde.org
Unknown error condition in stat: Software caused connection abort

EXPECTED RESULT

open up the shared folder

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora 31 KDE Plasma
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION

Kernel Version: 5.5.17-200.fc31.x86_64
Processors: 12 x Intel Xeon CPU E5-2667 0 @ 2.90GHz
Memory: 62.8 GiB of RAM
Comment 1 Harald Sitter 2020-04-27 09:40:57 UTC

*** This bug has been marked as a duplicate of bug 415436 ***