cd/dvd burning does not work in gutsy and hardy(latest update)

[pliz]

I have tried it on three different machines:

laptops:
1. MacBook Pro (santa rosa)
    blank cd's and dvd's just are not recognized and when trying to burn an iso image (as an example) it keeps asking to insert a cd
    all other cd's are not automounted
    this happens always (all_ide_generic=1 as kernel parameter does not help)

2. Velocity Micro Neomagix Ultra L-80
    same as above
    this one worked in feisty though

desktop:
    it reads cds and dvds but not always surprisingly
    never burns

This all happens both on gutsy and hardy (I have upgraded desktop to see if it will help)
So for about 6 months I am unable to burn CDs and DVDs from Linux. I was too busy and was kind of hoping that the bug will be resolved but nothing was done and it seems will not be done even at hardy's release. I am attaching lshw outputs for all three machines I've mentioned. Also some other files that might be relevant. I hope someone can instruct me in providing additional relevant information that might help fixing this bug.

Thanks!

[pliz (pliz)]

Here is the log of what Brasero gives me on Hardy Heron when trying to burn a disk.

[Jan Rüegg (rggjan)]

For me it works (Macbooks Pro rev 3), but only in console using cdrecord (also blanking works when using cd-rw's).
When I use cdrecord, I have to specify "--force" or it won't burn anything and stop with an error.

[pliz (pliz)]

Thanks for the advice. So it is a severe bug then, at least for Macbook Pro rev 3. Or if it is a feature (console only burning), then it should be described in the documentation, which I do not believe anyway.
I am only wondering why is the problem ignored by developers. it has been 6 months since was Gutsy released and the issue is not fixed in Hardy. Keeps me wondering about the whole bug reporting business.

[LindseyD. (ai279)]

Whatever the bug is, it's certainly not limited to Macbook Pro. I have a HP Pavilion 753n (a desktop PC) and I can't burn anything either.

[pliz (pliz)]

You're right! I am mentioning two other PCs here and also, please, see Bug 200337 which is surprisingly "Low Priority"

My solution was to go back to Feisty dual boot and burn there

[Jan Rüegg (rggjan)]

Still the same problem, here. Brasero and any other gui application won't work, everything exept a "cdrecord --force" fails...

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Pedro Villavicencio (pedro)]

could you please try to see if this is still an issue with Intrepid? thanks.

[Jan Rüegg (rggjan)]

Does not seem to work... even though I think I could erase a cd-rw with brasero, I'm not able to burn anything.

Also, trying with cdrecord, I get

jan@MacBuntu:~$ cdrecord blank=fast --verbose
TOC Type: 1 = CD-ROM
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.Device was not specified. Trying to find an appropriate drive...
Detected CD-R drive: /dev/cdrw
Using /dev/cdrom of unknown capabilities
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.8
Driveropts: 'burnfree'
SCSI buffer size: 64512
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'MATSHITA'
Identification : 'DVD-R UJ-857D '
Revision : 'KCVB'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x000A (CD-RW)
Profile: 0x002B (DVD+R/DL)
Profile: 0x001B (DVD+R)
Profile: 0x001A (DVD+RW)
Profile: 0x0013 (DVD-RW restricted overwrite)
Profile: 0x0014 (DVD-RW sequential recording)
Profile: 0x0011 (DVD-R sequential recording)
Profile: 0x0010 (DVD-ROM)
Profile: 0x000A (CD-RW) (current)
Profile: 0x0009 (CD-R)
Profile: 0x0008 (CD-ROM)
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO
Drive buf size : 1310720 = 1280 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 1
  Reference speed: 0
  Is not unrestricted
  Is erasable
  Disk sub type: Ultra High speed Rewritable media (2)
  ATIP start of lead in: -11076 (97:34/24)
  ATIP start of lead out: 359849 (79:59/74)
  1T speed low: 16 1T speed high: 16
  2T speed low: 8 2T speed high: 24
  power mult factor: 4 5
  recommended erase/write power: 1
  A1 values: 66 4A 99
  A2 values: 38 80 00
  A3 values: 04 C4 A0
Disk type: Phase change
Manuf. index: 11
Manufacturer: Mitsubishi Chemical Corporation
Speed set to 1764 KB/s
wodim: Probably trying to use ultra high speed medium on improper writer.

[Sebastien Bacher (seb128)]

is the issue specific to this application or does using command line tools give similar issue?

[LindseyD. (ai279)]

Sebastien, as I understand it, the bug is in wodim, which Debian-based distributions use instead of cdrecord. I suspect this is a duplicate of bug 149076 and if I could figure out Launchpad, I'd report it as such.

[Jan Rüegg (rggjan)]

It seems to work now, I just burned a cd - r without problems with brasero on Ubuntu Intrepid....

For me, this can be marked as completed.

[Ian Weisser (ian-weisser)]

Does anyone else still have this problem in Intrepid?

[Pedro Villavicencio (pedro)]

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.