Summary: | Eject button detection doesn't work with drives supporting ATAPI AN | ||
---|---|---|---|
Product: | hal | Reporter: | Robert Hancock <hancockrwd> |
Component: | hald | Assignee: | Danny Kukawka <danny.kukawka> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | danny.kukawka |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Robert Hancock
2009-10-11 15:32:36 UTC
Can you try, in a case where it fails, to call CheckForMedia() on the affected device via dbus_send? Something like that IIRC (you have to use the correct device path): dbus-send --system --print-reply --dest=org.freedesktop.Hal /org/freedesktop/Hal/devices/storage_model_DVD__RW_UJ_857G org.freedesktop.Hal.Device.Storage.Removable.CheckForMedia Would help to know if this may eject the device. Doesn't seem to help, after pressing the eject button in vain: dbus-send --system --print-reply --dest=org.freedesktop.Hal /org/freedesktop/Hal/devices/storage_model_iHAS324___A org.freedesktop.Hal.Device.Storage.Removable.CheckForMedia method return sender=:1.0 -> dest=:1.356 reply_serial=2 boolean false I suspect something is swallowing up the notification without acting on it. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.