[k3b] [Bug 337553] k3b doesn't detect multiple writers properly
https://bugs.kde.org/show_bug.cgi?id=337553 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #11 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 337553] k3b doesn't detect multiple writers properly
https://bugs.kde.org/show_bug.cgi?id=337553 --- Comment #10 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 337553] k3b doesn't detect multiple writers properly
https://bugs.kde.org/show_bug.cgi?id=337553 Justin Zobel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #9 from Justin Zobel --- 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! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 337553] k3b doesn't detect multiple writers properly
https://bugs.kde.org/show_bug.cgi?id=337553 --- Comment #8 from Leslie Zhai --- 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 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 337553] k3b doesn't detect multiple writers properly
https://bugs.kde.org/show_bug.cgi?id=337553 --- Comment #7 from Stoat --- 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 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 337553] k3b doesn't detect multiple writers properly
https://bugs.kde.org/show_bug.cgi?id=337553 Leslie Zhai changed: What|Removed |Added CC||xiangzha...@gmail.com --- Comment #6 from Leslie Zhai --- 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 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 337553] k3b doesn't detect multiple writers properly
https://bugs.kde.org/show_bug.cgi?id=337553 --- Comment #5 from Stoat --- 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. -- You are receiving this mail because: You are watching all bug changes.
