Bug 10399 - Wrong maximum burning speed(s)
Summary: Wrong maximum burning speed(s)
Status: RESOLVED FIXED
Alias: None
Product: hal
Classification: Unclassified
Component: hald (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Danny Kukawka
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-24 09:40 UTC by Rouquier Philippe
Modified: 2007-08-29 01:19 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rouquier Philippe 2007-03-24 09:40:24 UTC
In nautilus-cd-burner or hal-device-manager, the maximum burning speed displayed can sometimes be wrong since it's not updated on new medium insertion. That happens when the new medium is not of the same type as the one that was in the drive when HAL started. 

For example:
start hald with a rewritable CDRW. Most of the time the maximum burning speed is 10x. Now insert a writable CDR and the maximum burning speed will still be 10x even though it should be much higher. Restart hald and then the right speed will be displayed.
It also works the other way round.

That's why it seems to me, but I may be wrong, that HAL doesn't ask the drive the maximum speed on new medium insertion.
Comment 1 Danny Kukawka 2007-08-22 11:26:37 UTC
I have submitted two patches to the HAL ML to fix this issue:

http://lists.freedesktop.org/archives/hal/2007-August/009400.html
http://lists.freedesktop.org/archives/hal/2007-August/009401.html
Comment 2 Danny Kukawka 2007-08-28 12:28:36 UTC
fixed in git HEAD now
Comment 3 Rouquier Philippe 2007-08-29 01:19:14 UTC
great thanks.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct.