We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello there.
In am facing this problem a long time now. Any how, the eject funktion does not work at all.
dev.cdrom.lock=0 is set and xbmc is in cdrom group too, the log tells me
3:33:22 T:140635390674816 DEBUG: OnKey: return (f00d) pressed, action is Select 13:33:22 T:140635390674816 DEBUG: ExecuteXBMCAction : Translating EjectTray() 13:33:22 T:140635390674816 DEBUG: ExecuteXBMCAction : To EjectTray()
nothing happens
If i run a
"eject -i off /dev/sr0"
before, it works using the gui like it should.
I would recommend to solve this - anybody an idea for a workaround so far?
The text was updated successfully, but these errors were encountered:
editing the /lib/dev/ruled.d/60-cdrom_id.rules does the trick: changed
IMPORT{program}="cdrom_id --lock-media $tempnode"
to
IMPORT{program}="cdrom_id $tempnode"
Sorry, something went wrong.
We're not yet using github issues for user support. Please either go to forum.xbmc.org or trac.xbmc.org for that.
If you have a fix, feel free to open a pull request.
Disable volume control if audio is passthrough
f0fe1e1
Fixes xbmc#858
No branches or pull requests
Hello there.
In am facing this problem a long time now. Any how, the eject funktion does not work at all.
dev.cdrom.lock=0 is set and xbmc is in cdrom group too, the log tells me
3:33:22 T:140635390674816 DEBUG: OnKey: return (f00d) pressed, action is Select
13:33:22 T:140635390674816 DEBUG: ExecuteXBMCAction : Translating EjectTray()
13:33:22 T:140635390674816 DEBUG: ExecuteXBMCAction : To EjectTray()
nothing happens
If i run a
"eject -i off /dev/sr0"
before, it works using the gui like it should.
I would recommend to solve this - anybody an idea for a workaround so far?
The text was updated successfully, but these errors were encountered: