Version: 1.91.0 (using 4.4.3 (KDE 4.4.3), PCLinuxOS release 2010 (PCLinuxOS) for i586) Compiler: gcc OS: Linux (i686) release 2.6.32.11-pclos2.bfs Several days ago, prior to installing new pclos 2010 release, I used K3b (in pclos 2009) to back up all the data I wanted to keep (mp3s, jpeg, bmp, avi, mpeg, pdf, the usuall etc) to DVD+R in ISO format. When I was done, I made sure they were accessible before continuing with new OS install. Now, after I'm up and running, the DVD-RW used to make them is unable to mount any of the data DVDs with the command line -- mount -t iso9660 /dev/sr0 /media/cdrom, and K3b informed me that the background data was incomplete and that the disc (and I quote) "was probably created with buggy software". I can't decide whether to laugh or cry. Also, up until today, I had been able to mount the discs in my other drive (which is a DVD-ROM) but in read-only mode which was annoying because I had to then right click and open files as root, put in password, etc. and it was only about 50% successfull in copy/paste operation. K3b recognizes the disc in both DVD-RW and DVD-ROM drive, but only reports ISO info in DVD-ROM. I right clicked and selected copy medium in both drives, only checked "only create image" to try to copy entire ISO back to hard drive and both times it err. Here is debugging output for DVD-RW Devices ----------------------- DVD-16X DVD-ROM BDV316G 0C17 (/dev/sr1, CD-ROM, DVD-ROM) [DVD-ROM, CD-ROM] [None] [%7] HP DVD Writer 1040r MH21 (/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] System ----------------------- K3b Version: 1.91.0 KDE Version: 4.4.3 (KDE 4.4.3) QT Version: 4.6.2 Kernel: 2.6.32.11-pclos2.bfs and here is debugging output for DVD-ROM Devices ----------------------- DVD-16X DVD-ROM BDV316G 0C17 (/dev/sr1, CD-ROM, DVD-ROM) [DVD-ROM, CD-ROM] [None] [%7] HP DVD Writer 1040r MH21 (/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::DataTrackReader ----------------------- reading sectors 0 to 2289791 with sector size 2048. Length: 2289792 sectors, 4689494016 bytes. using buffer size of 64 blocks. Error while writing to IO device. Current sector is 0. Read a total of 64 sectors (131072 bytes) System ----------------------- K3b Version: 1.91.0 KDE Version: 4.4.3 (KDE 4.4.3) QT Version: 4.6.2 Kernel: 2.6.32.11-pclos2.bfs I then tried enabling DMA on both drives using hdparm (in super user mode) and both drives said "setting using_dma to 1 (on) HDIO_SET_DMA failed: Inappropriate ioctl for device HDIO_GET_DMA failed: Inappropriate ioctl for device". Call me crazy, but I hope all this babbling I've just done is a waste of your time and mine due to something simple I've been overlooking. Please let me know if you require any further info, if this is even truly a bug with K3b. Thank you for your time. Sincerely, still a complete noob.
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!
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!