#libinput — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #libinput, aggregated by home.social.
-
The GitHub user bry4n12255 is working on #AnbryInput, a small experimental Xorg/#XLibre input driver focused on low-latency mouse and keyboard input. In his measurements, it performed roughly 20-35% better than #libinput. #Xingsday https://github.com/bry4n12255/anbryinput
-
The GitHub user bry4n12255 is working on #AnbryInput, a small experimental Xorg/#XLibre input driver focused on low-latency mouse and keyboard input. In his measurements, it performed roughly 20-35% better than #libinput. #Xingsday https://github.com/bry4n12255/anbryinput
-
The GitHub user bry4n12255 is working on #AnbryInput, a small experimental Xorg/#XLibre input driver focused on low-latency mouse and keyboard input. In his measurements, it performed roughly 20-35% better than #libinput. #Xingsday https://github.com/bry4n12255/anbryinput
-
The GitHub user bry4n12255 is working on #AnbryInput, a small experimental Xorg/#XLibre input driver focused on low-latency mouse and keyboard input. In his measurements, it performed roughly 20-35% better than #libinput. #Xingsday https://github.com/bry4n12255/anbryinput
-
why do I only come across the most weird bugs that no one has ever talked about before
anyways if ANYONE knows ANY pointers on what is going on here, I will be extremely happy & give you 5 tubs of ice cream
#cachyos #wayland #libinput #bug
https://discuss.cachyos.org/t/possible-kernel-issue-with-mpp-pens-libinput/32357 -
why do I only come across the most weird bugs that no one has ever talked about before
anyways if ANYONE knows ANY pointers on what is going on here, I will be extremely happy & give you 5 tubs of ice cream
#cachyos #wayland #libinput #bug
https://discuss.cachyos.org/t/possible-kernel-issue-with-mpp-pens-libinput/32357 -
BOOSTS NEEDED, HELP WANTED:
I came across a very odd issue that I thought was Krita specific, but turns out it's not.
https://krita-artists.org/t/edit-pressure-input-is-capped-only-when-using-rubber-key-on-stylus/185000/10?u=wakocima
I have no idea how to troubleshoot this. I'm not experienced with #wayland and #libinput . To clarify, I am using a 2-in-1 MSI Summit, together with Renaisser 520C. Things have worked fine before, and suddenly broke down -- I have no idea where to pinpoint the time things broke, but I did not do any system upgrades -- I did one AFTER encountering the issue. -
BOOSTS NEEDED, HELP WANTED:
I came across a very odd issue that I thought was Krita specific, but turns out it's not.
https://krita-artists.org/t/edit-pressure-input-is-capped-only-when-using-rubber-key-on-stylus/185000/10?u=wakocima
I have no idea how to troubleshoot this. I'm not experienced with #wayland and #libinput . To clarify, I am using a 2-in-1 MSI Summit, together with Renaisser 520C. Things have worked fine before, and suddenly broke down -- I have no idea where to pinpoint the time things broke, but I did not do any system upgrades -- I did one AFTER encountering the issue. -
:(
It's pretty fundamental to use of mouse that when you are clicking a mouse button, your hand moves the mouse and this may register in the sensor, causing a drag event to register. The higher quality sensor (high DPI), the more likely this is.
There used to be a "drag start distance" setting in Linux desktop environments, but now it's missing (specifically #KDE Plasma 6 but probably elsewhere too).
#libinput is the backend of mouse handling with #Wayland, I couldn't find this setting in it.
-
:(
It's pretty fundamental to use of mouse that when you are clicking a mouse button, your hand moves the mouse and this may register in the sensor, causing a drag event to register. The higher quality sensor (high DPI), the more likely this is.
There used to be a "drag start distance" setting in Linux desktop environments, but now it's missing (specifically #KDE Plasma 6 but probably elsewhere too).
#libinput is the backend of mouse handling with #Wayland, I couldn't find this setting in it.
-
:(
It's pretty fundamental to use of mouse that when you are clicking a mouse button, your hand moves the mouse and this may register in the sensor, causing a drag event to register. The higher quality sensor (high DPI), the more likely this is.
There used to be a "drag start distance" setting in Linux desktop environments, but now it's missing (specifically #KDE Plasma 6 but probably elsewhere too).
#libinput is the backend of mouse handling with #Wayland, I couldn't find this setting in it.
-
:(
It's pretty fundamental to use of mouse that when you are clicking a mouse button, your hand moves the mouse and this may register in the sensor, causing a drag event to register. The higher quality sensor (high DPI), the more likely this is.
There used to be a "drag start distance" setting in Linux desktop environments, but now it's missing (specifically #KDE Plasma 6 but probably elsewhere too).
#libinput is the backend of mouse handling with #Wayland, I couldn't find this setting in it.
-
I've already assumed that my touch pad was broken (or the driver was buggy) because after a tap-and-drag action, the mouse button was not released when releasing the finger from the touch pad.
It was "sticky", e.g. after marking multiple lines of text.
Just found out that this was introduced a while ago in Sway (to follow libinput recommendations):
https://github.com/swaywm/sway/commit/bbadf9b8b10d171a6d5196da7716ea50ee7a6062
Setting "drag_lock disabled" in the touch pad's config fixes this. 😌
-
I've already assumed that my touch pad was broken (or the driver was buggy) because after a tap-and-drag action, the mouse button was not released when releasing the finger from the touch pad.
It was "sticky", e.g. after marking multiple lines of text.
Just found out that this was introduced a while ago in Sway (to follow libinput recommendations):
https://github.com/swaywm/sway/commit/bbadf9b8b10d171a6d5196da7716ea50ee7a6062
Setting "drag_lock disabled" in the touch pad's config fixes this. 😌
-
I've already assumed that my touch pad was broken (or the driver was buggy) because after a tap-and-drag action, the mouse button was not released when releasing the finger from the touch pad.
It was "sticky", e.g. after marking multiple lines of text.
Just found out that this was introduced a while ago in Sway (to follow libinput recommendations):
https://github.com/swaywm/sway/commit/bbadf9b8b10d171a6d5196da7716ea50ee7a6062
Setting "drag_lock disabled" in the touch pad's config fixes this. 😌
-
I've already assumed that my touch pad was broken (or the driver was buggy) because after a tap-and-drag action, the mouse button was not released when releasing the finger from the touch pad.
It was "sticky", e.g. after marking multiple lines of text.
Just found out that this was introduced a while ago in Sway (to follow libinput recommendations):
https://github.com/swaywm/sway/commit/bbadf9b8b10d171a6d5196da7716ea50ee7a6062
Setting "drag_lock disabled" in the touch pad's config fixes this. 😌
-
I've already assumed that my touch pad was broken (or the driver was buggy) because after a tap-and-drag action, the mouse button was not released when releasing the finger from the touch pad.
It was "sticky", e.g. after marking multiple lines of text.
Just found out that this was introduced a while ago in Sway (to follow libinput recommendations):
https://github.com/swaywm/sway/commit/bbadf9b8b10d171a6d5196da7716ea50ee7a6062
Setting "drag_lock disabled" in the touch pad's config fixes this. 😌
-
In today's edition of FDO sabotaging the desktop experience: #libinput spiking a single CPU core to 100% when the mouse is moved and dropping a crapton of events when twitching it in shooter games.
Uninstall the libinput Xorg input driver directly using evdev instead; and lo and behold: No CPU spikes and perfectly smooth input.
Can the whole libinput+Wayland+"modern Linux desktop" fad (that's holding back true progress for 15 years now) now please go collectively go and die in a fire?
-
In today's edition of FDO sabotaging the desktop experience: #libinput spiking a single CPU core to 100% when the mouse is moved and dropping a crapton of events when twitching it in shooter games.
Uninstall the libinput Xorg input driver directly using evdev instead; and lo and behold: No CPU spikes and perfectly smooth input.
Can the whole libinput+Wayland+"modern Linux desktop" fad (that's holding back true progress for 15 years now) now please go collectively go and die in a fire?
-
In today's edition of FDO sabotaging the desktop experience: #libinput spiking a single CPU core to 100% when the mouse is moved and dropping a crapton of events when twitching it in shooter games.
Uninstall the libinput Xorg input driver directly using evdev instead; and lo and behold: No CPU spikes and perfectly smooth input.
Can the whole libinput+Wayland+"modern Linux desktop" fad (that's holding back true progress for 15 years now) now please go collectively go and die in a fire?
-
In today's edition of FDO sabotaging the desktop experience: #libinput spiking a single CPU core to 100% when the mouse is moved and dropping a crapton of events when twitching it in shooter games.
Uninstall the libinput Xorg input driver directly using evdev instead; and lo and behold: No CPU spikes and perfectly smooth input.
Can the whole libinput+Wayland+"modern Linux desktop" fad (that's holding back true progress for 15 years now) now please go collectively go and die in a fire?
-
In today's edition of FDO sabotaging the desktop experience: #libinput spiking a single CPU core to 100% when the mouse is moved and dropping a crapton of events when twitching it in shooter games.
Uninstall the libinput Xorg input driver directly using evdev instead; and lo and behold: No CPU spikes and perfectly smooth input.
Can the whole libinput+Wayland+"modern Linux desktop" fad (that's holding back true progress for 15 years now) now please go collectively go and die in a fire?
-
libinput now supports LUA plugins. Sounds quite exciting. It makes customization of input devices much more robust, granular and programming friendly (looking at existing evdev events remapping tools).
https://wayland.freedesktop.org/libinput/doc/latest/lua-plugins.html
https://www.phoronix.com/news/libinput-1.30-Released -
libinput now supports LUA plugins. Sounds quite exciting. It makes customization of input devices much more robust, granular and programming friendly (looking at existing evdev events remapping tools).
https://wayland.freedesktop.org/libinput/doc/latest/lua-plugins.html
https://www.phoronix.com/news/libinput-1.30-Released -
libinput now supports LUA plugins. Sounds quite exciting. It makes customization of input devices much more robust, granular and programming friendly (looking at existing evdev events remapping tools).
https://wayland.freedesktop.org/libinput/doc/latest/lua-plugins.html
https://www.phoronix.com/news/libinput-1.30-Released -
libinput now supports LUA plugins. Sounds quite exciting. It makes customization of input devices much more robust, granular and programming friendly (looking at existing evdev events remapping tools).
https://wayland.freedesktop.org/libinput/doc/latest/lua-plugins.html
https://www.phoronix.com/news/libinput-1.30-Released -
libinput now supports LUA plugins. Sounds quite exciting. It makes customization of input devices much more robust, granular and programming friendly (looking at existing evdev events remapping tools).
https://wayland.freedesktop.org/libinput/doc/latest/lua-plugins.html
https://www.phoronix.com/news/libinput-1.30-Released -
Darn, looks like there’s nothing comparable to #xinput in #Wayland. Under #X11, I could temporarily disable my Ergoslider bar mouse with `xinput disable "Ergoslider Mouse"`. Under Wayland, I can only list the devices recognized by #libinput with `sudo libinput list-devices` (and yes, it *does* require sudoing!) but that’s that. #Sad, as the orange buffoon is fond of saying. #Linux #FLOSS
-
Darn, looks like there’s nothing comparable to #xinput in #Wayland. Under #X11, I could temporarily disable my Ergoslider bar mouse with `xinput disable "Ergoslider Mouse"`. Under Wayland, I can only list the devices recognized by #libinput with `sudo libinput list-devices` (and yes, it *does* require sudoing!) but that’s that. #Sad, as the orange buffoon is fond of saying. #Linux #FLOSS
-
Darn, looks like there’s nothing comparable to #xinput in #Wayland. Under #X11, I could temporarily disable my Ergoslider bar mouse with `xinput disable "Ergoslider Mouse"`. Under Wayland, I can only list the devices recognized by #libinput with `sudo libinput list-devices` (and yes, it *does* require sudoing!) but that’s that. #Sad, as the orange buffoon is fond of saying. #Linux #FLOSS
-
Darn, looks like there’s nothing comparable to #xinput in #Wayland. Under #X11, I could temporarily disable my Ergoslider bar mouse with `xinput disable "Ergoslider Mouse"`. Under Wayland, I can only list the devices recognized by #libinput with `sudo libinput list-devices` (and yes, it *does* require sudoing!) but that’s that. #Sad, as the orange buffoon is fond of saying. #Linux #FLOSS
-
Darn, looks like there’s nothing comparable to #xinput in #Wayland. Under #X11, I could temporarily disable my Ergoslider bar mouse with `xinput disable "Ergoslider Mouse"`. Under Wayland, I can only list the devices recognized by #libinput with `sudo libinput list-devices` (and yes, it *does* require sudoing!) but that’s that. #Sad, as the orange buffoon is fond of saying. #Linux #FLOSS
-
Giving GNOME a chance on my new Framework 13 laptop. Last time I tried it was around 7 years ago, and it's much better than I remember.
But some ridiculous things keep popping up — like the fact that I still can’t adjust the touchpad scroll speed. What the heck? libinput has supported this for ages. How is this still not a thing?
-
Giving GNOME a chance on my new Framework 13 laptop. Last time I tried it was around 7 years ago, and it's much better than I remember.
But some ridiculous things keep popping up — like the fact that I still can’t adjust the touchpad scroll speed. What the heck? libinput has supported this for ages. How is this still not a thing?
-
Giving GNOME a chance on my new Framework 13 laptop. Last time I tried it was around 7 years ago, and it's much better than I remember.
But some ridiculous things keep popping up — like the fact that I still can’t adjust the touchpad scroll speed. What the heck? libinput has supported this for ages. How is this still not a thing?
-
Giving GNOME a chance on my new Framework 13 laptop. Last time I tried it was around 7 years ago, and it's much better than I remember.
But some ridiculous things keep popping up — like the fact that I still can’t adjust the touchpad scroll speed. What the heck? libinput has supported this for ages. How is this still not a thing?
-
Giving GNOME a chance on my new Framework 13 laptop. Last time I tried it was around 7 years ago, and it's much better than I remember.
But some ridiculous things keep popping up — like the fact that I still can’t adjust the touchpad scroll speed. What the heck? libinput has supported this for ages. How is this still not a thing?
-
#libinput 1.28.901 (1.29 RC1) has been released (#InputDeviceManagement / #EventHandlingLibrary / #Wayland / #WaylandCompositor / #X11 / #XOrg / #FreeDesktop) https://wayland.freedesktop.org/libinput/doc/latest/
-
#libinput 1.28.901 (1.29 RC1) has been released (#InputDeviceManagement / #EventHandlingLibrary / #Wayland / #WaylandCompositor / #X11 / #XOrg / #FreeDesktop) https://wayland.freedesktop.org/libinput/doc/latest/
-
#libinput 1.28.901 (1.29 RC1) has been released (#InputDeviceManagement / #EventHandlingLibrary / #Wayland / #WaylandCompositor / #X11 / #XOrg / #FreeDesktop) https://wayland.freedesktop.org/libinput/doc/latest/
-
#libinput 1.28.901 (1.29 RC1) has been released (#InputDeviceManagement / #EventHandlingLibrary / #Wayland / #WaylandCompositor / #X11 / #XOrg / #FreeDesktop) https://wayland.freedesktop.org/libinput/doc/latest/
-
#libinput 1.28.1 has been released (#InputDeviceManagement / #EventHandlingLibrary / #Wayland / #WaylandCompositor / #X11 / #XOrg / #FreeDesktop) https://wayland.freedesktop.org/libinput/doc/latest/
-
#libinput 1.28.1 has been released (#InputDeviceManagement / #EventHandlingLibrary / #Wayland / #WaylandCompositor / #X11 / #XOrg / #FreeDesktop) https://wayland.freedesktop.org/libinput/doc/latest/
-
#libinput 1.28.1 has been released (#InputDeviceManagement / #EventHandlingLibrary / #Wayland / #WaylandCompositor / #X11 / #XOrg / #FreeDesktop) https://wayland.freedesktop.org/libinput/doc/latest/
-
#libinput 1.28.1 has been released (#InputDeviceManagement / #EventHandlingLibrary / #Wayland / #WaylandCompositor / #X11 / #XOrg / #FreeDesktop) https://wayland.freedesktop.org/libinput/doc/latest/
-
Die #libinput-Probleme mit Pinch-/Kneifgesten waren ein Bug und sind mit v1.28.1 behoben worden:
https://github.com/bulletmark/libinput-gestures/issues/378#issuecomment-2769870193
