[Touch-packages] [Bug 1406952] Re: systemd-udevd[471]: Error calling EVIOCSKEYCODE: Invalid argument

2015-01-15 Thread mark wade
Last three boots yielded: 1st boot:systemd-udevd[283]: Error calling EVIOCSKEYCODE: Invalid argument 2nd boot: systemd-udevd[295]: Error calling EVIOCSKEYCODE: Invalid argument 3rd boot: systemd-udevd[287]: Error calling EVIOCSKEYCODE: Invalid argument touching the file did not prevent a

[Touch-packages] [Bug 1406952] Re: systemd-udevd[471]: Error calling EVIOCSKEYCODE: Invalid argument

2015-01-14 Thread mark wade
Maybe I'm not supposed to post here? But since I did I'll finish up. It seems to come and go on it's own now requiring no action from me, mostly it's gone. The last was January 12 with: systemd-udevd[287]: Error calling EVIOCSKEYCODE: Invalid argument but successive boots yield no further

[Touch-packages] [Bug 1406952] Re: systemd-udevd[471]: Error calling EVIOCSKEYCODE: Invalid argument

2015-01-09 Thread mark wade
I neglected to say I've restored the original /lib/udev/hwdb.d/60-keyboard.hwdb with all its entries intact and have rebooted a few times with no errors. Next error I'll touch the file and reboot and see. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1406952] Re: systemd-udevd[471]: Error calling EVIOCSKEYCODE: Invalid argument

2015-01-09 Thread mark wade
I've completely emptied /lib/udev/hwdb.d/60-keyboard.hwdb and still get boot errors of the sort: systemd-udevd[285]: Error calling EVIOCSKEYCODE: Invalid argument Each time I edited 60-keyboard.hwdb the error would go away next boot and some number of successive boots but would return with a