couldnt burn cd when /tmp had 1GB instead of 3GB
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
brasero (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Binary package hint: brasero
Hi,
further to details in question: #57949
https:/
brasero 0.8.2 on ubuntu intrepid 8.10 with kernal updated to 2.6.27-9-generic
There was no place for selecting a working directory other than /tmp (that I could readily find) in the burn project area
when I tried burning the cd with a separate /tmp partition of 1GB the burn failed.
I released some of the spare space I had set aside to balance the system when I found out which file systems were growing the most and created a /tmp partition of 3GB and restarted the system, the burn ran OK.
It had only a few dozen MB used when brasero failed to burn cd when /tmp was 1GB
(This suggests I may get problems burning a DVD if I dont have /tmp of 8GB or more, once I get past the excessive directory level problem, but thats another story / bug report)
there are a couple of things to deal with :
- the burn project option doesnt have a properties selection button or similar (whereas the copy disc option does)
- the process seems to need more than 30% above the 750 MB that the ISO image file is likely to occupy during disc burning.
this might not be a problem if I had done the intrepid install and set aside only a separate /boot and /swap and bundled the rest of the space under the root directory /.
there should be enough info in
https:/
to supplement the above.
also some system details below:
david@johnstonp
8.10
intrepid
david@johnstonp
Linux johnstonpc1 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux
david@johnstonp
ii brasero 0.8.2-0ubuntu1 CD/DVD burning application for GNOME
david@johnstonp
Changed in brasero (Ubuntu): | |
importance: | Undecided → Low |
Thank you for your report. You can change the location for storing temporary files by specifying it in the gconf key "/apps/ brasero/ drives/ tmpdir" . To edit gconf settings, launch "gconf-editor".
I'm going to close this, as there doesn't appear to be any bug.