k3b takes all memory and cpu when choosing "burn cd image"

[Pavel Šimerda]

Binary package hint: k3b

I turned on k3b (with proper k3b setup using burning group) and choose "Burn CD Image" from the menu.

Nothing reasonable doing yet, k3b uses (according to top) 99% cpu and an increasing amount of memory (i killed it on 85%).

[Kenny Duffus (kduffus)]

please could you explain what you mean by "Nothing reasonable doing yet"

[Pavel Šimerda (pavlix)]

I click on the menu item and k3b stops responding.

No window appears, no error, nothing.

[Kenny Duffus (kduffus)]

What happens if you leave it, does it recover?

How fast is your machine and how much RAM does it have?

[Pavel Šimerda (pavlix)]

If i kill k3b or terminate through X (titlebar button, confirming termination), the system recovers. It's only k3b that hangs.

AMD Sempron 2400+ (1666 MHz), 512 MB ram, 52x cd-rw (dvd-rom combo)

[Kenny Duffus (kduffus)]

do you still have this problem if you upgrade to 0.12.17 in dapper-backports or edgy?

[Pavel Šimerda (pavlix)]

I'm not switching to edgy any soon, when I try with a livecd, I'll report.

[Mario Đanić (mario-danic)]

Do you still have this problem in feisty/gutsy?

[Sam Peterson (peabodyenator)]

I'm not sure if my problems with K3B are related to this bug or not, but I am running Fiesty Fawn and I cannot use K3B to burn image files. I have an Optiarc dvd burner which I believe is a SATA drive in my compaq presario c571nr laptop. Thing spins its wheels forever, and error messages related to the drive show up in dmesg. Not sure what the problem could be. It's not a big deal for me because burning data CDs/DVDs works.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 alpha?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described 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!