nautilus-cd-burner does not autodetect maximum write speed

Bug #14464 reported by asubedi on 2005-03-23
14
Affects Status Importance Assigned to Milestone
nautilus-cd-burner
Fix Released
Wishlist
nautilus-cd-burner (Ubuntu)
Wishlist
Sebastien Bacher

Bug Description

When choosing maximum possible for write speed while tyring to burn a data cd,
nautilus ejects cd saying that my system is too slow for writing at that speed.
I can burn cd fine if I choose 8x speed. There wasn't this issue in Warty.

I'm using Hoary preview release with daily updates. My laptop is Sony PCG-GRX500.

http://bugzilla.gnome.org/show_bug.cgi?id=157899: http://bugzilla.gnome.org/show_bug.cgi?id=157899

Sebastien Bacher (seb128) wrote :

*** Bug 14465 has been marked as a duplicate of this bug. ***

Sebastien Bacher (seb128) wrote :

can you set the gconf key "/apps/nautilus-cd-burner/debug" to get a log of the bug ?
- gnome-session remove nautilus
- nautilus
... get the bug

Do you know how to rebuild a package ? There is a ./list_cddrives in the ncb
build directory to run which is useful to debug such issues.

asubedi (asubedi) wrote :

I set the debug gconf key and tried to burn again at max speed. Following is the
Disc writing error details:

cdrecord: fifo was 0 times empty and 1 times full, min fill was 0%.
cdrecord: fifo had 64 puts and 0 gets.
cdrecord: Try to use 'driveropts=burnfree'.
cdrecord: Max DMA data speed is 11.
cdrecord: DMA speed too slow (OK for 11x). Cannot write at speed 16x.
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
SCSI buffer size: 64512
cdrecord: Warning: using unofficial version of libscg (ubuntu-0.8ubuntu1
'@(#)scsitransp.c 1.91 04/06/17 Copyright 1988,1995,2000-2004 J. Schilling').
Linux sg driver version: 3.5.27
Warning: Open by 'devname' is unintentional and not supported.
scsibus: -2 target: -2 lun: -2
devname: '/dev/hdc'
scsidev: '/dev/hdc'
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: Warning: Running on Linux-2.6.10-5-686
cdrecord: Continuing in 5 seconds...
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
cdrecord: Asuming -tao mode.
cdrecord: No write mode specified.

I don't know how to rebuild a package.

Sebastien Bacher (seb128) wrote :

I've opened a bug upstream about it:
http://bugzilla.gnome.org/show_bug.cgi?id=171487

Sebastien Bacher (seb128) wrote :

updating according to the upstream changes

Sebastien Bacher (seb128) wrote :

fixed upstream, it uses hal to get the speed of the drive now

Changed in nautilus-cd-burner:
status: Unconfirmed → Fix Released
Sebastien Bacher (seb128) wrote :

This upload uses hal to get the speed of the drive:

 nautilus-cd-burner (2.13.90-0ubuntu1) dapper; urgency=low
 .
   * New upstream version:
     nautilus-cd-burner:
     - Display only the supported write speeds (Ubuntu: #14464)
     - Use gnome-vfs to glob and tilde expand the source iso and cue files
     - Add eject button to write finished dialog
     - Add eject button to media request dialog
     - Use disc label as default label for writing ISO
     libnautilus-burn:
     - New API nautilus_burn_drive_get_write_speeds
     - New HAL only API nautilus_burn_drive_get_media_label
     - Use HAL volume.disc.capacity if available
     - Use gnome-mount if available
     - Get media type information even if the volume is mounted
   * debian/rules:
     - updated the shlibs version

I'm closing the bug as fixed, feel free to reopen if you still have an issue with it

Changed in nautilus-cd-burner:
status: Unconfirmed → Fix Released
Changed in nautilus-cd-burner:
importance: Unknown → Wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.