kdemultimedia3 - patch to fix lockup of audiocd:/ kioslave

Stephan Kulow coolo at kde.org
Sun Sep 24 12:08:41 BST 2006

Am Freitag, 22. September 2006 13:08 schrieb Tilman Vogel:
> Hi!
> I debugged and fixed a problem of kdemultimedia-3.5.4 which causes the
> audiocd kioslave to not work at all on my machine.
> I sent the patch to bugs.kde.org
> <http://bugs.kde.org/show_bug.cgi?id=126174> but will attach it to this
> message too, because it's very small and because it didn't get any
> attention on bugs.kde.org yet. For convenience, I quote from my comment
> there:
> - CUT -
> In fact, cdparanoia-IIIalpha9.8-550 (from SuSE 10.0) does not return any
> device name in drive->ioctl_device_name (see
> kdemultimedia/kioslave/audiocd/audiocd.cpp). Therefore, the device
> cannot be opened and the number of tracks is not initialised. Then
> kio_audiocd hangs in a (virtually) endless loop, eating up lots of
> memory while filling a very long list of track names...
> I have to admit, that I am very surprised by the for me incomprehensible
> mix of using libwm (inside kscd) and libcdda_paranoia... paranoia
> already gives the right count in the drive structure referred above... so?
> Anyway, I could fix the problem by the attached patch which falls back
> to drive->cdda_device_name in case drive->ioctl_device_name is a null
> pointer or zero length.
> I don't know how cdparanoia behaves on other drives, but with my drive I
> definitely need this. cdparanoia identifies my drive as follows:
> Found an accessible SCSI CDROM drive.
> Looking at revision of the SG interface in use...
> SG interface version 3.5.33; OK.
> CDROM model sensed sensed: MATSHITA DVD-RAM UJ-822S 1.61
> Other SG drives with that version of cdparanoia most likely all have
> this problem.

Interesting. I have roughly the same drive and needed this exactly the very 
same way around (on 10.1 though). So it won't hurt the way you did it.

Greetings, Stephan

More information about the kde-core-devel mailing list