2015-01-11, 14:06
On my Linux machine I start KODI through an entry in .xinitrc
and since KODI v14 helix, I can't use my keyboard anymore after I ran an external program, e. g. when I quit a program which I started through advanced launcher.
I knew this kind of problem from ratpoison WM, but I know how to solve it there, so I tried to use ratpoison with KODI together (I did this with XBMC 12-13 on various occasions and it always worked), and I changed my .xinitrc to
However, after this I can't use my keyboard at all in KODI.
Evidently KODI changed its way of handling window/input focus (at least I deduce this from the problem I had with ratpoison), I don't know if this is a bug or a feature, but can anyone tell me what changed in v14, and thus what causes this behavior?
What is the preferred way to start a window manager with KODI on Linux now?
Code:
exec kodi --standalone
and since KODI v14 helix, I can't use my keyboard anymore after I ran an external program, e. g. when I quit a program which I started through advanced launcher.
I knew this kind of problem from ratpoison WM, but I know how to solve it there, so I tried to use ratpoison with KODI together (I did this with XBMC 12-13 on various occasions and it always worked), and I changed my .xinitrc to
Code:
ratpoison &
exec kodi --standalone
However, after this I can't use my keyboard at all in KODI.
Evidently KODI changed its way of handling window/input focus (at least I deduce this from the problem I had with ratpoison), I don't know if this is a bug or a feature, but can anyone tell me what changed in v14, and thus what causes this behavior?
What is the preferred way to start a window manager with KODI on Linux now?