Bug#716715: Still reproducible

2020-05-04 Thread atzlinux 肖盛文
Control: |reassign udev|

|
|

在 2020/5/4 下午8:19, Sebastian Leske 写道:
> Unfortunately, the bug is not fixed.
> There is a typo in the bug report:
>
>> This can be fixed by uncommenting the line
>> ENV{DISK_EJECT_REQUEST}=="?*", RUN+="cdrom_id --eject-media $tempnode", 
>> GOTO="cdrom_end"
> This should say: "This can be fixed by COMMENTING the line".
> This is explained in the linked blog post.
>
> As of udev 245.5-1, the line above is still present in
> /lib/udev/rules.d/60-cdrom_id.rules , and "eject -i on" still does not
> lock the eject button.
>
> If the line is removed/commented, "eject -i on" works as expected.
>
> I have reopened this bug. Or maybe this should be filed against udev?

I think so,udev's rule,need to modify.

I'd |reassign this bug to udev.
|

> It's unclear who is "at fault" here...

>
-- 
肖盛文 Faris Xiao
微信:atzlinux
QQ:909868357
铜豌豆 Linux 
基于 Debian 的 Linux 中文桌面操作系统:https://www.atzlinux.com




signature.asc
Description: OpenPGP digital signature


Bug#716715: Still reproducible

2020-05-04 Thread Sebastian Leske
Unfortunately, the bug is not fixed.
There is a typo in the bug report:

> This can be fixed by uncommenting the line
> ENV{DISK_EJECT_REQUEST}=="?*", RUN+="cdrom_id --eject-media $tempnode", 
> GOTO="cdrom_end"

This should say: "This can be fixed by COMMENTING the line".
This is explained in the linked blog post.

As of udev 245.5-1, the line above is still present in
/lib/udev/rules.d/60-cdrom_id.rules , and "eject -i on" still does not
lock the eject button.

If the line is removed/commented, "eject -i on" works as expected.

I have reopened this bug. Or maybe this should be filed against udev?
It's unclear who is "at fault" here...