! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Actually use detected capabilities for a drive
Status:
RESOLVED: FIXED

Comments

Description xface 2006-08-18 20:50:50 CEST
My first test of xfburn was on an old scsi cd burner I acquired. I tried to burn an ISO and it locked up the device. Had to power cycle it to regain control.

Turns out it could not handle the CDRW medium I fed it.


AFAIK the lock up is more of a kernel issue on Linux but that underlines the importance of checking the medium before burning. 

In k3b for examble there queries the drives capabilities and issues a cancel/force-it option in this sort of situation 

That would seem preferable to a total refusal but this probably should at least be trapped in view of the inconvenient consequences.
Comment 1 xface 2006-08-18 21:19:26 CEST
just seen this on console so it's already detecting caps. Block inappropriate media should be fairly simple.

** Message: device [1] capabilities : CD-R

;)
Comment 2 Jean-François Wauthy editbugs 2006-08-18 21:20:06 CEST
i'll see to it, but so far xfburn relies on cdrecord for such thing and apparently it shouldn't
Comment 3 Mario Đanić 2008-04-12 20:10:05 CEST
We now use libburnia libraries. Closing candidate.
Comment 4 xface 2008-04-12 20:55:39 CEST
Closing candidate ??

I am not clear whether that means this issue is resolved. Could you explain "candidate"? 
Comment 5 Mario Đanić 2008-04-13 08:58:36 CEST
(In reply to comment #4)
> Closing candidate ??
> 
> I am not clear whether that means this issue is resolved. Could you explain
> "candidate"? 
> 

The issue should be solved in newest svn. Would you be so kind to test it, and see if you can still reproduce the problem?

Comment 6 Jérôme Guelfucci editbugs 2008-04-13 15:23:53 CEST
For me, this does not seem to be fixed, xfburn detects correctly what each drive can do (as can be seen in the preferences dialog, second tab) but still offers to burn a composition whith both drives, even the one that can't do it.
Comment 7 Mario Đanić 2008-04-13 15:37:46 CEST
Accepting the bug, will be fixed before release. Thank you for testing.
Comment 8 xface 2008-04-13 17:40:27 CEST
A -force option may be useful like kde does.

Maybe a checkbox "enable all drives" or so.

Sometimes drive capabilities and media sniffing are unreliable (codes wrongly identified or incorrectly interpreted). If the user knows his media to be burnable (or just wants to try his luck) the program should not be inoperable.

Glad to see this close to a fix anyway. Nice work.
Comment 9 David Mohr 2008-06-05 22:49:18 CEST
This should be fixed in rev 4892. If anyone could check that it works, that'd be great - I don't have a drive which can't burn something ;-). Except BD of course, but then I'm not sure if the drive would even detect that as a disc.

Actually, that is a very good question, does a drive that can't write CDRW even detect that a CDRW is inserted?

Bug #2194

Reported by:
xface
Reported on: 2006-08-18
Last modified on: 2020-05-24

People

Assignee:
Mario Đanić
CC List:
2 users

Version

Version:
unspecified

Attachments

Additional information