CDs won't burn in GUI apps anymore

userlander · 2008-12-13 19:15:15

Suddenly CD burning is failing in all my gui apps. It seems to work on the command line, but it fails in Brasero, K3B, NeroLinux, and Imgburn can't even see my writer anymore.

My user is in the optical and the storage groups.

The permissions of the devices are as follows:

ll /dev |grep sr
lrwxrwxrwx 1 root root            17 2008-12-13 10:47 cdrom -> /dev/cd/cdrosr0
lrwxrwxrwx 1 root root            17 2008-12-13 10:47 cdrom0 -> /dev/cd/cdrom-sr0
lrwxrwxrwx 1 root root            16 2008-12-13 10:47 cdrw -> /dev/cd/cdrw-sr0
lrwxrwxrwx 1 root root            16 2008-12-13 10:47 cdrw0 -> /dev/cd/cdrw-sr0
srw-rw-rw- 1 root root             0 2008-12-13 10:47 log=
lrwxrwxrwx 1 root root             3 2008-12-13 10:47 scd0 -> sr0
brw-rw---- 1 root optical    11,   0 2008-12-13 10:47 sr0

The error message in K3B says "cdrecord has no permission to open the device."

The error messages running Brasero from the command prompt say:

** (brasero:6576): WARNING **: Failed to inhibit the system from suspending: The name org.freedesktop.PowerManagement was not provided by any .service files
(brasero:6576): GLib-GIO-CRITICAL **: g_volume_can_eject: assertion `G_IS_VOLUME (volume)' failed
(brasero:6576): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** (brasero:6576): WARNING **: Failed to restore the system power manager: The name org.freedesktop.PowerManagement was not provided by any .service files

With those "freedesktop.org" messages I wondered if it might have something to do with hal or policykit. Otherwise, I can't figure out what's wrong. wodim on the command line both burns and erases CDs.

I posted a bug report earlier when I thought it was just a brasero bug, but now I am not sure what's going on and am posting here in case it is a configuration problem.

thank you

p.s. I tried downgrading to the previous kernel but that didn't work.

Last edited by userlander (2008-12-13 19:21:56)

peart · 2008-12-13 19:53:25

I saw your other thread and you are most likely right about PolicyKit being the culprit. The quick and painless solution is to revert to hal from [extra]. Otherwise, you'll have to set up a policy somewhere in /etc/PolicyKit that allows your regular user to access the optical drive.

http://hal.freedesktop.org/docs/PolicyK … onf.5.html

userlander · 2008-12-13 20:05:26

most likely policykit in conjunction with the kernel, possibly. I just downgraded to kernel 2.6.26.5-1 and nerolinux burned the iso, brasero erased the disc, and as I'm writing brasero just finished burning the iso successfully.

I had the failures burning with the current kernel 2.6.27.8-1 and the one before that (2.6.27.7-1).

So now I guess either reinstall the latest kernel and mess with hal, or else keep trying kernels working backward from 2.6.27.7-1 to see at which kernel the problem shows up. Since at least it's working with a different kernel, I think I would rather do that, what do you think?

n/m - I misread what you wrote. IOW, this is a new "feature" I take it. So I guess it's better to go with the current kernel and downgrade hal until I figure out how to write the rule I would need. no real mention of any of this in the wiki....

Last edited by userlander (2008-12-13 20:34:04)

userlander · 2008-12-13 20:58:03

Okay, very strange! Downgrading hal and hal-info with the current kernel seems to have fixed the problem with K3B and nero, but now Brasero can't even see a disc in the drive! And imgburn still can't see the device. Really annoying since I use Brasero the most and also imgburn for testing media.

Now what? Just go back to an earlier kernel? :-/

-------------------------------------------
just so I remember the versions:

[2008-12-13 15:39] upgraded kernel26 (2.6.26.5-1 -> 2.6.27.8-1)
[2008-12-13 15:39] upgraded hal (0.5.11-4 -> 0.5.11-1)
[2008-12-13 15:40] upgraded hal-info (0.20081022-1 -> 0.20080508-1)

Last edited by userlander (2008-12-13 21:00:23)

userlander · 2008-12-13 22:06:34

brasero and imgburn still seem broken. brasero can't see any media in the drive. I added:

to PolicyKit.conf, it didn't help (edit: with my own user in "username" - also logged out and back on).

Downgrading to the earlier kernel that worked before now doesn't work anymore.

Could the drive be going bad?

Last edited by userlander (2008-12-13 22:07:34)

userlander · 2008-12-14 14:53:07

No one? K3B and Nerolinux work, brasero can't see the disc and says "no available medium." imgburn used to see the drive, now it can't anymore. Why would that be?

userlander · 2008-12-26 20:50:41

can anyone help with this? All GUI apps are failing to burn now. The disc erases and burns perfectly in PCLinuxOS using Brasero on the same hardware. Last failure of K3B burning as root to test permissions said this:

System
-----------------------
K3b Version: 1.0.5

KDE Version: 3.5.10
QT Version:  3.3.8
Kernel:      2.6.27-ARCH
Devices
-----------------------
LITE-ON LTR-40125S ZS0J (/dev/sr0, ) [CD-R, CD-RW, CD-ROM] [CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R]

K3bIsoImager
-----------------------
mkisofs print size result: 54517 (111650816 bytes)
Pipe throughput: 13393664 bytes read, 13389312 bytes written.

Used versions
-----------------------
mkisofs: 1.1.9
cdrecord: 1.1.9

cdrecord
-----------------------
scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.9
SCSI buffer size: 64512
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
TOC Type: 3 = CD-ROM XA mode 2
Driveropts: 'burnfree'
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   : 
Vendor_info    : 'LITE-ON '
Identification : 'LTR-40125S      '
Revision       : 'ZS0J'
Device seems to be: Generic mmc CD-RW.
Current: 0x000A (CD-RW)
Profile: 0x000A (CD-RW) (current)
Profile: 0x0009 (CD-R) 
Profile: 0x0008 (CD-ROM) 
Profile: 0x0002 (Removable disk) (current)
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/R16 RAW/R96P RAW/R96R
Drive buf size : 1422080 = 1388 KB
FIFO size      : 4194304 = 4096 KB
Track 01: data   106 MB        
Total size:      122 MB (12:06.92) = 54519 sectors
Lout start:      122 MB (12:08/69) = 54519 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 5
  Reference speed: 2
  Is not unrestricted
  Is erasable
  ATIP start of lead in:  -11635 (97:26/65)
  ATIP start of lead out: 359849 (79:59/74)
  1T speed low:  0 (reserved val  0) 1T speed high:  4
  2T speed low:  8 2T speed high:  0 (reserved val 10)
  power mult factor: 4 6
  recommended erase/write power: 3
  A1 values: 02 4C B0
  A2 values: 4A C8 36
Disk type:    Phase change
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 305330
Forcespeed is OFF.
Starting to write CD/DVD at speed   4.0 in real TAO mode for multi session.
Last chance to quit, starting real write in    2 seconds.
Speed set to 704 KB/s
   1 seconds.
   0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0
Track 01:    0 of  106 MB written.
Track 01:    1 of  106 MB written (fifo 100%) [buf 100%]   4.8x.
Track 01:    2 of  106 MB written (fifo 100%) [buf 100%]   4.1x.
Track 01:    3 of  106 MB written (fifo 100%) [buf 100%]   4.2x.
Track 01:    4 of  106 MB written (fifo 100%) [buf  99%]   4.1x.
Track 01:    5 of  106 MB written (fifo 100%) [buf 100%]   4.2x.
Track 01:    6 of  106 MB written (fifo 100%) [buf 100%]   4.1x.
Track 01:    7 of  106 MB written (fifo 100%) [buf 100%]   4.2x.
Track 01:    8 of  106 MB written (fifo 100%) [buf 100%]   4.1x.
Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB:  2A 00 00 00 11 8F 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00
Sense Key: 0x0 No Additional Sense, Segment 11
Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 65.417s timeout 40s
/usr/bin/wodim: A write error occured.
/usr/bin/wodim: Please properly read the error message above.
write track data: error after 9205760 bytes
Writing  time:   93.940s
Average write speed   8.4x.
Min drive buffer fill was 99%
Fixating...
Fixating time:   77.570s
BURN-Free was never needed.
/usr/bin/wodim: fifo had 209 puts and 146 gets.
/usr/bin/wodim: fifo was 0 times empty and 133 times full, min fill was 89%.

cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=4 -tao driveropts=burnfree -eject -overburn -multi -xa -tsize=54517s - 

mkisofs
-----------------------
54517
I: -input-charset not specified, using utf-8 (detected in locale settings)
  0.94% done, estimate finish Fri Dec 26 15:37:07 2008
  1.85% done, estimate finish Fri Dec 26 15:37:07 2008
  2.76% done, estimate finish Fri Dec 26 15:37:07 2008
  3.70% done, estimate finish Fri Dec 26 15:37:07 2008
  4.61% done, estimate finish Fri Dec 26 15:40:22 2008
  5.52% done, estimate finish Fri Dec 26 15:40:44 2008
  6.43% done, estimate finish Fri Dec 26 15:40:29 2008
  7.36% done, estimate finish Fri Dec 26 15:40:30 2008
  8.27% done, estimate finish Fri Dec 26 15:40:32 2008
  9.18% done, estimate finish Fri Dec 26 15:40:22 2008
 10.09% done, estimate finish Fri Dec 26 15:40:25 2008
 11.03% done, estimate finish Fri Dec 26 15:40:26 2008
 11.94% done, estimate finish Fri Dec 26 15:40:19 2008

mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid CDROM -volset  -appid K3B THE CD KREATOR (C) 1998-2006 SEBASTIAN TRUEG AND THE K3B TEAM -publisher  -preparer  -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-root/k3bwfbELa.tmp -rational-rock -hide-list /tmp/kde-root/k3betVJVb.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-root/k3bj02ssa.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-root/k3bXzwDXa.tmp 

mkisofs command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -volid CDROM -volset  -appid K3B THE CD KREATOR (C) 1998-2006 SEBASTIAN TRUEG AND THE K3B TEAM -publisher  -preparer  -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-root/k3bvsF0Qb.tmp -rational-rock -hide-list /tmp/kde-root/k3bt82Ksc.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-root/k3bxbzMaa.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-root/k3bElHRmc.tmp

Now cdrecord (wodim) is failing, too. I'd think the drive was failing, but why does it work perfectly in PCLinux? I bought a new drive, but if Arch is destroying the drive, I don't know if I want to test it yet until I can find out what's wrong.

 $ wodim -v dev=/dev/cdrw test.avi 
wodim: No write mode specified.
wodim: Asuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
TOC Type: 1 = CD-ROM
wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/cdrw'
devname: '/dev/cdrw'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.9
SCSI buffer size: 64512
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   : 
Vendor_info    : 'LITE-ON '
Identification : 'LTR-40125S      '
Revision       : 'ZS0J'
Device seems to be: Generic mmc CD-RW.
Current: 0x000A (CD-RW)
Profile: 0x000A (CD-RW) (current)
Profile: 0x0009 (CD-R) 
Profile: 0x0008 (CD-ROM) 
Profile: 0x0002 (Removable disk) (current)
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/R16 RAW/R96P RAW/R96R
Drive buf size : 1422080 = 1388 KB
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
FIFO size      : 4194304 = 4096 KB
Track 01: data    44 MB        
Total size:       51 MB (05:03.90) = 22793 sectors
Lout start:       51 MB (05:05/68) = 22793 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 5
  Reference speed: 2
  Is not unrestricted
  Is erasable
  ATIP start of lead in:  -11635 (97:26/65)
  ATIP start of lead out: 359849 (79:59/74)
  1T speed low:  0 (reserved val  0) 1T speed high:  4
  2T speed low:  8 2T speed high:  0 (reserved val 10)
  power mult factor: 4 6
  recommended erase/write power: 3
  A1 values: 02 4C B0
  A2 values: 4A C8 36
Disk type:    Phase change
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 337056
Forcespeed is OFF.
Speed set to 704 KB/s
Starting to write CD/DVD at speed   4.0 in real TAO mode for single session.
Last chance to quit, starting real write in    0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0
Track 01:    9 of   44 MB written (fifo 100%) [buf 100%]   4.2x.Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB:  2A 00 00 00 12 68 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00
Sense Key: 0x0 No Additional Sense, Segment 11
Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 65.441s timeout 40s

write track data: error after 9650176 bytes
wodim: A write error occured.
wodim: Please properly read the error message above.
Writing  time:   87.604s
Average write speed   3.5x.
Min drive buffer fill was 99%
Fixating...
Fixating time:   77.389s
BURN-Free was never needed.
wodim: fifo had 216 puts and 153 gets.
wodim: fifo was 0 times empty and 139 times full, min fill was 85%.

K3B says cdrecord has no permissions to open the device. what permissions does it need? user is already in optical, storage, and burning groups. And it fails as root anyway. something is seriously wrong. Is this what permissions in /dev/ are supposed to look like? user is in optical group, so I don't get it.

$ ll |grep cd
drwxr-xr-x 2 root root           0 2008-12-26 16:26 cd/
lrwxrwxrwx 1 root root          21 2008-12-26 16:26 cdrom -> /dev/cd/cdrom-1:0:0:0
lrwxrwxrwx 1 root root          21 2008-12-26 16:26 cdrom0 -> /dev/cd/cdrom-1:0:0:0
lrwxrwxrwx 1 root root          20 2008-12-26 16:26 cdrw -> /dev/cd/cdrw-1:0:0:0
lrwxrwxrwx 1 root root          20 2008-12-26 16:26 cdrw0 -> /dev/cd/cdrw-1:0:0:0
lrwxrwxrwx 1 root root           3 2008-12-26 16:26 scd0 -> sr0

$ ll |grep sr
srw-rw-rw- 1 root root           0 2008-12-26 16:26 log=
lrwxrwxrwx 1 root root           3 2008-12-26 16:26 scd0 -> sr0
brw-rw---- 1 root optical  11,   0 2008-12-26 16:26 sr0

Last edited by userlander (2008-12-26 21:37:15)

userlander · 2008-12-28 16:07:31

downgrading hal/hal-info with .27-8 kernel fixed for K3B, ImgBurn, nerolinux, brasero can't even recognize discs anymore. bug report filed.

Army · 2008-12-28 22:35:36

Same here, but cli apps still seem to work, so I won't downgrade. For external drives I use pmount and I rarely use optical media, so it's acceptable.

skai · 2009-05-10 11:42:41

Up!

Exact same problem here.

GUI won't burn CD/DVD.

I browsed the web for hours to no avail.

Finally tried the ugly : launch Brasero as root just to check : it works fine.
THis confirms it is a rights matter, but damn, where and how ?

My user is in optical group, I even tried the ugly "suid" on wodim : no better result.

Help greatly appreciated here ...

yvonney · 2009-06-18 00:46:59

same problem here: graveman input/output errors. And: growiso begins to scan files then stops.
Running an 'everything latest' ARCH install on intel chipset year old laptop

Last edited by yvonney (2009-06-18 01:34:28)

arnuld · 2009-06-18 14:43:30

I also have the same problem. K3B says this:

No CD/DVD writer found.

K3b did not find an optical writing device in your system. Thus, you will not be able to burn CDs or DVDs.
 However, you can still use other K3b features such as audio track extraction, audio transcoding or 
ISO9660 image creation.


[arnuld@drunken ~]$ dmesg | grep sr
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 0x/52x writer cd/rw xa/form2 cdda tray
sr 3:0:0:0: Attached scsi CD-ROM sr0
sr1: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
sr 3:0:1:0: Attached scsi CD-ROM sr1
sr 3:0:0:0: Attached scsi generic sg1 type 5
sr 3:0:1:0: Attached scsi generic sg2 type 5

[arnuld@drunken ~]$ eject -v /dev/sr1
eject: device name is `/dev/sr1'
eject: expanded name is `/dev/sr1'
eject: `/dev/sr1' is not mounted
eject: `/dev/sr1' is not a mount point
eject: `/dev/sr1' is not a multipartition device
eject: trying to eject `/dev/sr1' using CD-ROM eject command
eject: CD-ROM eject command succeeded

[arnuld@drunken ~]$ eject -tv /dev/sr1
eject: device name is `/dev/sr1'
eject: expanded name is `/dev/sr1'
eject: `/dev/sr1' is not mounted
eject: `/dev/sr1' is not a mount point
eject: closing tray
[arnuld@drunken ~]$

Yesterday I burnt 6 CentOS CDs from CLI with no problem. I have not tried burning a DVD from CLI yet, will try one this weekend. K3B was working fine last month. But I keep on updating the system every week and saw K3B was broken by this 2 weeks ago. Anyway, hope it will be resolved. I think I am fine as long a X runs, I can burn the DVD in urxvt

Last edited by arnuld (2009-06-18 14:43:54)

yvonney · 2009-06-18 17:53:39

My input/output errors and freezing wth gravemen/growiso are a result of file names or something in various folders/files incuding sourcefile stuff. Thinning out the obvious stuff and works fine. Just a rushed and basic comment here. I'm not that skilled at dvd/cd burning as I've not done much of it.

Last edited by yvonney (2009-06-18 17:53:56)

zenlord · 2009-06-19 14:40:59

I don't know if it is relevant, but a while ago someone posted here in the forums about the relation between cdrkit and cdrtools. While there is discussion about the license of cdrtools, it is heavily developped (compared to cdrkit) and available in AUR. I made the switch to cdrtools and have not experienced any problems.

/EDIT: I almost forgot: the main developper of cdrtools claims that cdrkit is full of bugs, that's what made me think this could be related.

Last edited by zenlord (2009-06-19 14:41:58)

skai · 2009-10-04 08:06:48

How do you "switch" from one the the other ?simply installing cdrtools on top of cdrkit could do the trick ? seems ugly.

Remove cdrkit and anything that depends on it first ?

bram85 · 2009-10-04 16:59:09

skai wrote:

How do you "switch" from one the the other ?simply installing cdrtools on top of cdrkit could do the trick ? seems ugly.
Remove cdrkit and anything that depends on it first ?

I seem to remember that cdrtools and cdrkit are conflicting packages, so you have to remove the first one in order to replace it with the other.

amj · 2009-11-26 21:50:45

I also have this problem, but I have found a workaround: disable image creation and burn disk on-the-fly.

Maybe the problem is related with the permissions of cdrecord accessing the image on /tmp/kde-username (with username=my login name).
I use Arch x86_64, and cdrecord is a link to wodim.

lrwxrwxrwx 1 root root 5 abr 12  2009 /usr/bin/cdrecord -> wodim
-rwxr-xr-x 1 root root 393096 abr 12  2009 /usr/bin/wodim

Ideas?

Last edited by amj (2009-11-26 21:56:10)

goran'agar · 2009-11-27 08:50:48

I created my own PKGBUILD for smake (cdrtools own build system), cdrtools (built with smake) and xcdroast (the version in AUR is patched for use with cdrkit).

Everything is working fine so far. I can easily burn DVD on-the-fly.

No cdrkit and friends on my eeepc :-)

mandog · 2009-11-29 08:16:41

I think you are looking in the wrong direction I'm still using cdrkit,
I have no problems with brassero or any burning program I have 2 DVD drives and both are recognised and burn up x16 with no errors.
I think you have got permission errors possibly multiple permissions with hal and its replacement?
Also in the daemons list do not start hal in the background.

Last edited by mandog (2009-11-29 08:27:07)

Schily · 2009-11-29 18:30:35

Hald can really be seen as a hostile application regarding to
optical recording.

For the other problems that are not caused by bad hardware
or media, upgrade from wodim to the original software:

ftp://ftp.berlios.de/pub/cdrecord/alpha/

http://cdrecord.berlios.de/

Let me add some notes:

As the way hal has been introduced into Linux did cause a lot of trouble:

- Hald was introduced on Linux without contacting the authors of the
software it influences. This is one reason why hald interrupts the
CD/DVD/BluRay burning process.

- Hald (on Linux) uses an algorithm for detecting media change conditions
that is wrong (it hits even when there never was a media change). As
a result, hald triggers read operations on partially written media
that is currently written to in "uninteruptable streaming mode".
This creates coasters. As it caused the Optical Media software to
see strange SCSI error codes, the users are confused and do not
easily understand that a related write error was caused by hald.

- It seems that there is no concept for an interface that would allow
a safe way to write CD/DVD/BluRay media in multi-session or
multi-border mode.

- It seems that hald is based on OS specific implementation details
and for this reason would have portability problems in case that
there would be an interface for optical media software.

What I need is:

- A media change detection system that stays quiet (after some time -
e.g. after 3 seconds) in case that it detects the insertion of blank
media. This is implemented on Solaris since 1992.

- A system that can be told that there is new content without a media
change (write process finished) and mounting or multi-media playing
is possible.

- A working way to claim exclusive access to a drive that still allows
to send e.g. TEST UNIT READY and INQUIRY SCSI commands.

- A working way to tell the system to forcibly unmount the media at some
time in order to allow reliable multi-session operation. Active multi
media playing software should be shut down from this interface.

- The way the related drive "name" is specified must not be OS platform
specific.
Note that most platforms (including several "UNIX" platforms) do not not
have a UNIX like /dev/* entry for the device and many (including
Mac OS X) do not even associate a file handle to the interface that
allows to send SCSI commands. For this reason, /dev/* or file handle
based interfaces are highly non-portable.

cogent · 2010-04-12 21:47:54

I switched from cdrkit to cdrtools and from hal to hal-easy and still the same problem.

All apps fail about 1/3 of the way into a cd...

I haven't been able to burn a cd for weeks. This is sad

cogent · 2010-04-24 01:11:18

After no luck in any apps, I got cd's to burn by running the following command:

hal-disable-polling --device /dev/sr0

cogent · 2010-05-04 05:00:34

CORRECTION: burning only works with nero DAO/96 mode

arriagga · 2011-05-10 00:23:34

i have the same problem (i cant burn anything since last upgrade)

Arch Linux

#1 2008-12-13 19:15:15

CDs won't burn in GUI apps anymore

#2 2008-12-13 19:53:25

Re: CDs won't burn in GUI apps anymore

#3 2008-12-13 20:05:26

Re: CDs won't burn in GUI apps anymore

#4 2008-12-13 20:58:03

Re: CDs won't burn in GUI apps anymore

#5 2008-12-13 22:06:34

Re: CDs won't burn in GUI apps anymore

#6 2008-12-14 14:53:07

Re: CDs won't burn in GUI apps anymore

#7 2008-12-26 20:50:41

Re: CDs won't burn in GUI apps anymore

#8 2008-12-28 16:07:31

Re: CDs won't burn in GUI apps anymore

#9 2008-12-28 22:35:36

Re: CDs won't burn in GUI apps anymore

#10 2009-05-10 11:42:41

Re: CDs won't burn in GUI apps anymore

#11 2009-06-18 00:46:59

Re: CDs won't burn in GUI apps anymore

#12 2009-06-18 14:43:30

Re: CDs won't burn in GUI apps anymore

#13 2009-06-18 17:53:39

Re: CDs won't burn in GUI apps anymore

#14 2009-06-19 14:40:59

Re: CDs won't burn in GUI apps anymore

#15 2009-10-04 08:06:48

Re: CDs won't burn in GUI apps anymore

#16 2009-10-04 16:59:09

Re: CDs won't burn in GUI apps anymore

#17 2009-11-26 21:50:45

Re: CDs won't burn in GUI apps anymore

#18 2009-11-27 08:50:48

Re: CDs won't burn in GUI apps anymore

#19 2009-11-29 08:16:41

Re: CDs won't burn in GUI apps anymore

#20 2009-11-29 18:30:35

Re: CDs won't burn in GUI apps anymore

#21 2010-04-12 21:47:54

Re: CDs won't burn in GUI apps anymore

#22 2010-04-24 01:11:18

Re: CDs won't burn in GUI apps anymore

#23 2010-05-04 05:00:34

Re: CDs won't burn in GUI apps anymore

#24 2011-05-10 00:23:34

Re: CDs won't burn in GUI apps anymore

Board footer