[k3b] [Bug 337553] k3b doesn't detect multiple writers properly

2022-11-24 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=337553 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED

[k3b] [Bug 337553] k3b doesn't detect multiple writers properly

2022-11-09 Thread Bug Janitor Service
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

[k3b] [Bug 337553] k3b doesn't detect multiple writers properly

2022-10-25 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=337553 Justin Zobel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED

[k3b] [Bug 337553] k3b doesn't detect multiple writers properly

2016-10-10 Thread Leslie Zhai via KDE Bugzilla
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

[k3b] [Bug 337553] k3b doesn't detect multiple writers properly

2016-10-09 Thread Stoat via KDE Bugzilla
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.

[k3b] [Bug 337553] k3b doesn't detect multiple writers properly

2016-09-11 Thread Leslie Zhai via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=337553 Leslie Zhai changed: What|Removed |Added CC||xiangzha...@gmail.com ---

[k3b] [Bug 337553] k3b doesn't detect multiple writers properly

2016-06-03 Thread Stoat via KDE Bugzilla
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