K3b (Version 2.0.0 -- KDE 4.4.5) refuses to "overburn" even if the related option is correctly set. Not a burner issue since cdrecord does overburning fine. Reproducible: Always Steps to Reproduce: 1. Load a medium of size X (e.g. 700MB) 2. Create a data project and drag one or more items totalling more than X 3. Click the burn icon 4. Click the burn button Actual Results: It doesn't even start the process (whatever option I choose, except image only which works fine), just stops asking for a bigger medium (see attached screen shot). Expected Results: Start burning the medium. $ cat k3b.log Devices ----------------------- SONY DVD RW DW-G521A FPS3 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7] K3b::IsoImager ----------------------- mkisofs print size result: 361111 (739555328 bytes) System ----------------------- K3b Version: 2.0.0 KDE Version: 4.4.5 (KDE 4.4.5) QT Version: 4.6.3 Kernel: 2.6.34-tuxonice-r6 Used versions ----------------------- mkisofs: 3.0 mkisofs ----------------------- /usr/bin/mkisofs: Warning: Cannot add inode hints with -no-cache-inodes. 361111 mkisofs calculate size command: ----------------------- /usr/bin/mkisofs -gui -graft-points -print-size -quiet -volid Bullet Ballet -volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-poleggi/k3bP10605.tmp -rational-rock -hide-list /tmp/kde-poleggi/k3bJ10605.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-poleggi/k3bR10605.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-poleggi/k3bw10605.tmp
Created attachment 253905 [details] screen shot of k3b asking for bigger medium
Not sure if we can do much here. I'd suggest you file a bugreport at http://bugs.kde.org/ and add a link to that report here in the URL field (so we can keep track of it)...
Oops, sorry, I couldn't find it in my previous searches on kde.bugs.org -- it looks like it's already fixed in KDE's SVN trunk, see here: <https://bugs.kde.org/show_bug.cgi?id=241534> Though I can't test, 'cause no info about the release is given. I let you resolve this -- don't know much about resolution policies here...
The fix is included in k3b-2.0.1, and that's already in portage. Give it a try! :)
