available speeds are wrong

Thanks for your bug. Could you get a "lshal" log? What "storage.cdrom.write_speeds" is listed for your CD drive?

I have the same issue with wrong speeds on a DVD Burner. Additionally, I receive an error message : error while writing to disc, try a lower speed at the end of the burn process - regardless of what speed the CD was burned on. Strangely enough, the CD is actually burned properly.

lshal output:

jchildrose@workstation1:~$ lshal | grep storage.cdrom
  storage.cdrom.write_speed = 0 (0x0) (int)
  storage.cdrom.read_speed = 7056 (0x1b90) (int)
  storage.cdrom.support_media_changed = true (bool)
  storage.cdrom.hddvdrw = false (bool)
  storage.cdrom.hddvdr = false (bool)
  storage.cdrom.hddvd = false (bool)
  storage.cdrom.bdre = false (bool)
  storage.cdrom.bdr = false (bool)
  storage.cdrom.bd = false (bool)
  storage.cdrom.dvdplusrdl = false (bool)
  storage.cdrom.dvdplusrw = false (bool)
  storage.cdrom.dvdplusr = false (bool)
  storage.cdrom.dvdram = false (bool)
  storage.cdrom.dvdrw = false (bool)
  storage.cdrom.dvdr = false (bool)
  storage.cdrom.dvd = true (bool)
  storage.cdrom.cdrw = false (bool)
  storage.cdrom.cdr = false (bool)
  info.capabilities = {'storage', 'block', 'storage.cdrom'} (string list)
  storage.cdrom.write_speeds = {'5645', '4234', '2822', '2117'} (string list)
  storage.cdrom.write_speed = 5645 (0x160d) (int)
  storage.cdrom.read_speed = 8467 (0x2113) (int)
  storage.cdrom.support_media_changed = true (bool)
  storage.cdrom.hddvdrw = false (bool)
  storage.cdrom.hddvdr = false (bool)
  storage.cdrom.hddvd = false (bool)
  storage.cdrom.bdre = false (bool)
  storage.cdrom.bdr = false (bool)
  storage.cdrom.bd = false (bool)
  storage.cdrom.dvdplusrdl = true (bool)
  storage.cdrom.dvdplusrw = true (bool)
  storage.cdrom.dvdplusr = true (bool)
  storage.cdrom.dvdram = false (bool)
  storage.cdrom.dvdrw = false (bool)
  storage.cdrom.dvdr = true (bool)
  storage.cdrom.dvd = true (bool)
  storage.cdrom.cdrw = true (bool)
  storage.cdrom.cdr = true (bool)
  info.capabilities = {'storage', 'block', 'storage.cdrom'} (string list)

I have the same error messsage "error while writing to disc, try a lower speed" as Joe Childrose. The CD seems to be actually burned properly here too.

lshal output:

nous@ubuntu:~$ lshal | grep storage.cdrom
  storage.cdrom.write_speeds = {'8467', '7056', '5645', '4234', '2822', '2117'} (string list)
  storage.cdrom.write_speed = 8467 (0x2113) (int)
  storage.cdrom.read_speed = 8467 (0x2113) (int)
  storage.cdrom.support_media_changed = true (bool)
  storage.cdrom.hddvdrw = false (bool)
  storage.cdrom.hddvdr = false (bool)
  storage.cdrom.hddvd = false (bool)
  storage.cdrom.bdre = false (bool)
  storage.cdrom.bdr = false (bool)
  storage.cdrom.bd = false (bool)
  storage.cdrom.dvdplusrdl = true (bool)
  storage.cdrom.dvdplusrw = true (bool)
  storage.cdrom.dvdplusr = true (bool)
  storage.cdrom.dvdram = false (bool)
  storage.cdrom.dvdrw = false (bool)
  storage.cdrom.dvdr = true (bool)
  storage.cdrom.dvd = true (bool)
  storage.cdrom.cdrw = true (bool)
  storage.cdrom.cdr = true (bool)
  info.capabilities = {'storage', 'block', 'storage.cdrom'} (string list)
nous@ubuntu:~$

nous@ubuntu:~$ gconftool -R /apps/nautilus-cd-burner
 burnproof = true
 temp_iso_dir =
 debug = true
 overburn = false
 default_speed = 0
 /apps/nautilus-cd-burner/ubuntu:
  last_device = /dev/hdc
nous@ubuntu:~$

