Bug 906946
| Summary: | eject -i on does not disable hardware button | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Grant <gvfarns> |
| Component: | systemd | Assignee: | udev-maint |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | gvfarns, hannsj_uhl, harald, johannbg, jonathan, kdudka, kzak, lagarcia, lnykryn, mluscon, msekleta, plautrba, systemd-maint, udev-maint, vpavlin, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-02-23 17:45:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Grant
2013-02-02 00:02:29 UTC
OK, little more research has shed some light on this. The udev rule /usr/lib/udev/rules.d/60-cdrom_id.rules hears the hardware button and makes it eject without caring what's in /proc/sys/dev/cdrom/lock or anywhere else.
If you comment out the line
ENV{DISK_EJECT_REQUEST}=="?*", RUN+="cdrom_id --eject-media $devnode", GOTO="cdrom_end"
then everything seems to work as expected. Cdrom still ejects when you want it to but responds to disabling as it should. I don't know enough about udev to know what else it breaks to comment out this line, but it works for me. Smarter udev behavior would be great.
eject works as expected. I am switching the component to udev... This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This bug is still present in Fedora 20. eject -i locks an individual cdrom, /proc is an awkward global interface acting for all cdroms on the system. I don't see a way to query an individual cdrom for the eject -i setting. I'm closing this bug, it is unlikely to get changed/fixed in the kernel, and udev should not use the awkward /proc interface. You can always, as a local customization, copy the udev rules file from /usr/lib to /etc and edit it there. The one in /etc will entirely overwrite the one in /usr/lib. |