After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 609566 - gedit can't save existing files on VirtualBox shared folders
gedit can't save existing files on VirtualBox shared folders
Status: RESOLVED OBSOLETE
Product: gedit
Classification: Applications
Component: general
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
: 614625 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-02-10 17:57 UTC by lietk12
Modified: 2016-11-26 22:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description lietk12 2010-02-10 17:57:21 UTC 
This bug has been reported here:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/341725

For Ubuntu (other distros have not been tested) inside VirtualBox with Guest Additions, if gedit attempts to edit a file on a shared folder, gedit fails to save, and instead returns a "Text file busy" error:

~$ gedit /mnt/share/foobar.txt

** (gedit:1942): WARNING **: Hit unhandled case 0 (Text file busy) in parse_error.

However, this issue only occurs with "save", and only with gedit.  If gedit edits the file and the user does "Save as" for any file name (including the same file name as the original file), gedit saves the file's changes without complaining.  If nano (or any other editor) modifies the file and tries to save it, the file's changes are saved.
Comment 1 jessevdk@gmail.com 2010-04-26 22:17:49 UTC 
*** Bug 614625 has been marked as a duplicate of this bug. ***
Comment 2 EgonF 2012-02-24 09:37:29 UTC 
The same in gedit 2.30.4

Maybe this is a hint:
gedit creates a hidden temporary file in the shared folder when a changed file should be saved. But gedit cannot change file names so the save command is not finished.
Comment 3 EgonF 2012-02-24 20:37:25 UTC 
geany has the same problem

Maybe something is wrong in GTK
Comment 4 Kevin Hagner 2016-11-26 22:23:50 UTC 
Thanks for taking the time to report this.
However, you are using a version that is too old and not supported anymore by GNOME developers. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes by GNOME developers for the version that you use. Edition of files through a VirtualBox shared folder with Gedit 3.22 works fine.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.

Please feel free to reopen this bug report if the problem still occurs with a recent version of GNOME, or feel free to report this bug in the bug tracking system of your Linux distribution if your distribution still supports the version that you are using.