udev 182 not responding to the DISK_EJECT_REQUEST
All,
we have the following issue reported by a gentoo user.
https://bugs.gentoo.org/show_bug.cgi?id=409563
I realize that we no longer create /dev/dvd, but what about responding to EJECT_REQUEST?
Thanks,
William
Quoted 6 lines · William Hubbs
we have the following issue reported by a gentoo user.
https://bugs.gentoo.org/show_bug.cgi?id@9563
I realize that we no longer create
/dev/dvd, but what about responding toEJECT_REQUEST?
It should all work. DISK_EJECT_REQUEST=1 handling work fine for me here.
Kay
Hi Kay,
Quoted 9 lines · Kay Sievers
Quoted 6 lines · William Hubbs
we have the following issue reported by a gentoo user.
https://bugs.gentoo.org/show_bug.cgi?id=409563
I realize that we no longer create
/dev/dvd, but what about responding toEJECT_REQUEST?It should all work. DISK_EJECT_REQUEST=1 handling work fine for me here.
A solution I found (I saw that I did not have a /dev/dvd symbolic link) was to rm the /etc/udev/rules.d/70-persistent-cd.rules file then restart udev. That brought the link back for me.
However, now we have a continuation of this report where a gentoo developer is saying that doing that killed his keyboard settings in xfce.
Do you have any suggestions?
William
Quoted 11 lines · William Hubbs
Quoted 9 lines · Kay Sievers
Quoted 6 lines · William Hubbs
we have the following issue reported by a gentoo user.
https://bugs.gentoo.org/show_bug.cgi?id=409563
I realize that we no longer create
/dev/dvd, but what about responding toEJECT_REQUEST?It should all work. DISK_EJECT_REQUEST=1 handling work fine for me here.
Quoted 7 lines
A solution I found (I saw that I did not have a
/dev/dvdsymbolic link) was to rm the/etc/udev/rules.d/70-persistent-cd.rulesfile then restart udev. That brought the link back for me.However, now we have a continuation of this report where a gentoo developer is saying that doing that killed his keyboard settings in xfce.
I was advised that we should update our init scripts on gentoo so that if someone wants to restart udev we use --action=change on the udevadm trigger commands when we restart instead of --action=add. I've been told that will take care of the keyboard issue.
But, both people are reporting on the bug that they do not have a /dev/dvd symbolic link after running the solution I suggested, and they have posted the device information on the bug.
Do you have any other suggestions?
Thanks,
William