[Jaunty] k3b in gnome fails to burn audio CD reporting I/O error

[Nigel Cundy]

Binary package hint: k3b

sudo dpkg -l | grep k3b
ii k3b 1.0.5+kde4svn935857+really1.0.5-3ubuntu5 A sophisticated KDE CD burning application
ii k3b-data 1.0.5+kde4svn935857+really1.0.5-3ubuntu5 A sophisticated KDE CD burning application - data files
ii k3b-i18n 1.0.5-1ubuntu1 Internationalized (i18n) files for k3b
ii libk3b3 1.0.5+kde4svn935857+really1.0.5-3ubuntu5 The KDE cd burning application library - runtime files
ii libk3b3-extracodecs 1.0.5+kde4svn935857+really1.0.5-3ubuntu5 The KDE cd burning application library - extra decoders

I run a jaunty system which I dist-upgraded from Intrepid. I ran k3b in Intrepid without any problems.

 I tried burning an audio CD in Gnome earlier today (having failed with Brasero, which I'm still investigating).
K3B reported an I/O error (your disk is probably full) when I clicked on `burn,' without starting the burning process. After a little experimentation, I fixed the problem with

mkdir /tmp/kde-`whoami`

and was able to burn my CD. If k3b requires this temporary directory, then it should be created at some point as the application is started.

[Rohan Garg (rohangarg)]

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.

[Harald Sitter (apachelogger)]

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!