Error burning SVCD

Bug #500157 reported by gazpa
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
k3b (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: k3b

Devices
-----------------------
HL-DT-ST DVD-RAM GSA-H50L 1.00 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7]

K3b::VcdXml:
-----------------------
<?xml version="1.0"?>
<!DOCTYPE videocd PUBLIC "-//GNU//DTD VideoCD//EN" "http://www.gnu.org/software/vcdimager/videocd.dtd">
<videocd version="1.0" class="svcd" xmlns="http://www.gnu.org/software/vcdimager/1.0/" >
 <info>
  <album-id></album-id>
  <volume-count>1</volume-count>
  <volume-number>1</volume-number>
  <restriction>0</restriction>
 </info>
 <pvd>
  <volume-id>VIDEOCD</volume-id>
  <system-id>CD-RTOS CD-BRIDGE</system-id>
  <application-id>CDI/CDI_VCD.APP;1</application-id>
  <preparer-id>K3B - VERSION 1.68.0</preparer-id>
  <publisher-id>K3B - VERSION 1.68.0</publisher-id>
 </pvd>
 <filesystem>
  <folder>
   <name>SEGMENT</name>
  </folder>
 </filesystem>
 <sequence-items>
  <sequence-item id="sequence-000" src="/media/almacen2/rey/rey.mpg" >
   <default-entry id="entry-000" />
  </sequence-item>
 </sequence-items>
</videocd>

System
-----------------------
K3b Version: 1.68.0
KDE Version: 4.3.2 (KDE 4.3.2)
QT Version: 4.5.2
Kernel: 2.6.31-17-generic

vcdxbuild
-----------------------
I/O warning : failed to load external entity "/tmp/kde-gazpa/k3bR30114.tmp"
<log level="warning">error while parsing file `/tmp/kde-gazpa/k3bR30114.tmp': No such file or directory</log>

vcdxbuild command:
-----------------------
/usr/bin/vcdxbuild --progress --gui --cue-file=/tmp/kde-gazpa//VIDEOCD.cue --bin-file=/tmp/kde-gazpa//VIDEOCD.bin /tmp/kde-gazpa/k3bR30114.tmp

ProblemType: Bug
Architecture: amd64
Date: Thu Dec 24 16:39:21 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/k3b
NonfreeKernelModules: nvidia
Package: k3b 1.68.0~alpha3-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: k3b
Uname: Linux 2.6.31-17-generic x86_64

Revision history for this message
gazpa (alain-crespo) wrote :
gazpa (alain-crespo)
Changed in k3b (Ubuntu):
assignee: nobody → Kubuntu Bugs (kubuntu-bugs)
tags: added: k3b svcd
Revision history for this message
Alessandro Briosi (tsdogs) wrote :

It seems to be a kernel bug. doing the same with an older kernel (ubuntu kernel 2.6.31-11) worked for me.

Revision history for this message
gazpa (alain-crespo) wrote :

I think that the problem is the no existence of /tmp/kde-gazpa/k3bR30114.tmp file. K3b tells to vcdxbuild that file, but it doesn't exist.

Changed in k3b (Ubuntu):
assignee: Kubuntu Bugs (kubuntu-bugs) → nobody
Revision history for this message
Rohan Garg (rohangarg) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

Changed in k3b (Ubuntu):
status: New → Incomplete
Revision history for this message
Harald Sitter (apachelogger) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!

Changed in k3b (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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