https://bugs.winehq.org/show_bug.cgi?id=49788
--- Comment #5 from TasosSah winebugzilla@tasossah.com --- (In reply to Esme Povirk from comment #3)
Patch sent: https://www.winehq.org/pipermail/wine-devel/2020-November/176663.html
However, this doesn't fully fix the regression. I'm told that udisks2 does not report a /dev/sgX device, and that wnaspi32 depends on this.
Since we need Linux-specific logic somewhere to locate the correct 'sg' driver device, and it's wnaspi32's Linux-specific code that needs it, that logic should be added to wnaspi32 IMO.
First of all, thank you for the patch.
Only easy way I see of associating the info in regedit reported by mountmgr with that patch is to open up /sys/bus/scsi/devices and match the scsi bus and id, and then opening the "generic" symlink. I'll try making a patch for wnaspi32.
Additionally, the submitted patch only reports optical drives on my system, and with a generic name. In this case DeviceName is "CdRom1". Fixed disks are also not reported at all.
There's also a new blank key called "Initiator Id 255" which wasn't there before.
(In reply to Saulius K. from comment #4)
(In reply to Esme Povirk from comment #3)
that udisks2 does not report a /dev/sgX device, and that wnaspi32 depends on this.
But maybe it should? I am not familiar with udisks2, thus my curiosity.
Since we need Linux-specific logic somewhere to locate the correct 'sg' driver device, and it's wnaspi32's Linux-specific code that needs it, that logic should be added to wnaspi32 IMO.
Ooor... it could be added to udisks2 too in case it's bug of udisks2, no?
Ideally, I think so, yeah, but I feel like a lot of existing systems won't get an updated version of udisks2 if they add support for it. I think there should be a fallback.
The original report was about Debian not having /proc/scsi/scsi, and in the process of attempting to fix it, if I am understanding this correctly, the code was added to libhal, which is deprecated, and udisks2 doesn't support this.