Hi again Michael,
I appreciate your effort to help out triaging but I fear that your
devices_after is of no use to as, the issue isn't there anymore. So its the
same as devices_before.
Regarding your another issue, It would be good if you could file another
new bug report for that. Also, as
Hi Michael Watson,
Thanks for reporting bug and helping us to make ubuntu, even better. For
developers to work on this bug we want to have additional information from you,
about the bug.
I hope if you could upload the logs of
$ cat /proc/bus/input/devices
both before and after
Alright here is the input device list; I need a little bit more time to
figure out how to get any other useful information since the keyboard
stops working as soon as I recreate the issue. I can copy my Xorg log,
but it doesn't look like anything useful has been captured in them.
** Attachment
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/667430/+attachment/1715819/+files/Xorg.0.log
--
Hp Tx2510us synaptic touch pad does not work properly after it has been
disabled/reenabled
https://bugs.launchpad.net/bugs/667430
You
Michael,
I'm more interested in the devices_after file. I hope you could figure out
something to get the log from your machine.
--
Hp Tx2510us synaptic touch pad does not work properly after it has been
disabled/reenabled
https://bugs.launchpad.net/bugs/667430
You received this bug
If you still unable to get the log file, consider using evtest by
switching into a VT using CTrl+Alt+F2. Then use the button to enable
disable the touchpad and see how events respond to that.
Remember DebuggingTouchpad guide is there to help you out.
--
Hp Tx2510us synaptic touch pad does not
Alright looking through the Xorg log it said that my touchpad was mapped
to /dev/input/event11 so that is what I used evtest for. Evtest didn't
do anything when turning the touchpad on and off, which I don't think it
is meant to, but just in case it didn't. It showed values for clicking
and moving
Aaaann for some reason after installing evtest and doing system
updates that only had empathy and some other crap not related to X as
far as I know the touch pad can enable and disable via the hard switch,
and works just fine now.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Ok then, in any case you bug seems to be solved by itself. So I'm
closing the bug, if however you encounter the bug again and want to
reopen the bug, you can do so any time, by setting the status as New
again.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Invalid = New
**
Alright it has been happening, and I got an output in a VT for
/proc/bus/input/devices finally. I also want to note that when it
doesn't have this issue the mouse seems to have a really hard time
moving according to user inputs (goes all over the place) for a while
(~20 seconds) until it calms
--
Hp Tx2510us synaptic touch pad does not work properly after it has been
disabled/reenabled
https://bugs.launchpad.net/bugs/667430
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in ubuntu.
Upon making sure everything in what I said was accurate I tried
disabling and reenabling the touch pad again, and it seems to affect my
ability to use anything on the gnome desktop, but if i have an internet
browser window open I can still affect it with my actions. The keyboard
will not even work
12 matches
Mail list logo
