Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Permission denied on SAMBA network drive #17858

Closed
1 task done
TvviNN opened this issue Aug 14, 2018 · 4 comments
Closed
1 task done

Permission denied on SAMBA network drive #17858

TvviNN opened this issue Aug 14, 2018 · 4 comments

Comments

@TvviNN
Copy link

TvviNN commented Aug 14, 2018

Prerequisites

Description

I cannot open folders in a SAMBA network drives as projects. Trying to open folders on the network drive gives the "Permission denied" error. Opening files is possible, but saving is not permitted (Unable to save file '[path]' --- EEXIST: file already exists, mkdir '[path]')

Steps to Reproduce

  1. Mount a folder including a file on a SAMBA network
  2. Open Atom Editor and try to open the folder as a project folder, folder or directly open the file.
  3. Try to save the opened file.

Expected behavior: Be able to open folder or save the file.

Actual behavior:

  • Trying to open network folder as project: Project folder does not even show up, nothing happens.
  • Trying to open folder: New window is opened, but "Permission denied" error is displayed.
  • Unable to save files.

Reproduces how often: 100%

Versions

Atom Version 1.29.0
apm 1.19.0
npm 3.10.10
node 6.9.5 x64

OS: Windows 7 Enterprise - Service Pack 1

Additional Information

Trying to do all these things (opening project folder, folder or save file) on the local file system works as it should. In addition, opening SAMBA network files and editing is no problem with other programs like, e.g., Notepad++.

@rsese
Copy link
Contributor

rsese commented Aug 15, 2018

Thanks for the report - is this behavior new for you after updating to 1.29 and worked previously or is this a fresh install?

Also, do you see any difference if you try the other options for Settings > Core > File System Watcher?

@TvviNN
Copy link
Author

TvviNN commented Aug 15, 2018

Unfortunately I did never try to access network directories using SAMBA before.

I tried all other options and did not see any difference, the problems still persist.

@stale
Copy link

stale bot commented Sep 20, 2019

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. Because the Atom team treats their issues as their backlog, stale issues are closed. If you would like this issue to remain open:

  1. Verify that you can still reproduce the issue in the latest version of Atom
  2. Comment that the issue is still reproducible and include:
    • What version of Atom you reproduced the issue on
    • What OS and version you reproduced the issue on
    • What steps you followed to reproduce the issue

Issues that are labeled as triaged will not be automatically marked as stale.

@stale stale bot added the stale label Sep 20, 2019
@stale stale bot closed this as completed Oct 4, 2019
@lock
Copy link

lock bot commented Apr 2, 2020

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@lock lock bot locked as resolved and limited conversation to collaborators Apr 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants