wodim 1.0-1 is already installed. gnomebaker works fine. In k3b the burn
dialog doesn't appear. I think the problem is not related to wodim. I think
the problem is in k3b. The brk-syscall is called endless (last lines in the
log). I think a function, which reserves some memory and then fails is
A backtrace with gdb:
#0 0xb66891c1 in mallopt () from /lib/tls/libc.so.6
#1 0xb68363b1 in operator delete () from /usr/lib/libstdc++.so.6
#2 0xb719dec8 in QStringData::deleteSelf () from /usr/lib/libqt-mt.so.3
#3 0x08129a02 in QString::~QString ()
#4 0xb71a214c in QString::arg () from
Additional Information:
- Burner is IDE
- DMA is enabled
I started k3b as follows:
strace -f k3b --nofork
After klicking e.g. Burn Image the output is:
ioctl(6, FIONREAD, [1]) = 0
ioctl(6, FIONREAD, [1]) = 0
ioctl(6, FIONREAD, [1]) = 0
ioctl(6,
Hi Martin,
Thanks for the additional details.
Whenever you burn something with K3b, does it just hang or are you able to
get to the burning log at some point?
Also, have you been able to test your version of wodim with gnomebaker to
check whether the problem is coming from K3b or wodim?
Ok, thanks for letting me know!
Francois
On Fri, Nov 17, 2006 at 09:55:59AM +0100, Martin Bammer wrote:
Sorry, the earliest date I can send you this information is the 27.Nov,
because I'm on holiday and the machine is at my workplace.
Martin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Package: k3b
Version: 0.12.17-3
Severity: important
Since the last upgrade k3b consumes 100 percent CPU and eats up all
memory when starting an action like Burn Image.
This behavior is since the last run of the setup wizard. I started it
because every burning action failed. I've seen in the setup
It works fine on my box, so I'm going to need some more details about your
setup:
- What kind of burner do you have? (IDE, SATA, SCSI, USB)
- Is DMA enable for your drive?
(check with hdparm -d /dev/hda where /dev/hda is your burner)
- What are you burning when it takes 100% of the
7 matches
Mail list logo
