| Summary: | Empty cdrom not recognized | ||
|---|---|---|---|
| Product: | [Applications] k3b | Reporter: | Grondin <bertrand.grondin> |
| Component: | Burning/Hardware | Assignee: | k3b developers <k3b> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | hochdavid, joerg.schilling, thomas, trueg |
| Priority: | NOR | ||
| Version: | 2.0.2 | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | medium missing in dropdown list | ||
|
Description
Grondin
2012-04-21 22:47:49 UTC
Created attachment 74472 [details]
medium missing in dropdown list
When I want to burn a CD-ROM from an ISO image k3b sees the medium as can be seen in the left list in the background, but it doesn't appear in the dropdown list from the "Burn Image" dialog.
If I eject the CD, I can see that the list in the background first says "No medium", then when I insert it again and wait a bit, it is correctly registered - but still only in the list in the background. The dropdown list flickers for a second, but the medium still doesn't appear in the list.
k3b 2.0.2 on KDE 4.9.2 btw. And apparently this only happens with large ISOs, eg. the Kubuntu installer in the attached screenshot. It burned fine using: cdrecord -v -pad speed=1 -overburn kubuntu-12.04.1-desktop-i386.iso If anything k3b could give a warning that the image might be too large, ask if you want to try anyway, and then try with the -overburn switch (assuming that is possible?) This error is still not resolved. Instead of pointing to the real problem (iso file too large), k3b says "Please insert an empty medium". Maybe you are not using official software but something that was created by OSS-hostile people from Debian. the original cdrecord correctly checks for the media size. This is why I recommend to first upgrade to recent original software from ftp.berlios.de/pub/cdrecord/alpha/ Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Please however be careful: Some unfriendly Linux distros still ship the dead fork called "cdrkit" that results in a source state from May 2004. So you should warn your users in case that old software has been installed. Make sure to use a PATH that finds /opt/schily/bin/mkisofs before /usr/bin/mkisofs and inform your users that recent software is at this location: Bi-weekly snapshots (recommended): http://sourceforge.net/projects/schilytools/files/ Less frequent regular release: http://sourceforge.net/projects/cdrtools/files/alpha So called "stable" release: http://sourceforge.net/projects/cdrtools/files/ Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |