Optical disks that failed to be read with Leap 42.2 were burnt between 1998 and 2004
Optical disks that could be read with Leap 42.2 were burnt between 1998 and 2007
those disks that could not be read were identified as follows
Check again: Can they still be read in Tumbleweed on same hardware? Disks do fail at random times. Also, if different reader, or dust on the lens, etc.
A double check has been made. The results are 100% reproducible.
With Leap 42.2 only about 50% of the optical disks are readable.
With Tumbleweed 100% are readable.
Also the there is an even split between those burnt on MS machines and Linux.
Assumptions:
the Device Notifier has been modified making it impossible for it to read some disks.
no HW failure as both Leap 42.2 and Tumbleweed are on the same machine
Additional info:
initially when selecting to copy a disk that failed, with K3b, the message
came up “System locale charset is ANSI_X3.4-1968”
(which seems to be an old problem)
this message no longer appears after putting
export LC_LANG=en_AU.utf8
export LC_CTYPE=“en_AU.utf8”
export LC_ALL=en_AU.utf8
in the user .bashrc file
although no attempt has been made to copy any disks
also tried using locale-gen but this function is not included in Leap 42.2?