Geany ошибка при сохранении файла

aleksandr barakinaleksandr barakin

67.5k200 золотых знаков74 серебряных знака216 бронзовых знаков

I am not a windows expert, but a couple of questions/suggestions.

The number one is, are you running any plugins? And if you are, does the problem occur when you run with no plugins?

I presume you retried the save and the «permission denied» continued after you had checked that nobody had a handle on the file?

Are you using windows native dialogs or GTK dialogs? And does the problem occur when you try the other? I vaguely remember something about dialogs having locks on files or directories because they read the metadata to populate the dialog.

IIRC the gio_unsafe_save_backup needs use_gio_unsafe_file_saving set as well.

Does the problem occur if you have neither use_atomic_file_saving nor use_gio_unsafe_file_saving nor gio_unsafe_save_backup set?

(1) The number one is, are you running any plugins?

I’m not aware of. I have installed Geany today, and did not fiddle around with Plugins. Of course, it might be that Geany, out of the box, uses some Plugins which need to be disabled. In any case, the settings have a checkmark in «use plugins». If the pane which shows the map of my functions, is displayed by a plugin, then I would conclude that at least this plugin is running alongside.

(2) I presume you retried the save and the «permission denied» continued after you had checked that nobody had a handle on the file?

Of course, and, as I said, I for sure did not do anything with this file from a different program. Plus, the error occured on 3 files out of 5. And, I could save these files earlier in the same edit session.

(3) Are you using windows native dialogs or GTK dialogs?

They are GTK dialogs. I have now changed the settings to use Windows dialogues, but honestly, I like the GTK ones better.

(4) Does the problem occur if you have neither use_atomic_file_saving nor use_gio_unsafe_file_saving nor gio_unsafe_save_backup set?

Yes, the other ones were disabled as well, but this didn’t have any influence.

I wonder whether the problem might be related to a temporary directory or backup directory. Is Geany using some of them under the hood, maybe in my Windows Profile Data space? This is certainly an area which Geany should better keep its fingers off….

ADDITIONAL NOTE: After continuing to edit my files (after restarting Geany) for maybe 15 minutes, the error occured again. It is not possible to save the file.

Unfortunately, this version of Geany is not usable for me. I will therefore switch to a different editor, BUTif one of the Geany maintainers wants me to try out something, I will of course turn back to Geany, because I want to help to find the bug.

I have installed Geany today, and did not fiddle around with Plugins.

Ok, if its a new install and you didn’t enable any plugins in Tools->Plugin Manager then there should be none running, but maybe just check none are enabled in plugin manager.

Of course, and, as I said, I for sure did not do anything with this file from a different program. Plus, the error occured on 3 files out of 5. And, I could save these files earlier in the same edit session.

Thats fine, we have to check the obvious first 🙂

I have now changed the settings to use Windows dialogues, but honestly, I like the GTK ones better.

Let us know if the problem still occurs, the GTK dialogs are not something we build so I don’t know what they do, but I know they run extra threads, so maybe they trawl the filesystem to pre-load the dialogs, and I think I remember somewhere reports of them holding locks on stuff.

I wonder whether the problem might be related to a temporary directory or backup directory.

Other than its config directory that is saved in your user data (see Help->Debug Messages 4-5 down says where) Geany itself doesn’t fiddle with files other than your explicit save and load, but some plugins do, hence the first question.

Unfortunately, this version of Geany is not usable for me. I will therefore switch to a different editor, BUTif one of the Geany maintainers wants me to try out something, I will of course turn back to Geany, because I want to help to find the bug.

I presume that means the windows dialogs didn’t help 🙁

I know that there are some who use Geany on windows without problems, not sure if its 7 though, think its 10. Maybe they can provide some more suggestions on that might be unusual about your system.

I presume that means the windows dialogs didn’t help 🙁

This is correct.

If someone could provide me a special, instrumented version, which logs what is going on during saving, I could run it until the problem occurs again, and then send the logs.

I use it on Windows 7 and Windows 10 without this problem. All files I edit are local on the disk and both machines have my one user as an administrator. Not sure it helps.

Edit: Also both systems use all US-English locales and no files with non-ASCII filenames.
Edit2: Also I don’t use/have Cygwin at all, just using the offical Geany releases from the website.

Just for some rainy day reading see my PHD thesis on saving files in Geany on the wiki.

If someone could provide me a special, instrumented version, which logs what is going on during saving, I could run it until the problem occurs again, and then send the logs.

As the wiki article says, two of the three saving methods are from libraries that we don’t control, so there is not much that can be done to see what is going on there. The third saving method is so simple that there is nothing to log, it exits on the first error and gives you a failure dialog.

