Bug 337553

*** Bug 341180 has been marked as a duplicate of this bug. ***

*** Bug 252214 has been marked as a duplicate of this bug. ***

Created attachment 92986 [details]
results from solid-hardware lists (details)

Not sure why this is unconfirmed. I have the same problem, but looks like it is the way K3b is getting it's information from Udisks.

I have 2 identical drives: Lite-ON Model LH-20A1S (both are sata)
/dev/sr0 symlink of /dev/cdrom
/dev/sr1 symlink of /dev/cdrom1

1) K3b only sees /dev/sr1 when both are installed.
2) K3b will see /dev/sr0 only if unplug /dev/sr1. 

It might be the way K3b gets it information from udisks. 
Udisks reports two ways:

a) udi = '/org/freedesktop/UDisks2/drives/LITE_ON_DVDRW_LH_20A1S_LITE_ON_DVDRW_LH_20A1S
   1) where it only report /dev/sr1 (maybe just the last drive it sees if both the same)
   2) this way only looks at 'drives'

b)  '/org/freedesktop/UDisks2/block_devices/sr0'  AND udi = '/org/freedesktop/UDisks2/block_devices/sr1'
   1) where it reports both devices /dev/sr0 & /dev/sr1
   2) this way looks at 'block_devices'

c) Looks like K3b is only looking at udi = '/org/freedesktop/UDisks2/drives/

Also know that both drives are good. Have used /dev/sr0 with Xfburn, which sees both drives. Used with Xine, cdrecord,...

The problem appears to be due to optical devices reporting their model number in the scsi serial number field. Udisks doesn't like that and only reports the first one it sees.

This is a consistent "error" across multiple optical drive makers, so udisks needs to cope.

Hi,

k3b master https://github.com/KDE/k3b is able to detect multiple devices https://pbs.twimg.com/media/Cro8t4oUEAAonM2.jpg one is CDEmu and one is ASUS, if created more virtual devices by CDEmu, k3b is also able to detect them!

so please try k3b master branch, if still unable to dectect, please let me know, thanks a lot!

Regards,
Leslie Zhai

Leslie: This bug can only be tested if you have 2 _identical_ drives.

if you use a bunch of different models then they get picked up fine.

I'll test this, but please bear the point above in mind.

Thanks

Hi Stota,

> This bug can only be tested if you have 2 _identical_ drives

There are often /dev/sr0, /dev/sr1, /dev/srN for the multi-drivers of Real or Virtual device driver.
But I will bear the point you mentioned in mind, and please test the master branch, thanks a lot ;-)

Regards,
Leslie Zhai

Thank you for reporting this bug 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!