Actually, yeah, that 204 I got from some wiki page. It seems the possible keycodes are:
$ xmodmap -pke | grep Eject keycode 169 = XF86Eject NoSymbol XF86Eject keycode 170 = XF86Eject XF86Eject XF86Eject XF86Eject keycode 174 = XF86AudioStop XF86Eject XF86AudioStop XF86Eject The fact that 174 is potentially both XF86AudioStop and XF86Eject makes me somewhat concerned but it doesn't look like we're using XF86AudioStop. It's possible some other user is using this and adding something for XF86Eject will maybe break it, which is not necessarily ideal. We could just use the specific keycodes (169, 170) and ignore 174 and let that be a known bug. That's probably my inclination and it wouldn't negatively affect you, Fritz. I assume you use `eject` on the command line? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768294 Title: "eject" key doesn't open optical drive tray in Openbox To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-next/+bug/1768294/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
