Bug 466883 - Unable to edit samba share
Summary: Unable to edit samba share
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdenetwork-filesharing
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-05 12:20 UTC by matthewlupica
Modified: 2023-03-06 23:32 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description matthewlupica 2023-03-05 12:20:44 UTC 
SUMMARY
***
Unable to edit files on samba share. Previously this was possible, now I receive the message :

Internal Error
Please send a full bug report at http://bugs.kde.org
Unknown error condition in stat: Read-only file system
***


STEPS TO REPRODUCE
1. Access samba share.
2. Attempt to copy to, or create new file.
3. Unable.

OBSERVED RESULT
Internal Error
Please send a full bug report at http://bugs.kde.org
Unknown error condition in stat: Read-only file system

EXPECTED RESULT
Previously I was able to complete these tasks using Dolphin without any issue.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
Operating System: Debian GNU/Linux 10
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-21-amd64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz
Memory: 15.6 GiB of RAM

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2023-03-06 23:32:56 UTC 
I'm afraid Plasma 5.14 is unfortunately no longer eligible for support or maintenance. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. Please update to Plasma 5.27 as soon as your distro offers it to you. If you need support for Plasma 5.14, please contact your distro, who bears the responsibility of providing support for older non-LTS releases.

If you can reproduce the issue after upgrading to Plasma 5.27, feel free to re-open this bug report.

Thanks for understanding!