This issue also exists with nautilus-cd-burner 2.16.1 on Fedora Core 6 as well. I tested burning CDs and/or DVDs with cdrecord, K3B, and Gnomebaker, all of which burn the media without issue.

If there is any more information needed, let me know and I will try to get it for you.

do you still get the bug?

Sebastien,

Absolutely. The problem only exists in nautilus-cd-burner in Edgy - all
other CD/DVD burning applications work exactly as expected. As I said in the
bug report - the burn is still good, but the error message persists and the
available speeds are wrong.

I haven't tested it with Feisty Beta yet, as I still haven't gotten around
to installing it.

On 4/16/07, Sebastien Bacher <email address hidden> wrote:
>
> do you still get the bug?
>
> --
> available speeds are wrong
> https://bugs.launchpad.net/bugs/67034
> You received this bug notification because you are a direct subscriber
> of the bug.
>

could you activate /apps/nautilus-cd-burner/debug in gconf-editor, run nautilus-cd-burner on a command line and copy the debug log to a comment?

Here's the output:

jchildrose@workstation1:~$ nautilus-cd-burner --source-iso=
ubuntu-6.06.1-desktop-i386.iso
launching command: cdrecord fs=16m dev=/dev/hdd -dao driveropts=burnfree -v
-data -nopad /home/jchildrose/ubuntu-6.06.1-desktop-i386.iso
cdrecord stderr: cdrecord: Warning: Running on Linux-2.6.17-11-generic
cdrecord stderr: cdrecord: There are unsettled issues with Linux-2.5 and
newer.
cdrecord stderr: cdrecord: If you have unexpected problems, please try
Linux-2.4 or Solaris.
cdrecord stderr: scsidev: '/dev/hdd'
cdrecord stderr: devname: '/dev/hdd'
cdrecord stderr: scsibus: -2 target: -2 lun: -2
cdrecord stderr: Warning: Open by 'devname' is unintentional and not
supported.
cdrecord stderr: Linux sg driver version: 3.5.27
cdrecord stderr: Error: Cannot gain SYS_RAWIO capability.Is cdrecord
installed SUID root?
cdrecord stderr: : Operation not permitted
cdrecord stderr: cdrecord: Warning: using inofficial version of libscg (
debian-0.8debian2 '@(#)scsitransp.c 1.91 04/06/17 Copyright
1988,1995,2000-2004 J. Schilling').
cdrecord stderr: SCSI buffer size: 64512
cdrecord stderr: cdrecord: This version of cdrecord does not include
DVD-R/DVD-RW support code.
cdrecord stderr: cdrecord: See /usr/share/doc/cdrecord/README.DVD.Debian for
details on DVD support.
cdrecord stdout: Cdrecord-Clone 2.01.01a03 (i686-pc-linux-gnu) Copyright (C)
1995-2005 Joerg Schilling
cdrecord stdout: NOTE: this version of cdrecord is an inofficial (modified)
release of cdrecord
cdrecord stdout: and thus may have bugs that are not present in the
original version.
cdrecord stdout: Please send bug reports and support requests to <
<email address hidden>>.
cdrecord stdout: The original author should not be bothered with
problems of this version.
cdrecord stdout:
cdrecord stdout: TOC Type: 1 = CD-ROM
cdrecord stdout: Using libscg version 'debian-0.8debian2'.
cdrecord stdout: Driveropts: 'burnfree'
cdrecord stdout: atapi: 1
cdrecord stdout: Device type : Removable CD-ROM
cdrecord stdout: Version : 0
cdrecord stdout: Response Format: 3
cdrecord stdout: Capabilities :
cdrecord stdout: Vendor_info : 'ATAPI '
cdrecord stdout: Identifikation : 'DVD DD 8X16X8X16'
cdrecord stdout: Revision : 'GSOB'
cdrecord stdout: Device seems to be: Generic mmc2 DVD-R/DVD-RW.
cdrecord stdout: Current: 0x0009
cdrecord stdout: Profile: 0x002B
cdrecord stdout: Profile: 0x001B
cdrecord stdout: Profile: 0x001A
cdrecord stdout: Profile: 0x0016
cdrecord stdout: Profile: 0x0015
cdrecord stdout: Profile: 0x0014
cdrecord stdout: Profile: 0x0013
cdrecord stdout: Profile: 0x0011
cdrecord stdout: Profile: 0x0010
cdrecord stdout: Profile: 0x000A
cdrecord stdout: Profile: 0x0009 (current)
cdrecord stdout: Profile: 0x0008
cdrecord stdout: Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
cdrecord stdout: Driver flags : MMC-3 SWABAUDIO BURNFREE
cdrecord stdout: Supported modes: TAO PACKET SAO SAO/R96R RAW/R16 RAW/R96R
cdrecord stdout: Drive buf size : 1073152 = 1048 KB
cdrecord stdout: FIFO size : 16777216 = 16384 KB
cdrecord stderr: Error: Cannot gain SYS_RAWIO capability.Is cdrecord
installed SUID root?
cdrecord stderr: : Operation not permi...

Same error in feisty.

nautilus-cd-burner uses the storage.cdrom.write_speeds list and assume 1x=150, looks like an hal or linux bug then

If it is a hal issue, should this bug be marked as a duplicate of Bug
#93328?

I've marked the other bug as duplicate

Some error in Gutsy, with different burner.

Since Gutsy I got this error message. Though for me the burned CDs are completely OK.

Never had this error before, using a PHLIPS DVD+RW416.

My first thought was, that it would be related to wodim or nautilus-cd-burner. But it is definetely the package libhal1. Because write speeds since Gutsy are shown completely incorrect and weird. I can select from 9x, 13x etc.

I now tried this on my laptop with a TSSTCorp CD/DVD-Writer. There I get no error and I guess write speeds are estimate correctly. For example, when using a CDRW which only allows 4x CD writing speed (which is the minimum) I can't select any speed. Though in Feisty the option field said "4x", here it is just greyed out.
But altogether with this hardware combination it works fine. No error message. So some drives are not correctly supported by hal since gutsy (see my post above).

Please also see this bug: https://bugs.launchpad.net/ubuntu/+source/nautilus-cd-burner/+bug/86431
It is the same problem but connected to the package "nautilus-cd-burner". Though the error must be in the hal package, I guess. Maybe someone can connect these different reports.

Can someone please set the importance of this bug to "medium" or "high"?
This affects the standard burning application of ubuntu and is a major and everyday desktop task. As said before, it's not on all CD/DVD-Writers. But on most or many.

(Sorry for multiple posts, just getting used to launchpad ;-) )

