You are not logged in.
I don't know how to describe it. Some distros are just Pow!, and everything works, and some behave weirdly with my touchpad. The problem is that the mouse isn't crisp and does'nt do what I want, and it is very hard to pinpoint small buttons like X, because it is almost like the touchpad is too sensitive, and every molecule of my finger that touches the pad is registered, instead of only one. I don't know what regulates mouse behaviour, but I know that my mouse works perfectly on Xubuntu, Peppermint, and Tails, and weirdly on Lubuntu, Bunsenlabs and Antergos. Maybe you can find a clue in this info or something. I dunno. It's not a big deal, but I just used Tails and it was like heaven and earth, I had pixel perfect control, and when rebooting back into bunsenlabs, I had trouble tapping the X to close a window.
Please help!
Last edited by thia11 (2018-11-15 17:06:20)
Offline
Do you have the same problem with if you run the live session?
If not, make sure you have configured touchpad in ~/.config/openbox/autostart.
### TOUCHPAD: comment out the next two entries if you don't have one
## Configure touchpad. See 'man synaptics' for more info.
## (Now might be using libinput instead of synaptics.)
synclient VertEdgeScroll=1 HorizEdgeScroll=1 TapButton1=1 2>/dev/null
## Disable touchpad while typing
syndaemon -i .5 -K -t -R -d &
### TOUCHPAD END
Have you tried log in as another user, with fresh default profile?
What is our hardware?
// Regards rbh
Offline
Hey, thanks for the response.
I can't run a live session because I had to return the USB.
The code you mentioned appears to already be in my autostart config file for openbox.
BUT I can totally click and do everything with the mouse while typing, so it doesn't appear to work.
I know it's an older asus x series, but all stickers are scrached, so I dunno what exactly it is. Looks like 540.
Um, how do I make new users?
Offline
show us the output of
synclient
Offline
show us the output of
synclient
This is the output:
Couldn't find synaptics properties. No synaptics driver loaded?
This looks like a major clue. Maybe something isn't even working D:
Offline
Have you got xserver-xorg-input-synaptics installed?
Last edited by malm (2018-11-11 13:10:55)
Offline
Have you got xserver-xorg-input-synaptics installed?
Nope. Alt + F3 didn't list it, and in the synaptics file manager, it says that that package isn't installed.
Should it be?
Why isn't it?
Is it my fault, or my computer's or something?
Offline
This is the output:
Couldn't find synaptics properties. No synaptics driver loaded?This looks like a major clue. Maybe something isn't even working D:
not all touchpads are synaptic.
next:
xinput list --long
Offline
malm wrote:Have you got xserver-xorg-input-synaptics installed?
Nope. Alt + F3 didn't list it, and in the synaptics file manager, it says that that package isn't installed.
Should it be?
Why isn't it?
Is it my fault, or my computer's or something?
A-F3 wouldn't list it, because it is a package, not an executable. You could do
apt-cache policy xserver-xorg-input-synaptics
You may need to wait for @johnraff et al, who know most about the BL setup, but IIRC libinput has superceded xserver-xorg-input-synaptics, and the synclient line in autostart is a legacy command for those touchpads which need it.
Try installing the package, then log out/in and see...
sudo apt-get update && sudo apt-get install xserver-xorg-input-synaptics
Be Excellent to Each Other...
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
^ what @damo said.
It’s been discussed a few times in this forum. I tried to drop synaptics a while ago and use libinput, but found that it was quite rough with my laptop.
It’s peculiar that you haven’t already got the synaptics package on your BL box. You’ll have to try to install it as @damo suggested.
Offline
I know it's an older asus x series, but all stickers are scrached, so I dunno what exactly it is. Looks like 540.
I like dmidecode to read the pc's dmi table.
In a root terminal execute:
dmidecode --type system
Um, how do I make new users?
as root execute:
adduser username
// Regards rbh
Offline
not all touchpads are synaptic.
next:
xinput list --long
Virtual core pointer id=2 [master pointer (3)]
Reporting 7 classes:
Class originated from: 11. Type: XIButtonClass
Buttons supported: 10
Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" None None None
Button state:
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 2:
Label: Rel Horiz Scroll
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 3:
Label: Rel Vert Scroll
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 11. Type: XIScrollClass
Scroll info for Valuator 2
type: 2 (horizontal)
increment: 15.000000
flags: 0x0
Class originated from: 11. Type: XIScrollClass
Scroll info for Valuator 3
type: 1 (vertical)
increment: 15.000000
flags: 0x0
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
Reporting 3 classes:
Class originated from: 4. Type: XIButtonClass
Buttons supported: 10
Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" None None None
Button state:
Class originated from: 4. Type: XIValuatorClass
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 4. Type: XIValuatorClass
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
⎜ ↳ FTE1001:00 0B05:0101 id=11 [slave pointer (2)]
Reporting 7 classes:
Class originated from: 11. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"
Button state:
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 2:
Label: Rel Horiz Scroll
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 11. Type: XIValuatorClass
Detail for Valuator 3:
Label: Rel Vert Scroll
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 11. Type: XIScrollClass
Scroll info for Valuator 2
type: 2 (horizontal)
increment: 15.000000
flags: 0x0
Class originated from: 11. Type: XIScrollClass
Scroll info for Valuator 3
type: 1 (vertical)
increment: 15.000000
flags: 0x0
⎣ Virtual core keyboard id=3 [master keyboard (2)]
Reporting 1 classes:
Class originated from: 13. Type: XIKeyClass
Keycodes supported: 248
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 5. Type: XIKeyClass
Keycodes supported: 248
↳ Power Button id=6 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 6. Type: XIKeyClass
Keycodes supported: 248
↳ Asus Wireless Radio Control id=7 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 7. Type: XIKeyClass
Keycodes supported: 248
↳ Video Bus id=8 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 8. Type: XIKeyClass
Keycodes supported: 248
↳ Sleep Button id=9 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 9. Type: XIKeyClass
Keycodes supported: 248
↳ USB2.0 VGA UVC WebCam id=10 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 10. Type: XIKeyClass
Keycodes supported: 248
↳ Asus WMI hotkeys id=12 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 12. Type: XIKeyClass
Keycodes supported: 248
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
Reporting 1 classes:
Class originated from: 13. Type: XIKeyClass
Keycodes supported: 248
This is it :S Apparently, there should be some touchpads here, but I can't see them. Are the virtual core pointer thingies touchpads?
@damo I was wrong. I DO have the xserver-xorg-input-synaptics installed. I mistook xserver-xorg-input-synaptics-dev for it, which is not installed.
Offline
If you have xserver-xorg-input-synaptics installed you should be able to post the output of
synclient
Also look at https://wiki.debian.org/LibinputTouchpad and https://wiki.debian.org/SynapticsTouchpad
Be Excellent to Each Other...
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
damo: going in circles.
see post #5.
my suspicion is that it's one of the few topuchpads that synaptics can't work with.
my method helped to find that out, but doesn't really tell us which device it is.
sorry to be such an idiot; try
xinput list
show us.
this should tell you which id is the touchpad, and how it's called.
with that id in mind, you can make some adjustments with xinput.
just as a n example, i have this in my autostart:
xinput --set-prop 12 'libinput Accel Speed' 1
(increases accelaration speed)
this is finicky, and you should read up on it (both your model and how xinput works generally) if you want to be succesful.
Offline
try
xinput list
show us.
It's the same as above, just without the extra fluff.
Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ FTE1001:00 0B05:0101 id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Asus Wireless Radio Control id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ USB2.0 VGA UVC WebCam id=10 [slave keyboard (3)]
↳ Asus WMI hotkeys id=12 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
That's so weird. Why does it work on some distros and not on others? Because of firmware, or because of these synaptic and libunput thingies?
Offline
@thia11: now execute
$ xinput --test 11
and try to use touchpad (or mouse?) - press it, or move it.
On my system it shows something like:
button press 1
button release 1
button press 1
button release 1
motion a[0]=1240 a[1]=1116
motion a[0]=1243 a[1]=1113
motion a[0]=1246 a[1]=1110
motion a[0]=1249 a[1]=1107
.... and so on
If it does show similar output, then this device number (11) is your touchpad (or mouse?). And in this case, configuring the touchpad (or mouse?) is done by series of 'xinput --set-prop' statements.
Last edited by iMBeCil (2018-11-13 13:51:54)
Postpone all your duties; if you die, you won't have to do them ..
Offline
...
That's so weird. Why does it work on some distros and not on others? Because of firmware, or because of these synaptic and libunput thingies?
Probably yes. Why not boot one you know that works, and see what they use to set up the touchpad? If it is synaptic/libinput/xorg configs, then copy those files into your BL install (backup the defaults first!)
Be Excellent to Each Other...
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
@thia11: now execute
$ xinput --test 11
Yep, there are a bunch of numbers for coordinates, and there are [1] when I click stuff, when the number is usually [0] when just moving mouse.
Is this conclusive? Do we know this is it now?
What should I do now? Is this weird or normal?
Last edited by thia11 (2018-11-13 17:52:00)
Offline
^This is completely normal. It means your touchpad works. (It would be analogous with the mouse ...)
Now, I would execute:
$ xinput --list-props 11
On my laptop it outputs:
Device 'bcm5974':
Device Enabled (148): 1
Coordinate Transformation Matrix (150): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Tapping Enabled (286): 1
libinput Tapping Enabled Default (287): 0
libinput Tapping Drag Enabled (288): 1
libinput Tapping Drag Enabled Default (289): 1
libinput Tapping Drag Lock Enabled (290): 0
libinput Tapping Drag Lock Enabled Default (291): 0
libinput Tapping Button Mapping Enabled (292): 1, 0
libinput Tapping Button Mapping Default (293): 1, 0
libinput Natural Scrolling Enabled (294): 0
libinput Natural Scrolling Enabled Default (295): 0
libinput Disable While Typing Enabled (296): 1
libinput Disable While Typing Enabled Default (297): 1
libinput Scroll Methods Available (298): 1, 1, 0
libinput Scroll Method Enabled (299): 1, 0, 0
libinput Scroll Method Enabled Default (300): 1, 0, 0
libinput Click Methods Available (301): 1, 1
libinput Click Method Enabled (302): 0, 1
libinput Click Method Enabled Default (303): 0, 1
libinput Middle Emulation Enabled (304): 0
libinput Middle Emulation Enabled Default (305): 0
libinput Accel Speed (306): 0.000000
libinput Accel Speed Default (307): 0.000000
libinput Left Handed Enabled (308): 0
libinput Left Handed Enabled Default (309): 0
libinput Send Events Modes Available (271): 1, 1
libinput Send Events Mode Enabled (272): 0, 0
libinput Send Events Mode Enabled Default (273): 0, 0
Device Node (274): "/dev/input/event9"
Device Product ID (275): 1452, 611
libinput Drag Lock Buttons (310): <no items>
libinput Horizontal Scroll Enabled (311): 1
Now, you can adjust particular settings with:
$ xinput --set-prop 11 <property> <value>
where <property> is one of the properties returned by '--list-props', and <value> is desired value.
Unfortunately, I have no idea what to change and how. I remember once I have set my touchpad with 'xinput' to recognize single-finger-tap, and double-finger-tap, but I forgot it.
It it up to you to study a bit what do you want to achieve, study 'man xinput', and possibly google something like 'xinput adjust sensitivity touchpad' or similar ... Or somebody here has more experience with this: you should post output of your 'xinput --list-props 11'.
Last edited by iMBeCil (2018-11-13 20:32:31)
Postpone all your duties; if you die, you won't have to do them ..
Offline
⎜ ↳ FTE1001:00 0B05:0101 id=11 [slave pointer (2)]
what's with the weird characters?
anyhow, on my system this shows the make/model of the device.
you have to find out more about this device.
maybe
dmesg|grep '0B05:0101'
???
Offline
thia11 wrote:⎜ ↳ FTE1001:00 0B05:0101 id=11 [slave pointer (2)]
what's with the weird characters?
anyhow, on my system this shows the make/model of the device.
you have to find out more about this device.
maybedmesg|grep '0B05:0101'
???
the weird characters are just the arrows you get with the command, but messed up because some reasons
this command gives me:
dmesg: read kernel buffer failed: Operation not permitted
iMBeCil and I concluded that the device uses xinput, so maybe we can start from there.
Offline
^ You need to use 'sudo' with dmesg, with recent Debian releases.
Be Excellent to Each Other...
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
this command gives me:
dmesg: read kernel buffer failed: Operation not permitted
Use
$ sudo dmesg|grep '0B05:0101'
('dmesg' requires elevated privileges).
EDIT: ah ... ninja'd by damo.
Last edited by iMBeCil (2018-11-14 09:43:57)
Postpone all your duties; if you die, you won't have to do them ..
Offline
iMBeCil and I concluded that the device uses xinput, so maybe we can start from there.
Please, post output of
$ xinput --list-props 11
In the meantime, as ohnonot suggested in post #14, try something like
$ xinput --set-prop 11 'libinput Accel Speed' 1
to change the acceleration speed (whatever it is). Try with different values instead of '1' and see if touchpad behaviour changes. Adjust according to personal preference.
Last edited by iMBeCil (2018-11-14 09:49:08)
Postpone all your duties; if you die, you won't have to do them ..
Offline
Please, post output of
$ xinput --list-props 11
Here it is:
Device 'FTE1001:00 0B05:0101':
Device Enabled (140): 1
Coordinate Transformation Matrix (150): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Accel Speed (278): 0.000000
libinput Accel Speed Default (279): 0.000000
libinput Accel Profiles Available (280): 1, 1
libinput Accel Profile Enabled (281): 1,0
libinput Accel Profile Enabled Default (282): 1,0
libinput Natural Scrolling Enabled (283): 0
libinput Natural Scrolling Enabled Default (284): 0
libinput Send Events Modes Available (263): 1, 0
libinput Send Events Mode Enabled (264): 0, 0
libinput Send Events Mode Enabled Default (265): 0, 0
libinput Left Handed Enabled (285): 0
libinput Left Handed Enabled Default (286): 0
libinput Scroll Methods Available (278): 0, 0, 1
libinput Scroll Method Enabled (288): 0, 0, 0
libinput Scroll Method Enabled Default (289): 0, 0, 0
libinput Button Scrolling Button (290): 0
libinput Button Scrolling Button Default (291): 0
Device Node (266): "/dev/input/event1"
Device Product ID (267): 2821, 257
libinput Drag Lock Buttons (292): <no items>
libinput Horizontal Scroll Enabled (293): 1
I notice some things are significantly different than on your computer. Like button scrolling button, methods available, I don't have disable while typing, and accel stuff is different, and I have a "profile". Why are my settings so fucky?
Offline