Bug 332992 - K3b no burn with recently format (quick) DVD-RW
Summary: K3b no burn with recently format (quick) DVD-RW
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 2.0.2
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2014-04-03 01:55 UTC by Brallan Aguilar
Modified: 2018-09-19 14:37 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Quick Formatting output (1.55 KB, text/plain)
2014-04-03 01:57 UTC, Brallan Aguilar
Details
Burning output using K3b (1.64 KB, text/plain)
2014-04-03 01:58 UTC, Brallan Aguilar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brallan Aguilar 2014-04-03 01:55:56 UTC
K3b no burns a recently quick-formatted DVD-RW (using K3b). The only way is to retry but no using quick format.

Reproducible: Always

Steps to Reproduce:
1. Burn a DVD-RW
2. Use a quick format to delete the content of the DVD
3. Try to burn in it again but K3b can not.



I attach two files generated with K3b: Quick format output and Burning output (using quick-formatted DVD).
Comment 1 Brallan Aguilar 2014-04-03 01:57:47 UTC
Created attachment 85923 [details]
Quick Formatting output
Comment 2 Brallan Aguilar 2014-04-03 01:58:33 UTC
Created attachment 85924 [details]
Burning output using K3b
Comment 3 srikkanth87 2014-08-19 03:37:57 UTC
I noticed the same issue with K3B from a long time.

After a quick format K3B does not recognise he disk and continue. User has to eject and reinsert the disk after which K3B detects a blank disk and can be continued to burn...
Comment 4 Scarlett Moore 2014-09-30 01:00:34 UTC
K3B 2.0.2 Kubuntu Quick format - k3b automatically ejected my cd when the quick format was done, all I had to do was re-insert the cd and it recognized the cd as writable just fine. So with that said I cannot reproduce this.
Comment 5 Andrew Crouthamel 2018-09-19 14:37:37 UTC
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.