I am not sure that this upstream fix will help. It makes the udev scan effectively dependant on whether there is a current profile reported by the drive. The drive in the cases we have documented are reporting a profile, indeed if they were not we would not be attempting the TOC read and later. Notethe ID_CDROM_MEDIA_<type>=1 in each report below:
This is patently an error and one which appears to be coming direct from the drive. It is reporting itself still as containing something when it does not.
Before the upstream fix we could have elided the TRACK_COUNT when the device reported blank but that will not work following the upstream change.
I am not sure that this upstream fix will help. It makes the udev scan effectively dependant on whether there is a current profile reported by the drive. The drive in the cases we have documented are reporting a profile, indeed if they were not we would not be attempting the TOC read and later. Notethe ID_CDROM_ MEDIA_< type>=1 in each report below:
ID_CDROM=1 MEDIA_CD= 1 MEDIA_STATE= blank MEDIA_SESSION_ NEXT=2894 MEDIA_SESSION_ COUNT=19194 MEDIA_TRACK_ COUNT=47323
ID_CDROM_DVD=1
ID_CDROM_MRW=1
ID_CDROM_MRW_W=1
ID_CDROM_
ID_CDROM_
ID_CDROM_
ID_CDROM_
ID_CDROM_
and:
ID_CDROM=1 MEDIA_DVD= 1 MEDIA_STATE= blank MEDIA_SESSION_ NEXT=55296 MEDIA_SESSION_ COUNT=45312 MEDIA_TRACK_ COUNT=20736
ID_CDROM_DVD=1
ID_CDROM_
ID_CDROM_
ID_CDROM_
ID_CDROM_
ID_CDROM_
This is patently an error and one which appears to be coming direct from the drive. It is reporting itself still as containing something when it does not.
Before the upstream fix we could have elided the TRACK_COUNT when the device reported blank but that will not work following the upstream change.