From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.6) Gecko/20050323 Galeon/1.3.20 Description of problem: nautilus-cd-burner keeps giving me the following error dialogue when I try drag files into the CD Creator: Error while link in "burn:///" There is not enough space on the destination However: - /tmp has 1GB free - my home directory has several GB free $ df -h /tmp /home/paul Filesystem Size Used Avail Use% Mounted on tmpfs 1000M 58M 943M 6% /tmp hibernia:/home/paul 20G 15G 4.6G 77% /home/paul $ df -i /tmp/ /home/paul Filesystem Inodes IUsed IFree IUse% Mounted on tmpfs 257065 1800 255265 1% /tmp hibernia:/home/paul 5155840 163261 4992579 4% /home/paul $ quota -s paul .. Filesystem blocks quota limit grace files quota limit grace hibernia:/home/paul 6291M 9668M 11670M 122k 180k 169k I tried using gconf to set the /apps/nautilus-cd-burner/temp_iso_dir key to /tmp, but still the same error message. The error message is uninformative. *what* is the destination? Where is it? If I knew, I could maybe fix the filesystem concerned, except the filesystems all appear to have plenty of space, so maybe it's an actual bug in nautilus-cd-burner in assessing free space. It's impossible to tell either way. I then ran: mkisofs -R ~/Desktop/temp/ | cdrecord -v fs=6m dev=/dev/hdc - Which worked fine. So: 1. The error message is most definitely uninformative and lacking a key detail (the fs concerned - without which knowledge the problem is impossible to resolve, if the problem is external to nautilus-cd-burner) 2. nautilus-cd-burner possibly has a bug in its logic to assess whether there is sufficient space free (but see 1 - I cant say for sure). I'm setting this to 'high' because while nautilus-cd-burner does not crash, it is rendered completely unuseable by this bug, when it strikes. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. drag files into cd-creator 2. get error message "not enough space on destination" 3. check that home and /tmp have plenty of space and inodes free, scratch head in bewilderment Expected Results: It should have: 1. Told me exactly which filesystem had insufficient space 2. If indeed this fs had enough space (which i think is possibly the case), it should not have produced the error in the first place Additional info:
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
Closing now, since too many FC releases have come and gone since this was marked as NEEDINFO