I can not burn any DVD to more than 4X

Bug #191568 reported by usr
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

I can not burn any DVD to more than 4X. I have tried in Kubuntu 6.06, 6.10, 7.04 and 7.10. I have tried too in different computers and the result is the same. I always use K3b.
When I used Windows I could record to 8X without no problem in the same computers.

Revision history for this message
usr (usrlp-deactivatedaccount-deactivatedaccount) wrote :
description: updated
Revision history for this message
usr (usrlp-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
usr (usrlp-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
usr (usrlp-deactivatedaccount-deactivatedaccount) wrote :
description: updated
Revision history for this message
SK (stephantom) wrote :

Thank you for taking the time to report this issue and helping to improve Ubuntu!
This report was not reported against a specific package. I have assigned the correct package now. Please try to file future bug reports against the right packages. You can learn to find the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage
Feel free to report any other issues you might find!

Revision history for this message
usr (usrlp-deactivatedaccount-deactivatedaccount) wrote :

OK. Thank you! :-)

penalvch (penalvch)
tags: added: dapper edgy fiesty gutsy needs-kernel-logs needs-upstream-testing
removed: burn dvd k3b kubuntu
Revision history for this message
penalvch (penalvch) wrote :

usr, thank you for reporting this and helping make Ubuntu better. Dapper desktop reached EOL on July 14, 2009.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.7-rc1-quantal

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

affects: k3b (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.