Burning via "Write to..." in nautilus leads to some files being corrupt

thanks for your bug, it's not really useful described as it and bumping the
settings will not make it fixed.
- what version of ubuntu are you using?
- what version of nautilus-cd-burner are you using?
- what architecture are you using?
- how have you recorded your CD? from an ISO or from some files?
- does it happen all the time?
- what kind of CD/DVD do you use? RW ones?
- does it work fine with cdrecord?
- can you get a log of what happens:
  - set /apps/nautilus-cd-burner/debug with gconf-editor
  - "gnome-session remove nautilus"
  - "nautilus"

It works fine here and for other users, I'm marking this bug as a normal one.

(In reply to comment #1)
> thanks for your bug, it's not really useful described as it and bumping the
> settings will not make it fixed.
I'm using Ubuntu 5.04, fully updated. I have 2.10.0-0ubuntu2 version of
nautilus-cd-burner. I'm on a i686 Pentium 3 Coppermine (a Dell Optiplex GX200).
I recorded files onto the disk, but note that in the processes of making the cd,
the progress bar says it is making and ISO first. This happens all the time, but
note that I used gnomebaker (ver. 0.3-3) successfully to create the same data CD
with those files. I was using Phillips 52x 700MB 80min CD-R's but I don't think
that's the problem because, I have used a spindle of 50 and am almost done. On
Debian via K3B, I never had a problem burning onto this brand of disk. I'm not
quite sure how to use cdrecord, but I assume gnomebaker uses it.

I burned another disk with the debug enable, but I can't yet figure out where
the debug log is stored. This CD also has corrupted files. I think that the disk
burned too quickly, also. I had about ~300 MB of data and it finished after a
couple seconds/or a minute.

> - can you get a log of what happens:
> - set /apps/nautilus-cd-burner/debug with gconf-editor
> - "gnome-session remove nautilus"
> - "nautilus"
>
> It works fine here and for other users, I'm marking this bug as a normal one.
>

thanks for the comment.

  - set /apps/nautilus-cd-burner/debug with gconf-editor
  - "gnome-session remove nautilus"
  - "nautilus"

gives you the log where you run "nautilus"

(In reply to comment #3)
> thanks for the comment.
>
> - set /apps/nautilus-cd-burner/debug with gconf-editor
> - "gnome-session remove nautilus"
> - "nautilus"
>
> gives you the log where you run "nautilus"

I don't think that works for me
$ gnome-session remove nautilus
gnome-session: you're already running a session manager
$ nautilus
$

nautilus is run, but the terminal (GNOME Terminal 2.10.0) moves on afterwards to
the next $ line

that's one more CD-R lost in the name of science : )

(In reply to comment #4)

> I don't think that works for me
> $ gnome-session remove nautilus
> gnome-session: you're already running a session manager

sorry, typo, "gnome-session-remove", should work better :)

(In reply to comment #2)
> This CD also has corrupted files. I think that the disk
> burned too quickly, also. I had about ~300 MB of data and it finished after a
> couple seconds/or a minute.

Have you tried burning with burnproof enabled? In gconf-editor, enable the
setting /apps/nautilus-cd-burner/burnproof.

I think it might be similar to bug 18298

I enabled burnproof but also used the GnomeBaker application, maybe this output
will help the other problem?

cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Continuing in 5 seconds...
cdrecord: Warning: Running on Linux-2.6.10-5-386
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/hdc'
devname: '/dev/hdc'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
cdrecord: Warning: using unofficial version of libscg (ubuntu-0.8ubuntu1
'@(#)scsitransp.c 1.91 04/06/17 Copyright 1988,1995,2000-2004 J. Schilling').
SCSI buffer size: 64512
Cdrecord-Clone 2.01a38 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Joerg Schilling
NOTE: this version of cdrecord is an unofficial (modified) release of cdrecord
      and thus may have bugs that are not present in the original version.
      Please send bug reports and support requests to
<email address hidden>.
      The original author should not be bothered with problems of this version.

TOC Type: 3 = CD-ROM XA mode 2
Using libscg version 'ubuntu-0.8ubuntu1'.
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : ' '
Identifikation : '52X24X52 CD-RW '
Revision : '1.06'
Device seems to be: Generic mmc CD-RW.
Current: 0x0009
Profile: 0x0008
Profile: 0x0009 (current)
Profile: 0x000A
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R
Drive buf size : 1359872 = 1328 KB
FIFO size : 4194304 = 4096 KB
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
Track 01: data 609 MB
Total size: 700 MB (69:21.89) = 312142 sectors
Lout start: 700 MB (69:23/67) = 312142 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 5
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type A, high Beta category (A+) (3)
  ATIP start of lead in: -11634 (97:26/66)
  ATIP start of lead out: 359846 (79:59/71)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Blocks total: 359846 Blocks current: 359846 Blocks remaining: 47704
Forcespeed is OFF.
Starting to write CD/DVD at speed 24 in real TAO mode for multi session.
Last chance to quit,
starting real write in 2 seconds. 1 seconds. 0
seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is ON.
Turning BURN-Free off
Performing OPC...
Starting new track at sec...

thanks for your log. This since to be a linux or cdrecord issue. Do you have the
issue with k3b by example? Does changing the write speed fix the issue?

no reply, bug closed. Feel free to reopen with the asked informations if that's
still an issue for you

I ran out of CD-R's to test. k3b had the issue too, if I recall correctly. Note
that I didn't make any modifications to the installed software as it was
installed/updated in 5.04. Now, I do recall having this problem before on
another distribution (maybe Debian, maybe non-Debian) in Gnome burning tools,
however I was able to configure k3b in that distribution to work without
problems most of the time-- it was quite reliable. So, this may be a hardware
issue, too (with relation to cdrecord)?

Well, I had this issue and I understand what happens.

In fact, if you burn as root, you will have no problem. The normal user has just
not enough privilege to set his cdrecord process in high priority for the
kernel, so the burning process is often interupted and that leads to corrupted
files.
The workaround was simply to burn as root.

I solved definitly this issue by adding myself to a group, but I don't remmeber
wich one.

can you try what Lionel described and note if that fixes your issue?

(In reply to comment #12)
> can you try what Lionel described and note if that fixes your issue?

I just bought more CD-R's, I think I have spent more than 5 already. I should
invest in CD-RW : )

I tried with sudo nautilus and used the "write to disc..." function but this did
not work either. I get a success message but only part of the disc has been
written to (you can see darker parts on foil where data has been written to.
When I run the files, they are bogus.

Another experiment I did before this was to use k3b on default settings
(non-root) and the file burned more completely except there were obvious errors
this time since the video did not contain sound when played off the disc versus
off the harddrive.

I do remember having to be root user to successfully burn in k3b when I used
Debian Testing/Sarge. There was a solution that allowed regular users tburn in
k3b which may have involved downloading extra packages and changing a few
settings. I never remember successfully making a disc in GNOME my entire Linux
career. My successes were all in k3b which became quiet reliable.

I didn't have debug report printed while burning but I expect it to be the same
as the previous one I posted. And again, this hardware has been able to write
many many successful discs (of many different types) with k3b.

Do you still get this problem with Breezy?

It seems that this bug is solved in Breezy. My mother's computer had the problem in Hoary but just dist-upgrade to breezy solved it.

She's even able to burn DVD without any problem.

I mark this bug as fixed. Feel free to reopen it if needed.