I still have that issue, it survived three ubuntu versions now.

lshal |grep "storage.cdrom"

  info.capabilities = {'storage', 'block', 'storage.cdrom'} (string list)
  storage.cdrom.bd = false (bool)
  storage.cdrom.bdr = false (bool)
  storage.cdrom.bdre = false (bool)
  storage.cdrom.cdr = false (bool)
  storage.cdrom.cdrw = false (bool)
  storage.cdrom.dvd = true (bool)
  storage.cdrom.dvdplusr = false (bool)
  storage.cdrom.dvdplusrdl = false (bool)
  storage.cdrom.dvdplusrw = false (bool)
  storage.cdrom.dvdplusrwdl = false (bool)
  storage.cdrom.dvdr = false (bool)
  storage.cdrom.dvdram = false (bool)
  storage.cdrom.dvdrw = false (bool)
  storage.cdrom.hddvd = false (bool)
  storage.cdrom.hddvdr = false (bool)
  storage.cdrom.hddvdrw = false (bool)
  storage.cdrom.mo = false (bool)
  storage.cdrom.mrw = true (bool)
  storage.cdrom.mrw_w = true (bool)
  storage.cdrom.read_speed = 8448 (0x2100) (int)
  storage.cdrom.support_media_changed = true (bool)
  storage.cdrom.support_multisession = true (bool)
  storage.cdrom.write_speed = 0 (0x0) (int)
  storage.cdrom.write_speeds = {} (string list)
  info.capabilities = {'storage', 'block', 'storage.cdrom'} (string list)
  storage.cdrom.bd = false (bool)
  storage.cdrom.bdr = false (bool)
  storage.cdrom.bdre = false (bool)
  storage.cdrom.cdr = true (bool)
  storage.cdrom.cdrw = true (bool)
  storage.cdrom.dvd = false (bool)
  storage.cdrom.dvdplusr = false (bool)
  storage.cdrom.dvdplusrdl = false (bool)
  storage.cdrom.dvdplusrw = false (bool)
  storage.cdrom.dvdplusrwdl = false (bool)
  storage.cdrom.dvdr = false (bool)
  storage.cdrom.dvdram = false (bool)
  storage.cdrom.dvdrw = false (bool)
  storage.cdrom.hddvd = false (bool)
  storage.cdrom.hddvdr = false (bool)
  storage.cdrom.hddvdrw = false (bool)
  storage.cdrom.mo = false (bool)
  storage.cdrom.mrw = true (bool)
  storage.cdrom.mrw_w = true (bool)
  storage.cdrom.read_speed = 7056 (0x1b90) (int)
  storage.cdrom.support_media_changed = true (bool)
  storage.cdrom.support_multisession = true (bool)
  storage.cdrom.write_speed = 8467 (0x2113) (int)
  storage.cdrom.write_speeds = {'8467', '7056', '5645', '4234', '3528', '2822', '1411', '706'} (string list)

