Version: 0.11.20cvs (using KDE KDE 3.4.0) Installed from: SuSE RPMs OS: Linux SuSE 9.1 Pro k3b: 0.11.20cvs KDE: 3.4.0 level "b" dvd+rw-tools: 5.21.4.10.8-1 Devices ----------------------- PLEXTOR DVDR PX-716A 1.07 (/dev/hdc, ) at /media/dvdrecorder [CD-R; CD-RW; CD-ROM; DVD-ROM; DVD-R] [Error] [SAO; TAO; RAW; SAO/R16; RAW/R96P; RAW/R96R] I can burn almost everything if I start k3b as a regular user. But it fails when I try to burn dual layer DVD+R. If I start k3b as root, everything is OK. Here is the log output when it fails and the dvd+rw-mediainfo output: Devices ----------------------- PLEXTOR DVDR PX-716A 1.07 (/dev/hdc, ) at /media/dvdrecorder [CD-R; CD-RW; CD-ROM; DVD-ROM; DVD-R] [Error] [SAO; TAO; RAW; SAO/R16; RAW/R96P; RAW/R96R] LITEON DVD-ROM LTD163 GDHJ (/dev/hdb, ) at /media/dvd [CD-ROM; DVD-ROM] [DVD-ROM; CD-ROM] [None] System ----------------------- K3b Version: 0.11.20cvs KDE Version: 3.4.0 Level "b" QT Version: 3.3.4 Kernel: 2.6.5-7.151-default growisofs ----------------------- Executing 'builtin_dd if=/dev/fd/0 of=/dev/hdc obs=32k seek=0' /dev/hdc: splitting layers at 1925712 blocks :-( unable to SEND DVD+R DOUBLE LAYER RECORDING INFORMATION: Operation not permitted growisofs comand: ----------------------- /usr/bin/growisofs -Z /dev/hdc=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=dao -dvd-compat -speed=4 -overburn mkisofs ----------------------- /usr/bin/mkisofs: Warning: -follow-links does not always work correctly; be careful. The pad was 21 for file VIDEO_TS.BUP The pad was 21 for file VIDEO_TS.IFO The pad was 15 for file VIDEO_TS.VOB The pad was 22 for file VTS_01_0.BUP The pad was 22 for file VTS_01_0.IFO The pad was 17 for file VTS_01_0.VOB The pad was 5 for file VTS_01_1.VOB The pad was 23 for file VTS_02_0.BUP The pad was 23 for file VTS_02_0.IFO The pad was 17 for file VTS_02_0.VOB The pad was 12 for file VTS_02_1.VOB The pad was 23 for file VTS_03_0.BUP The pad was 23 for file VTS_03_0.IFO The pad was 17 for file VTS_03_0.VOB The pad was 26 for file VTS_03_1.VOB The pad was 23 for file VTS_04_0.BUP The pad was 23 for file VTS_04_0.IFO The pad was 49 for file VTS_04_0.VOB The pad was 28 for file VTS_04_5.VOB The pad was 31 for file VTS_05_0.BUP The pad was 31 for file VTS_05_0.IFO The pad was 17 for file VTS_05_0.VOB The pad was 2 for file VTS_05_3.VOB The pad was 23 for file VTS_06_0.IFO The pad was 17 for file VTS_06_0.VOB The pad was 1 for file VTS_06_1.VOB /usr/bin/mkisofs: Connection reset by peer. cannot fwrite 2048*1 mkisofs comand: ----------------------- /usr/bin/mkisofs -gui -graft-points -volid K3b data project -volset -appid K3B THE CD KREATOR VERSION 0.11.20cvs (C) 2003 SEBASTIAN TRUEG AND THE K3B TEAM -publisher -preparer K3b - Version 0.11.20cvs -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-sunny/k3b77l4tb.tmp -rational-rock -hide-list /tmp/kde-sunny/k3bYWaotc.tmp -full-iso9660-filenames -follow-links -iso-level 2 -path-list /tmp/kde-sunny/k3bTb0Mub.tmp -dvd-video /tmp/kde-sunny/k3bVideoDvd1 /home/sunny/.kde/share/apps/k3b/temp/dummydir0/ This the output of mediainfo: > dvd+rw-mediainfo /dev/hdc INQUIRY: [PLEXTOR ][DVDR PX-716A ][1.07] GET [CURRENT] CONFIGURATION: Mounted Media: 2Bh, DVD+R Double Layer Media ID: RITEK/D01 Current Write Speed: 4.0x1385=5540KB/s Write Speed #0: 4.0x1385=5540KB/s Write Speed #1: 2.4x1385=3324KB/s GET [CURRENT] PERFORMANCE: Write Performance: 4.0x1385=5540KB/s@[0 -> 4173824] Speed Descriptor#0: 02/4173824 R@8.0x1385=11080KB/s W@4.0x1385=5540KB/s Speed Descriptor#1: 02/4173824 R@8.0x1385=11080KB/s W@2.4x1385=3324KB/s READ DVD STRUCTURE[#0h]: Media Book Type: E1h, DVD+R DL book [revision 1] Legacy lead-out at: 2086912*2KB=4273995776 DVD+R DOUBLE LAYER BOUNDARY INFORMATION: L0 Data Zone Capacity: 2086912*2KB, can still be set READ DISC INFORMATION: Disc status: blank Number of Sessions: 1 State of Last Session: empty Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: blank Track Start Address: 0*2KB Next Writable Address: 0*2KB Free Blocks: 4173824*2KB Track Size: 4173824*2KB READ CAPACITY: 1*2048=2048
Then this is clearly not a bug but a permission problem!
Thanks for the response. But how comes that without changing anything, just using a single layer media, or CD, the burn process is OK. It fails only with dual layer media. Or at least, what more special permissions a dual layer media requires? This is reproducible always on my system. If I eject the dual layer media, and create a new single layer project and insert single layer media, it works like a charm. Cheers Sunny
i have no idea, sorry. maybe the kernel includes some bad patches from >= 2.6.8 that cause this.
as mentioned, not a bug.