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 726065 - Can't open, save, export, ar do anything like that because of "To many open files"
Can't open, save, export, ar do anything like that because of "To many open f...
Status: RESOLVED DUPLICATE of bug 705367
Product: GIMP
Classification: Other
Component: General
2.8.10
Other Mac OS
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2014-03-10 21:24 UTC by Brian Goerzen
Modified: 2014-03-10 21:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
This is what it looks like if I save it (846.12 KB, image/png)
2014-03-10 21:24 UTC, Brian Goerzen
Details

Description Brian Goerzen 2014-03-10 21:24:10 UTC
Created attachment 271478 [details]
This is what it looks like if I save it

I had a lot of windows open, then slowly closed them as I put them into a picture. I am trying to make an animation, so I would make a picture, export it as a .jpg, then make more changes. I have 25 pictures now, and it just randomly stopped working when I tried to export it. Now when-ever I try to save it, an error window pops up saying "Could not read the contents of Documents: Too many open files" When I export and open files it says the same thing. 

I tried to look in the help window, but that caused a lot of errors as well. Now, in the drop down menu, the help menu is completely blank, except for showing a couple short cuts, and the arrows. I want to try restarting the application, but I will lose all of my work.
Comment 1 Michael Schumacher 2014-03-10 21:28:16 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 705367 ***