On 12/25/2014 12:47 AM, Basil Chupin wrote:
OK. I've just read over your original post.
Always a good start.
Firstly, what happens if you start k3b FIRST and then try and insert a blank disc?
I get the popup notice about there not being a writer as soon as k3b starts whether there is a disk in either of the burners or not. Since the contents of /proc/sys/dev/cdrom/info says that neither can write, and I'm told that is generated by the kernel, this makes sense.
Secondly, you have a "CD burner" [sr0] and a "DVD burner" [sr1].
As far as I can tell its the other way round.
As far a I know - which has always been the case with me and I only have the one burner, DVDRW - the DVD burner will also burn CDs so why do you have a burner for CDs and another for DVDs? k3b confused?
That's how the box came. My next test is going to be conect only one at a time. I don't know if its useful but starting k3b from the CLI results in this
k3b Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) k3b(9252)/kdeui (kdelibs): Attempt to use QAction "location_bar" with KXMLGUIFactory! anton@Mainbox:/proc/sys/dev> QCoreApplication::postEvent: Unexpected null receiver k3b(9252) KDirWatch::removeDir: doesn't know ""
-- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org