Summary: | When I try to write a blu ray disc k3b says please insert media with greater capacity, even with a media size of 25 gigs and a compliation size of 17 gigs | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | cjae <cjae1> |
Component: | general | Assignee: | Michał Małek <michalm> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ben, fabo, muesli, trueg, wayland |
Priority: | NOR | ||
Version: | 1.91.0 | ||
Target Milestone: | 2.0 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.92.0 | |
Sentry Crash Report: |
Description
cjae
2010-05-02 21:06:53 UTC
Does K3b properly detect the media size? You can check that via right-click -> media info. That's the info I get to see under "Media Info". It's also notable that the "Available Space" indicator at the bottom of the mainwindow behaves fine when adding stuff to my current project. (e.g. shows 5,0 GiB of 23,3GiB) Type: BD-R Sequential (SRM) Capacity: 2715:25:17 min (23,3 GiB) Rewritable: no Appendable: no Empty: yes Layers: 1 Sessions: 0 Supported writing speeds: 2.0x (8991 KB/s) 4.0x (17982 KB/s) I've had a debugging session with Christian today and I think we disovered the issue. Device::writeCapabilities() doesn't contain MEDIA_BD_R_SRM. Since that's the medium which is inserted to the burner it doesn't get detected in EmptyDiscWaiter. Now, why Device::writeCapabilities() doesn't contain MEDIA_BD_R_SRM? Looks like nowhere in k3bdevice.cpp d->writeCapabilities is OR-ed with this flag. Maybe it should in line k3bdevice.cpp:2776, but we weren't sure. It probably is the same issue for MEDIA_BD_R_SRM_POW and MEDIA_BD_R_RRM. For plain MEDIA_BD_R it will work, maybe that's why it worked for Sebastian. SVN commit 1125491 by trueg: Properly set writeCapabilities for BD devices. BUG: 236069 M +3 -1 k3bdevice.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1125491 *** Bug 237324 has been marked as a duplicate of this bug. *** Ok, I tried this, and it gets past that stage now. I still can't burn, but I'll post that at http://forum.kde.org/viewtopic.php?f=153&t=85895&p=158221#p158221 since I'm not sure my other problem is a bug. *** Bug 227339 has been marked as a duplicate of this bug. *** *** Bug 229039 has been marked as a duplicate of this bug. *** |