Below are the lshal data from a ubuntu 6.06 live-cd on the same system.
The write speed values are pretty much the same. What makes you believe this is a bug in hal?

 storage.cdrom.write_speeds = {'8467', '7056', '5645', '4234', '3528',
'2822', '1411', '706'} (string list)
  storage.cdrom.write_speed = 8467 (0x2113) (int)
  storage.cdrom.read_speed = 7056 (0x1b90) (int)
  storage.cdrom.support_media_changed = true (bool)
  storage.cdrom.hddvdrw = false (bool)
  storage.cdrom.hddvdr = false (bool)
  storage.cdrom.hddvd = false (bool)
  storage.cdrom.bdre = false (bool)
  storage.cdrom.bdr = false (bool)
  storage.cdrom.bd = false (bool)
  storage.cdrom.dvdplusrdl = false (bool)
  storage.cdrom.dvdplusrw = false (bool)
  storage.cdrom.dvdplusr = false (bool)
  storage.cdrom.dvdram = false (bool)
  storage.cdrom.dvdrw = false (bool)
  storage.cdrom.dvdr = false (bool)
  storage.cdrom.dvd = false (bool)
  storage.cdrom.cdrw = true (bool)
  storage.cdrom.cdr = true (bool)
  info.capabilities = {'storage', 'block', 'storage.cdrom'} (string
list)
  storage.cdrom.write_speed = 0 (0x0) (int)
  storage.cdrom.read_speed = 8448 (0x2100) (int)
  storage.cdrom.support_media_changed = true (bool)
  storage.cdrom.hddvdrw = false (bool)
  storage.cdrom.hddvdr = false (bool)
  storage.cdrom.hddvd = false (bool)
  storage.cdrom.bdre = false (bool)
  storage.cdrom.bdr = false (bool)
  storage.cdrom.bd = false (bool)
  storage.cdrom.dvdplusrdl = false (bool)
  storage.cdrom.dvdplusrw = false (bool)
  storage.cdrom.dvdplusr = false (bool)
  storage.cdrom.dvdram = false (bool)
  storage.cdrom.dvdrw = false (bool)
  storage.cdrom.dvdr = false (bool)
  storage.cdrom.dvd = true (bool)
  storage.cdrom.cdrw = false (bool)
  storage.cdrom.cdr = false (bool)
  info.capabilities = {'storage', 'block', 'storage.cdrom'} (string
list)

think also this is a bug in hal.
Let's get this fix till hardy.

By the way, k3b shows correct write speeds while nautilus goes wrong.

Is there any progress on the bug. Can i help testing or something?

1) I have the similar problem with nautilus-cd-burner and Brasero;
2) k3b is working fine!
3) I could not save files to flash memory card in my SE 750i, writing process was always interrupted ; Just wonder if there is any connection between CD writing errors and errors writing to flash memory card

Similar/Same bug in hardy. No error message, but speeds are still incorrect.

Yeah, it's present.

#25 marius, your bug is not related with this one. But i owned a SE750i as well, and i know your problem too. You should not use the USB Cabel. Instead use a bluetooth-dongle (better, faster 2.0 not 1.2!), or a card-adapter (and install the package gnome-vfs-obexftp). I experienced corrupted data using the usb-cabel.

I dont think the bug is in hal, i think it is in libnautilus-burn4.

according to what /usr/share/doc/libnautilus-burn4/README tells, i attach my output of the list_cddrives command

the lshal logs attach to the bug show wrong speeds, don't reassign bugs without a reason

After looking in the source i found that hal's values are simply devided by 150 to get the speed values. You mentioned that in #13. Sorry about that Sebastien.

Thank you for posting this bug.

Is this an issue in Maverick?

[Expired for hal (Ubuntu) because there has been no activity for 60 days.]