Bug 187943

Summary: k3b does not burn
Product: [Fedora] Fedora Reporter: Chitlesh GOORAH <chitlesh>
Component: k3bAssignee: Harald Hoyer <harald>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 0.12.17-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-13 15:08:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
sysreport none

Description Chitlesh GOORAH 2006-04-04 19:45:55 UTC
Description of problem:
I've never ever burnt a single cd with k3b

Version-Release number of selected component (if applicable):
k3b-0.12.10-2.2
kdelibs-3.5.1-2.3
kernel-2.6.16-1.2080_FC5
kdebase-3.5.1-5

How reproducible:
Everysince Im using Fedora Core

Steps to Reproduce:
1.konsole
2.k3b
3.burn iso image
  
Actual results:
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key

Expected results:
It should be the cd

Additional info:
see attached sysreport

Comment 1 Chitlesh GOORAH 2006-04-04 19:45:55 UTC
Created attachment 127308 [details]
sysreport

Comment 2 Harald Hoyer 2006-04-05 10:01:22 UTC
Does this erratum fix your problems? 
http://www.redhat.com/archives/fedora-test-list/2006-March/msg01484.html

Comment 3 Chitlesh GOORAH 2006-04-06 16:52:02 UTC
It didn't work either :(
same situation as before, even gnomebaker crashes while starting to burn.

Comment 4 Chitlesh GOORAH 2006-12-13 15:08:19 UTC
For some reason, It started working again.
I'm closing this bug.