Version: unknown (using KDE 3.5.2, Kubuntu Package 4:3.5.2-0ubuntu0 dapper) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.16-deb6 I have a Thinkpad T60 with SATA-IDE and I use SCSI cdrom, ide is completely disabled because then cdrom only worked in PIO mode. I used to have this kernel log issue about wrong scsi command --> see Bug 103157 plus since I have been using scsi generic I never got correct track information in kio_audicd it shows 95 tracks on "Massive Attack - Blue lines" which has 9 Tracks, and the tracks are not numbered continuosly,the numbers go up to 221, all with a size of 0 B or last night I got 44 Byte but when I try to copy such a track it tells me the track doesn't exist. I rechecked this with other CD. same problem. I first conclude this is a kernel issue because it was no probem with ATAPI kernel driver, and I commented out the lines in sg.c that caused the log flooding --> see Bug 103157 This is not the problem, as tools like cdparanoia, cd-discid and XMMS have no problem to get correct number of tracks and get a CDDB result for it. If I copy a track that has actually a correct size sometimes - not always - kio_audiocd consumes 100% CPU and does not stop when I press the cancel button. I stops when I eject the disk.
I did some more tries. Kio_audiocd still has the problem. NO other tools has it not even kde programs like KAudioCdCreator. All show correct disk information. I don't know what is wrong.
Same here with Thinkpad T43p. In addition to symptoms described above .xsession-errors file is flooded with ASSERT: "i <= nodes" in /usr/share/qt3/include/qvaluelist.h (373) messages
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? 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!