[prev in list] [next in list] [prev in thread] [next in thread] 

List:       k3b
Subject:    [k3b]  [Bug 337553] k3b doesn't detect multiple writers properly
From:       David <decibelshelp () charter ! net>
Date:       2015-06-04 0:41:04
Message-ID: bug-337553-188845-tNBrf0IHSq () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=337553

--- Comment #4 from David <decibelshelp@charter.net> ---
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,...

-- 
You are receiving this mail because:
You are the assignee for the bug.
[prev in list] [next in list] [prev in thread] [next in thread]