Bug 1594705
| Summary: | Opening output file: Invalid argument, /run/user/1000/gvfs/smb-share: ... | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chrit van Ewijk <cvanewijk> |
| Component: | emacs | Assignee: | Jan Synacek <jsynacek> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 28 | CC: | cvanewijk, jkeating, jonathan.underwood, jsynacek, msekleta, phracek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-28 20:46:00 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
Created attachment 1454293 [details]
Screen shot 2 Nemo
Created attachment 1454294 [details]
screenshot 3 Error message when trying to save buffer
Created attachment 1454295 [details]
screenshot 4 gedit does not not give an error message and saves the buffer correctly.
I have a problem in Emacs with saving buffers to my Synology diskstation DS115j DSM 6.2-23739. For details see attachments. The problem did never occur earlier. I have the same problem on a second PC. I could save the same buffer to trhe diskstation without a problem with Gedit. The diskstation also plays music also without a problem. --Chrit Created attachment 1454298 [details]
screenshot 5 Synology diskstation status
An attempt to transribe the important part from the log: ... Saving file /run/user/1000/gvfs/smb-share:server=synology-nas.local,share=home/synx/S/Abelson/Test/add.scm... basic-save-buffer-2: Opening output file: Invalid argument, /run/user/1000/gvfs/smb-share:server=synology-nas.local,share=home/synx/S/Abelson/Test/add.scm ... My guess would be that the lisp code simply chokes on the funny file path. If you start emacs without any buffers (emacs -Q) and then open the same file (C-x C-f) that you're having troubles saving, does it work without any problems? Created attachment 1454323 [details]
screen 6 after test emacs -Q
Created attachment 1454324 [details]
screen 7 after emacs -Q
Created attachment 1454325 [details]
screen 8 after emacs -Q
Created attachment 1454326 [details]
screen 9 after emacs -Q
It still has the same problem.
--Chrit
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 1454292 [details] screenshot 1 log Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: