New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permissions #7
Comments
What OS/environment are you trying to run this under? You must not run this as root. This utility just wraps itself around the standard libinput-debug-events program so if you can't run that as your normal user then this utility won't work. You need to add yourself to the input group so that libinput-debug-events can read |
archlinux with gnome 3.18.2 |
@nos1609 Did you add yourself to the input group? Did it fix the problem? Use That gnome version on Arch is from 2015. Any reason you are not updating your system? What kind of machine is this? |
I presume that was the problem so I made the README a little more explicit about this with commit f415dfa. |
I have the same problem also I ran |
Note the instructions say to run that command and then log out and back in. Did you do that? |
Hi, I did that but I getting this message
|
Please list the output of |
|
There is no touchpad listed there. What model of laptop is this? There is a mouse reported so perhaps unplug that and run the command again. |
Dell Latitude E7470, it's a laptop |
What about my mouse question? |
I don't use a mouse or external peripheral , I use the built in touchpad, also, in web browser respond with two fingers scroll, :( |
So your touchpad is reported as a mouse it seems. Run the following command and do some 3 and 4 finger swipes and pinches to see if gestures are reported.
Note that device path may change between reboots. Get the current path using the |
Hi, I did that but only recognize two fingers |
Ok, that is a fairly new laptop. If you look around your will see others reporting on various Linux forums and bugtrackers that their similar model Dell laptops are reporting their touchpad as a mouse. E.g. see https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1590590 and http://en.community.dell.com/techcenter/os-applications/f/4613/t/19982526. Unfortunately you have to wait for a Linux kernel update. For the first 3 months after I got my Dell XPS 13 I compiled up my own kernel with various little patches for issues like this sad to say. Eventually, everything was working well by default. |
Ohh hehehe ok, I will wait, I don't have experience compiling kernel or libs hehehe :( thank you so much!! |
Hey so for me, I figured out which input device is the correct one: (NOTE: I am using the Razer Blade Pro 2017)
Which is weird because as you can see, I would not have expected this device to be the trackpad. I tested this device using the
But no recognizing any other gestures. |
I had the same problem on Ubuntu 17.04. Despite adding the user to group, logging out and logging back in and even rebooting, it continued to give the same error. libinput-ilist-devices would continue to give permission denied but would work with sudo. I am not sure if I did the right thing by changing it, but then this is my personal system with no one else using it. Can someone confirm what should be the owner:group and permission of /dev/input/event* files? Thanks |
I found my culprit.. an app called "WhatPulse", which tracks the number of keystrokes and mouse clicks. |
Hello i have the same problem that haroldSanchezb, i have Xiaomi NoteBook Pro Device: Power Button Device: Video Bus Device: Power Button Device: Lid Switch Device: Video Bus Device: Logitech M510 Device: XiaoMi USB 2.0 Webcam: XiaoMi U Device: ETD2303:00 04F3:3083 Touchpad Device: Intel HID events Device: HDA Intel PCH Headphone Device: HDA Intel PCH HDMI/DP,pcm=3 Device: HDA Intel PCH HDMI/DP,pcm=7 Device: HDA Intel PCH HDMI/DP,pcm=8 Device: HDA Intel PCH HDMI/DP,pcm=9 Device: HDA Intel PCH HDMI/DP,pcm=10 Device: AT Translated Set 2 keyboard Device: ETPS/2 Elantech Touchpad please any idea |
@retsel89 this closed bug is 3 years old. Please read and follow the TROUBLESHOOTING section in the README thoroughly and then raise a new bug if you think appropriate (providing all the data asked for there). |
Running on arch as a simple user fails
sudo output claims that no config files found
So far, a complete reboot is needed for wayland
The text was updated successfully, but these errors were encountered: