https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #63 from Thomas Schmitt <scdbac...@gmx.net> --- Hi, i found a suspect: https://cgit.kde.org/k3b.git/tree/libk3b/jobs/k3biso9660imagewritingjob.cpp#n232 void K3b::Iso9660ImageWritingJob::startWriting() { ... else { mt = K3b::Device::MEDIA_WRITABLE_DVD; } And no MEDIA_WRITABLE_BD ! This would mean it happens only with image writing but not with Data Composition. A good explanation why K3B can claim BD capability since years but does not work for Cristian's use case. The fog rises up. ----------------------------------------------------------------------- Coarse test proposal: Add (actually "or") unconditionally K3b::Device::MEDIA_WRITABLE_BD to mt. else { mt = K3b::Device::MEDIA_WRITABLE_DVD | K3b::Device::MEDIA_WRITABLE_BD; } Does this change appease that nasty "give me a 21.4 GiB medium" window ? If this works, then Leslie and i have to riddle whether this is the final solution and thus what this piece of code does. I have some idea but that would have to be verified. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