The error message in German in your OP does not seem to be one of ours, suggesting that you were running one of the library saving methods when that occurred. Our message says «Failed to open file ‘%s’ for writing: fopen() failed: %s», and the German translation also contains the «fopen()» part which is missing in the dialog you posted. Please make very sure that you have all three of the options use_atomic_file_saving and use_gio_unsafe_file_saving and gio_unsafe_save_backup turned off.

Finally thank you for continuing to help track the problem down, as you understand, until we can replicate it we can’t do anything to fix it.

I am new to geany, and I use it to update html and php files for my server, and I ran into the same issue. I searched online and no luck, then I tried the
«sudo chmod 775 filename.xxx» (xxx could stand for php, js, or whatever type of file).
This allowed the file to execute when being called from the browser. I was also able to
«sudo nano filename.xxx»

So i decided to try the command «sudo geany» which prompted for my password as usual when you use sudo and it worked. I was able to save.

So using the command geany assumes you’re logged in as root, and if you are, you shouldn’t have permission issues, but if not, you need to «sudo » into geany

«sudo nano filename.xxx»

If you have to sudo to edit the file you have your protections wrong, you need to fix them, not override them by running editors as root.

To be clear, the Geany team does NOT recommend running Geany as root, it is an IDE and some of the things it does as part of a normal development cycle may be security or other risks when run as root. You have been warned and you are responsible for any damage that may occur.

«sudo nano filename.xxx»

I don’t agree with the avoid-root-at-all-cost paranoia, but you can minimize the «danger» by running the editor as the actual user that owns the file with sudo -u. You can also avoid creating a new file with wrong ownership.

So using the command geany assumes you’re logged in as root, and if you are, you shouldn’t have permission issues, but if not, you need to «sudo » into geany

So what exactly was the issue?

I know this is old, but for the people coming here to fix the problem for themselves. You’re probably saving in the «Geany» folder and trying to execute your file out of the folder. Try saving your file on your desktop.

I have the same issue on network drives that I created with Win-SSHFS on Windows 10 and only in cases where the file already exist. The problem does not arise with other editors.

Geany 1.36

Hello,
I have just experienced the same problem today (after years of using Geany seamlessly). Can this be related to the fact that I have tried to input Unicode characters like «É» just before (unsuccessfully, by the way…), which I think I had never done before?
At each attempt of file saving, I get a new file named .goutputstream-XXXXXX instead, with the content of the file I am trying to save.
Yours,
Maxime

@MaximeG-51 when you say «input unicode characters» do you mean in the file contents or the filename?

Hi,
In the file contents. I tried to type Éduterre. The «Alt-144» method I use in other Windows applications did not work, so I tried the Ctrl-Shift-u method described in the Geany Help, to no success. The file name does not contain any accented character (not even those that are directly on my French keyboard).
Yours,
Maxime

Typing characters into the file is not part of this issue, if it failed to include the character it can have no effect on saving the file, but if you did manage to include it, and the Locale can’t store it in the file encoding, then save will fail, but with a different message to that which this issues is about.

I suggest you start a new issue and provide full system details and messages.

I am not a windows expert, but a couple of questions/suggestions.

The number one is, are you running any plugins? And if you are, does the problem occur when you run with no plugins?

I presume you retried the save and the «permission denied» continued after you had checked that nobody had a handle on the file?

Are you using windows native dialogs or GTK dialogs? And does the problem occur when you try the other? I vaguely remember something about dialogs having locks on files or directories because they read the metadata to populate the dialog.

IIRC the gio_unsafe_save_backup needs use_gio_unsafe_file_saving set as well.

Does the problem occur if you have neither use_atomic_file_saving nor use_gio_unsafe_file_saving nor gio_unsafe_save_backup set?

(1) The number one is, are you running any plugins?

I’m not aware of. I have installed Geany today, and did not fiddle around with Plugins. Of course, it might be that Geany, out of the box, uses some Plugins which need to be disabled. In any case, the settings have a checkmark in «use plugins». If the pane which shows the map of my functions, is displayed by a plugin, then I would conclude that at least this plugin is running alongside.

(2) I presume you retried the save and the «permission denied» continued after you had checked that nobody had a handle on the file?

Of course, and, as I said, I for sure did not do anything with this file from a different program. Plus, the error occured on 3 files out of 5. And, I could save these files earlier in the same edit session.

(3) Are you using windows native dialogs or GTK dialogs?

They are GTK dialogs. I have now changed the settings to use Windows dialogues, but honestly, I like the GTK ones better.

(4) Does the problem occur if you have neither use_atomic_file_saving nor use_gio_unsafe_file_saving nor gio_unsafe_save_backup set?

Yes, the other ones were disabled as well, but this didn’t have any influence.

