GNOME Bugzilla – Bug 158562
Bug in the creation of the tmp ISO of the project
Last modified: 2011-01-13 12:38:44 UTC
Description of Problem: If I try to burn a CD bigger than 250Mb the program stops to running because it try to create the ISO of the CD on the /tmp directory, but this directory has a limit of 250Mb, so the program can't complete the creation of the ISO. I modify the temporaney directory of nautilus-cd-burner in gconf but Coaster continue to create the ISO in /tmp even if I modified it Steps to reproduce the problem: 1. Create a project bigger then 250Mb 2. Burn the CD Actual Results: The program stops when the ISO of the project that is writing fill the /tmp directory (250Mb) Expected Results: The program burn CD bigger than 250Mb How often does this happen? Every time I create a CD bigger than 250Mb Additional Information: I think that there is a bad call of a function or that you must add in the option of the program the possibility of select the directory where Coster creates the temporaney ISO of the project
The problem is that I use only the glib tempdir function to get the temporary directory. I thought I checked the space on the device that holds that directory, but maybe I need to check limits on directories as well. This is a problem I haven't figured out how to handle. It's on my personal TODO list.
Maybe if we use ~ to create a tmp directory. I have seen the 250mb limit on /tmp, so the only restrition putting it in ~ would do is depend on the users space. We might want to make a dialog to help handle this situation better.
It is important for me, too, because i just use a tmpfs over /tmp so it wont be able to burn this way here.
I suggest that Coaster should check for space free on /tmp, and space free on the user's home directory, and perhaps space free on /var, and pick one that has enough free space for the ISO image. Note that Coaster does not handle running out of space; not only does Coaster always use /tmp, but if /tmp gets full, Coaster doesn't figure it out and stop operations, it just sits there burning CPU. Coaster should not only check that there is adequate space for the ISO image before attempting to make it, Coaster should also handle running out of space (for the rare case where you start out with 5 GB free, and another process burns up 2 GB of disk before you make your 4.3 GB ISO image for a DVD!). Actually, that could happen with a naive user who has two DVD burners, and tries to burn two DVDs at once; his system might have enough free space for one ISO image but not two. There is a workaround: choose "export to ISO" and then put the ISO somewhere that has enough free space. Then burn from the ISO.
Coaster development has been stalled and it has been unmaintained for a few years now. Maintainers don't have future development plan so i am closing bugs as WONTFIX. Please feel free to reopen the bugs in future if anyone takes the responsibility for active development.