I also ran the i2c_hid module with debug enabled (`modprobe i2c_hid
debug=1`), which gives a bit of insight in what commands are sent to the
touch screen. On a suspend, it seems to send a sleep command. On a
resume, it sends a power on command, followed by a reset command (which
is properly acknowl
I dug around a bit, and found that the touchscreen can also be fixed by
reloading the ic2_hid module.
It also works to reinitialize just the hid driver for the touchscreen
(rather than reloading the entire module) by running:
echo 0018:06CB:77B2.000C > /sys/bus/hid/drivers/hid-multitouch/unbind
e
** Description changed:
I'm not entirely sure this bug belongs in package xinput, but I'm
- following the lead of #1275416, which describes the same symptoms (but
- on other hardware, so likely a different underlying problem).
+ following the lead of
+ https://bugs.launchpad.net/ubuntu/+source/x
Public bug reported:
I'm not entirely sure this bug belongs in package xinput, but I'm
following the lead of #1275416, which describes the same symptoms (but
on other hardware, so likely a different underlying problem).
On this notebook, the touchscreen works well out of the box. But as soon
as I
In case any one else comes across this problem: I had exactly the same
symptoms and found out they were caused by xbindkeys that was started in
the background. Removing my .xbindkeysrc solved the problem for me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
5 matches
Mail list logo