I wonder whether the problem might be related to a temporary directory or backup directory. Is Geany using some of them under the hood, maybe in my Windows Profile Data space? This is certainly an area which Geany should better keep its fingers off….

ADDITIONAL NOTE: After continuing to edit my files (after restarting Geany) for maybe 15 minutes, the error occured again. It is not possible to save the file.

Unfortunately, this version of Geany is not usable for me. I will therefore switch to a different editor, BUTif one of the Geany maintainers wants me to try out something, I will of course turn back to Geany, because I want to help to find the bug.

I have installed Geany today, and did not fiddle around with Plugins.

Ok, if its a new install and you didn’t enable any plugins in Tools->Plugin Manager then there should be none running, but maybe just check none are enabled in plugin manager.

Of course, and, as I said, I for sure did not do anything with this file from a different program. Plus, the error occured on 3 files out of 5. And, I could save these files earlier in the same edit session.

Thats fine, we have to check the obvious first 🙂

I have now changed the settings to use Windows dialogues, but honestly, I like the GTK ones better.

Let us know if the problem still occurs, the GTK dialogs are not something we build so I don’t know what they do, but I know they run extra threads, so maybe they trawl the filesystem to pre-load the dialogs, and I think I remember somewhere reports of them holding locks on stuff.

I wonder whether the problem might be related to a temporary directory or backup directory.

Other than its config directory that is saved in your user data (see Help->Debug Messages 4-5 down says where) Geany itself doesn’t fiddle with files other than your explicit save and load, but some plugins do, hence the first question.

Unfortunately, this version of Geany is not usable for me. I will therefore switch to a different editor, BUTif one of the Geany maintainers wants me to try out something, I will of course turn back to Geany, because I want to help to find the bug.

I presume that means the windows dialogs didn’t help 🙁

I know that there are some who use Geany on windows without problems, not sure if its 7 though, think its 10. Maybe they can provide some more suggestions on that might be unusual about your system.

I presume that means the windows dialogs didn’t help 🙁

This is correct.

If someone could provide me a special, instrumented version, which logs what is going on during saving, I could run it until the problem occurs again, and then send the logs.

I use it on Windows 7 and Windows 10 without this problem. All files I edit are local on the disk and both machines have my one user as an administrator. Not sure it helps.

Edit: Also both systems use all US-English locales and no files with non-ASCII filenames.
Edit2: Also I don’t use/have Cygwin at all, just using the offical Geany releases from the website.

Just for some rainy day reading see my PHD thesis on saving files in Geany on the wiki.

If someone could provide me a special, instrumented version, which logs what is going on during saving, I could run it until the problem occurs again, and then send the logs.

As the wiki article says, two of the three saving methods are from libraries that we don’t control, so there is not much that can be done to see what is going on there. The third saving method is so simple that there is nothing to log, it exits on the first error and gives you a failure dialog.

The error message in German in your OP does not seem to be one of ours, suggesting that you were running one of the library saving methods when that occurred. Our message says «Failed to open file ‘%s’ for writing: fopen() failed: %s», and the German translation also contains the «fopen()» part which is missing in the dialog you posted. Please make very sure that you have all three of the options use_atomic_file_saving and use_gio_unsafe_file_saving and gio_unsafe_save_backup turned off.

Finally thank you for continuing to help track the problem down, as you understand, until we can replicate it we can’t do anything to fix it.

I am new to geany, and I use it to update html and php files for my server, and I ran into the same issue. I searched online and no luck, then I tried the
«sudo chmod 775 filename.xxx» (xxx could stand for php, js, or whatever type of file).
This allowed the file to execute when being called from the browser. I was also able to
«sudo nano filename.xxx»

So i decided to try the command «sudo geany» which prompted for my password as usual when you use sudo and it worked. I was able to save.

So using the command geany assumes you’re logged in as root, and if you are, you shouldn’t have permission issues, but if not, you need to «sudo » into geany

«sudo nano filename.xxx»

If you have to sudo to edit the file you have your protections wrong, you need to fix them, not override them by running editors as root.

To be clear, the Geany team does NOT recommend running Geany as root, it is an IDE and some of the things it does as part of a normal development cycle may be security or other risks when run as root. You have been warned and you are responsible for any damage that may occur.

«sudo nano filename.xxx»

I don’t agree with the avoid-root-at-all-cost paranoia, but you can minimize the «danger» by running the editor as the actual user that owns the file with sudo -u. You can also avoid creating a new file with wrong ownership.

So using the command geany assumes you’re logged in as root, and if you are, you shouldn’t have permission issues, but if not, you need to «sudo » into geany

So what exactly was the issue?

I know this is old, but for the people coming here to fix the problem for themselves. You’re probably saving in the «Geany» folder and trying to execute your file out of the folder. Try saving your file on your desktop.

