This just happened here with eject-2.1.5, but using "eject -i off" as suggested by zheoffec in comment #2 helped - thanks!
This just happened here with eject-2.1.5, but using "eject -i off" as suggested by zheoffec in comment #2 helped - thanks!