[CuBox-I] Keyboard does not function inside XBMC

[321liftoff]

After some updates around July 6, the keyboard stopped functioning inside XBMC. Exiting XMBC to the console prompt shows that the keyboard functions. Stopping and restarting the XBMC service does not resolve the behavior.

[mk01]

@321liftoff

some default rules of udevd were changed and as a result /dev/input/* was 640 root:input(xbian) and looks like xbmc needs RW.

I have not looked more into details so I can't track the specific change but in in last xbian-update (-103) there is /lib/udev/rules.d/99-zz-xbian.rules (derived from 10-local-xbian with just the INPUT relevant three lines).

(10-local-xbian rule file wasn't changed for quite some time).if you confirm it as working, please report back.

[321liftoff]

@mk01
after the updates (including xbian-update version -103) the usb keyboard works. Should I close the issue or do you want to keep open until you determine what change broke the keyboard?

[mk01]

@321liftoff

I would like to but jessie is changing so fast (meaning updates) that maybe until final or at least Betas we keep it that way - overwriting at the end of rule run.

maybe the problem is in changed syntax of "last_rule" as OPTION what was telling udevd to stop processing rules for the specific definition. now it looks like it is ignored.

in any case this will do the job for few week - in between can happen we abandon udevd completely or switch to systemd. nobody knows.
(udevd has become part of systemd. now with installing "udev" we get almost complete installation of systemd but it is also actively started and from upstart and hard dependency for libpam too :-/. I think gentoo devs took udevd, renamed and intent to develop in future as before. unfortunately Debian made core component out of systemd).

ok, too much info for nothing :)
and feel free to keep this open for a while. there are users who don't install updates by default so they find the info here.

[mk01]

this is from today's imx6 img generation:

dpkg: error processing package libpam-systemd:armhf (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of policykit-1:
 policykit-1 depends on libpam-systemd; however:
  Package libpam-systemd:armhf is not configured yet.

dpkg: error processing package policykit-1 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libpam-systemd:armhf
 policykit-1
dpkg: dependency problems prevent configuration of libpam-systemd:armhf:
 libpam-systemd:armhf depends on systemd-sysv | systemd-shim; however:
  Package systemd-sysv is not installed.
  Package systemd-shim is not installed.

we need policykit-1 for XBMC's to provide umount / mount rights for hot-plug devices. policykit-1 dependent on libpam-systemd, this on systemd-sysv. and systemd-sysv conflicts with upstart. how convenient :))