[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Nate Graham changed: What|Removed |Added Version Fixed In||5.27 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/commit/ca |ma/plasma-desktop/commit/eb |59a847bddc906c51fbb41635128 |0f45dfb1da15631d6f768bad550 |f40b1b31a30 |51ab478c38a --- Comment #33 from Nate Graham --- Git commit eb0f45dfb1da15631d6f768bad55051ab478c38a by Nate Graham, on behalf of David Edmundson. Committed on 07/02/2023 at 16:52. Pushed by ngraham into branch 'Plasma/5.27'. Re-run touchpad kcminit on device connect kcminit runs once on boot then closes. Devices are less static. For mouse and keyboard the keyboard daemon watches for input devices changing and re-runs kcminit modules for both keyboard and mouse. This patch adds touchpad to the list to cover remaining devices. Having this inside the keyboard daemon is not semantically sane, but it's an established pattern and we want a safe fix for 5.27. Fixed-in: 5.27.0 (cherry picked from commit ca59a847bddc906c51fbb41635128f40b1b31a30) M +4-4kcms/keyboard/keyboard_daemon.cpp M +1-1kcms/keyboard/keyboard_daemon.h https://invent.kde.org/plasma/plasma-desktop/commit/eb0f45dfb1da15631d6f768bad55051ab478c38a -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/ca ||59a847bddc906c51fbb41635128 ||f40b1b31a30 Resolution|--- |FIXED --- Comment #32 from Nate Graham --- Git commit ca59a847bddc906c51fbb41635128f40b1b31a30 by Nate Graham, on behalf of David Edmundson. Committed on 07/02/2023 at 15:55. Pushed by ngraham into branch 'master'. Re-run touchpad kcminit on device connect kcminit runs once on boot then closes. Devices are less static. For mouse and keyboard the keyboard daemon watches for input devices changing and re-runs kcminit modules for both keyboard and mouse. This patch adds touchpad to the list to cover remaining devices. Having this inside the keyboard daemon is not semantically sane, but it's an established pattern and we want a safe fix for 5.27. Fixed-in: 5.27.0 M +4-4kcms/keyboard/keyboard_daemon.cpp M +1-1kcms/keyboard/keyboard_daemon.h https://invent.kde.org/plasma/plasma-desktop/commit/ca59a847bddc906c51fbb41635128f40b1b31a30 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #31 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1376 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #30 from robin+kdeb...@rkslot.nl --- The issue where mouse settings reset when reconnecting a mouse with multiple mice connected seems to be fixed now that I upgraded from Ubuntu 22.04 to Ubuntu 22.10. Not sure how that relates to the original report though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #29 from Abdullah --- (In reply to Abdullah from comment #28) > I wrote a workaround here: https://askubuntu.com/a/1434072/1638910 > > It's not perfect but it's usable for me currently. Probably the easiest way > is to run a 60-second watchdog when udev triggers, but that'll require more > scripting effort. Don't use this workaround. I've deleted it as I've found a better workaround from another poster here: https://bugs.kde.org/show_bug.cgi?id=435113#c88 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Abdullah changed: What|Removed |Added CC||abdullah.kasim@gmail.co ||m --- Comment #28 from Abdullah --- I wrote a workaround here: https://askubuntu.com/a/1434072/1638910 It's not perfect but it's usable for me currently. Probably the easiest way is to run a 60-second watchdog when udev triggers, but that'll require more scripting effort. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 y...@uechi.io changed: What|Removed |Added CC||y...@uechi.io -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #27 from Zach White --- (In reply to sausagefactory0 from comment #25) > I need to change it two times > (to "Adaptive" and then to "Flat") to make it flat again. You can avoid changing it two times by changing another setting instead. I toggle "Press left and right buttons for middle-click" one time and it resets all my settings, so I only have to "Apply" once. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #26 from sausagefacto...@gmail.com --- ^ Sorry, forgot to add: I'm using KDE with X11, and everything is on a real PC, no VMs involved. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 sausagefacto...@gmail.com changed: What|Removed |Added CC||sausagefacto...@gmail.com --- Comment #25 from sausagefacto...@gmail.com --- I have a similar issue with mouses on Arch Linux. Either of the things listed below, resets the mouse acceleration to "Adaptive", even though it still shows in Settings UI as "Flat", and then I need to change it two times (to "Adaptive" and then to "Flat") to make it flat again. 1. sudo udevadm trigger -s input 2. simply disconnecting the mouse and then connecting it again to the same USB port -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Alex Ander changed: What|Removed |Added CC||aalexand...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Sean changed: What|Removed |Added CC||s...@krail.dev -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 robin+kdeb...@rkslot.nl changed: What|Removed |Added CC||robin+kdeb...@rkslot.nl --- Comment #24 from robin+kdeb...@rkslot.nl --- I am also running into this issue with two mice. My desktop computer is a qemu/libvirt/kvm virtual machine, which means it has my real passed through USB mouse but by default also an emulated PS/2 mouse. Whenever I unplug my USB mouse and plug it back in, settings like pointer acceleration reset. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 giraffefile+...@protonmail.com changed: What|Removed |Added CC||giraffeFile+kde@protonmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 v...@phux.dev changed: What|Removed |Added CC||v...@phux.dev -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #23 from Zach White --- I tried to dig into this problem a little bit and here is what I was able to observe. I still have not figured out how I can either fix or workaround the issue. The first surprising observation is that `sudo udevadm monitor` does not register any output at all at times I would expect it to. For example, there is no output when I run `udevadm trigger -s input` but there is output when I run `sudo udevadm trigger -s input`. This is what I see running that: https://gist.github.com/skullydazed/6a0703258dc9f0a231cebc0395174228 When I unplug and plugin my mouse here is what udevadm shows: https://gist.github.com/skullydazed/855393941da35627e15870b313224b7d Now, here's where things get interesting. I grabbed a second mouse and plugged it in (a Logitech TrackMan Marble.) When I did this my first mouse (Logitech MX Ergo) kept the correct settings but the new mouse had incorrect settings. More interestingly, when I went into System Settings -> Input Devices -> Mouse and changed a setting both mice adopted the correct settings. Steps to reproduce with any 2 mice: 1. Have first mouse plugged in, second mouse unplugged. 2. Go to System Settings -> Input Devices -> Mouse, check "Invert scroll direction", click "Apply". 3. Verify that moving the scroll wheel away from you scrolls a window down. 4. Plug in second mouse 5. Observe that first mouse scrolls down when the wheel is scrolled away from you while second mouse scrolls down when the wheel is scrolled towards you. 6. In the mouse settings window check (or uncheck) "Press left and right buttons together", then click Apply. 7. Observe that both mice scroll identically I believe this bug is classified incorrectly. Based on my observations it seems that the problem is that USB plug events are configuring devices with the default settings rather than the user's settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #22 from Adam E --- Sorry, I didn't realize I can't edit my replies so adding some more information here: Using Xorg, not wayland (although the system does have some wayland packages installed) Using libinput not synaptics. I got here from Bug 435113 which seems more similar to my issue but that report says they did not have an issue with this udevadm command. Let me know if I can provide any additional information or assistance -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #21 from Adam E --- Hi all, I'm on latest Arch Linux on a desktop and experiencing the same issue. Running the command resets mouse sensitivity settings - tested by lowering mouse sensitivity and then running that command. In my case I use a dock to switch inputs between two computers and so on every switch the mouse sensitivity is reset. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Adam E changed: What|Removed |Added CC||linuxad...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Cuchac changed: What|Removed |Added CC||cuc...@email.cz --- Comment #20 from Cuchac --- Hello, this issue hit me after upgrade to 5.24. Arch Linux here. Mouse sensitivity is reset on each sleep. I can trigger the bug on `sudo udevadm trigger -s input` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Zach White changed: What|Removed |Added CC||k...@drpepper.org --- Comment #19 from Zach White --- I upgraded my KDE Neon (5.24) system over the weekend and this started to occur for me. I do not have a touchpad at all, I'm using a Logitech MX Ergo with the wireless receiver, and the bug is triggered every time my trackball wakes up from sleep (being wireless the device itself goes into a sleep mode, this is not DPMS or the host sleeping.) The problem does not occur if I briefly (~30s) turn the trackball off and back on again. I can trigger the problem with `sudo udevadm trigger -s input`. Is there a workaround I can use here to make my preferred settings the default settings? I tried `sudo cp ~/.config/kcminputrc /root/.config` but that did not work. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #18 from Gerry Gavigan --- On power up the left-hand radio button is checked but the mouse is right-handed. To persuade the mouse to be left-handed I have to toggle the radio button twice. This only happens to me on an laptop. I never see it on my desktop. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Nate Graham changed: What|Removed |Added Priority|VHI |HI -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #17 from Mikel Pérez --- (In reply to Nate Graham from comment #16) > FWIW since moving from openSUSE Tumbleweed to Fedora, I haven't seen this > again. However my wife who uses Neon does see it. > > The triggering event somehow seems to be distro-packaging-specific. > > Still, we should fix the issue on the KDE side so that whatever does this > doesn't reset your touchpad configuration. this does happen to me on Fedora 35 (just tried it) and happened on previous versions -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #16 from Nate Graham --- FWIW since moving from openSUSE Tumbleweed to Fedora, I haven't seen this again. However my wife who uses Neon does see it. The triggering event somehow seems to be distro-packaging-specific. Still, we should fix the issue on the KDE side so that whatever does this doesn't reset your touchpad configuration. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=435113 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #15 from Nate Graham --- Ah, thanks! So I guess it's happening virtually everywhere but Gentoo then. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #14 from Patrick Silva --- duplicate bug 419533 happened on neon unstable. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 --- Comment #13 from Nate Graham --- This may be distro-specific. We have reports from people on Arch, Fedora, openSUSE Tumbleweed, and Solus. One person on Gentoo cannot reproduce it. No reports from anyone using Debian/Ubuntu-based distro. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=413973 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 David changed: What|Removed |Added CC||david...@hotmail.com --- Comment #12 from David --- Possibly related -- As a Solus Plasma user who is also experiencing touch pad settings being reset every time a system update is performed, the following also occurs at every system update: The Plasma Vault widget becomes empty. Restart, and the vault(s) are back; it's the same with the touch pad settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Nate Graham changed: What|Removed |Added Summary|Running "sudo udevadm |Running "sudo udevadm |trigger -s input" resets|trigger -s input" resets |touchpad configuration |touchpad configuration; can ||happen after system upgrade -- You are receiving this mail because: You are watching all bug changes.