I have the same issue on network drives that I created with Win-SSHFS on Windows 10 and only in cases where the file already exist. The problem does not arise with other editors.

Geany 1.36

Hello,
I have just experienced the same problem today (after years of using Geany seamlessly). Can this be related to the fact that I have tried to input Unicode characters like «É» just before (unsuccessfully, by the way…), which I think I had never done before?
At each attempt of file saving, I get a new file named .goutputstream-XXXXXX instead, with the content of the file I am trying to save.
Yours,
Maxime

@MaximeG-51 when you say «input unicode characters» do you mean in the file contents or the filename?

Hi,
In the file contents. I tried to type Éduterre. The «Alt-144» method I use in other Windows applications did not work, so I tried the Ctrl-Shift-u method described in the Geany Help, to no success. The file name does not contain any accented character (not even those that are directly on my French keyboard).
Yours,
Maxime

Typing characters into the file is not part of this issue, if it failed to include the character it can have no effect on saving the file, but if you did manage to include it, and the Locale can’t store it in the file encoding, then save will fail, but with a different message to that which this issues is about.

I suggest you start a new issue and provide full system details and messages.

asked Oct 26, 2012 at 11:15

This problem has been reported since 2009 (example _[archived]). It is awful that there’s no fix for it yet. Neither VirtualBox nor Gedit developers are willing to take responsibility for it, and instead are content to point fingers at one another for over three years.

You can set your editor preferences to ‘Create a backup’ then save twice. Incredibly painful, but it works.

Some other editors won’t report the problem. However, when I tested Kate and nano, for example, those just silently deleted the file on every other save. That’s even worse than the gedit situation…

“Text file busy” can be confusing here: it isn’t actually about text files, but about executables. Executables are called text files because… hum, actually, I don’t know why.

What the message really means is “this file is locked by another program that is using it and can’t let it be modified under its nose, so you can’t write to it.” It is quite unusual to see this message for a text file: unix systems generally frown on mandatory locks on files, and there is no facility for applications to lock out others from modifying a file. (Unix has advisory locks: they can be used to synchronize concurrent accesses to a file by cooperating programs.) The most common circumstance when you’ll see “text file busy” (ETXTBUSY) is if you try to modify an executable that’s running: the kernel locks it. Another possibility is a disk image that is mounted, again locked by the kernel.

In your case, given the location of the file /media/sf_Ubuntu and the ownership to the group vboxsf, my guess is that the file, which is on a VirtualBox file sharing filesystem, is locked in the host operating system. Presumably the host is a Windows machine and you also have the file open in an editor there. You’ll need to close the file on the host before you can save in the editor in the VM.

answered Oct 26, 2012 at 12:20

What fixed it for me (still a bit annoying but works), and is applicable to gedit, is to:

edit — preferences — editor
Put a check on «Create backup copy»

When saving from now on, save the file once, ignore the error, save again.
works every time.

answered Nov 12, 2013 at 15:21

asked Oct 26, 2012 at 11:15

This problem has been reported since 2009 (example _[archived]). It is awful that there’s no fix for it yet. Neither VirtualBox nor Gedit developers are willing to take responsibility for it, and instead are content to point fingers at one another for over three years.

You can set your editor preferences to ‘Create a backup’ then save twice. Incredibly painful, but it works.

Some other editors won’t report the problem. However, when I tested Kate and nano, for example, those just silently deleted the file on every other save. That’s even worse than the gedit situation…

“Text file busy” can be confusing here: it isn’t actually about text files, but about executables. Executables are called text files because… hum, actually, I don’t know why.

What the message really means is “this file is locked by another program that is using it and can’t let it be modified under its nose, so you can’t write to it.” It is quite unusual to see this message for a text file: unix systems generally frown on mandatory locks on files, and there is no facility for applications to lock out others from modifying a file. (Unix has advisory locks: they can be used to synchronize concurrent accesses to a file by cooperating programs.) The most common circumstance when you’ll see “text file busy” (ETXTBUSY) is if you try to modify an executable that’s running: the kernel locks it. Another possibility is a disk image that is mounted, again locked by the kernel.

In your case, given the location of the file /media/sf_Ubuntu and the ownership to the group vboxsf, my guess is that the file, which is on a VirtualBox file sharing filesystem, is locked in the host operating system. Presumably the host is a Windows machine and you also have the file open in an editor there. You’ll need to close the file on the host before you can save in the editor in the VM.

answered Oct 26, 2012 at 12:20

What fixed it for me (still a bit annoying but works), and is applicable to gedit, is to:

edit — preferences — editor
Put a check on «Create backup copy»

When saving from now on, save the file once, ignore the error, save again.
works every time.

answered Nov 12, 2013 at 15:21