[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2023-02-07 Thread Nate Graham
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:

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2023-02-07 Thread Nate Graham
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2023-02-07 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=414559 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit|

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2023-02-06 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=414559 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #31 from Bug

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-11-15 Thread bugzilla_noreply
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-10-06 Thread Abdullah
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-10-06 Thread Abdullah
https://bugs.kde.org/show_bug.cgi?id=414559 Abdullah changed: What|Removed |Added CC||abdullah.kasim@gmail.co |

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-09-03 Thread bugzilla_noreply
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-06-14 Thread Zach White
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-06-14 Thread bugzilla_noreply
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

2022-06-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=414559 sausagefacto...@gmail.com changed: What|Removed |Added CC||sausagefacto...@gmail.com ---

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-05-30 Thread Alex Ander
https://bugs.kde.org/show_bug.cgi?id=414559 Alex Ander changed: What|Removed |Added CC||aalexand...@gmail.com -- You are receiving this

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-05-28 Thread Sean
https://bugs.kde.org/show_bug.cgi?id=414559 Sean changed: What|Removed |Added CC||s...@krail.dev -- You are receiving this mail because:

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-05-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=414559 robin+kdeb...@rkslot.nl changed: What|Removed |Added CC||robin+kdeb...@rkslot.nl --- Comment

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-04-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=414559 giraffefile+...@protonmail.com changed: What|Removed |Added CC||giraffeFile+kde@protonmail.

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-04-13 Thread bugzilla_noreply
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-03-04 Thread Zach White
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-03-04 Thread Adam E
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-03-04 Thread Adam E
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-03-04 Thread Adam E
https://bugs.kde.org/show_bug.cgi?id=414559 Adam E changed: What|Removed |Added CC||linuxad...@gmail.com -- You are receiving this mail

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-02-20 Thread Cuchac
https://bugs.kde.org/show_bug.cgi?id=414559 Cuchac changed: What|Removed |Added CC||cuc...@email.cz --- Comment #20 from Cuchac ---

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-02-10 Thread Zach White
https://bugs.kde.org/show_bug.cgi?id=414559 Zach White changed: What|Removed |Added CC||k...@drpepper.org --- Comment #19 from Zach White

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-01-21 Thread Gerry Gavigan
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-01-20 Thread Nate Graham
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2022-01-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=414559 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2021-11-25 Thread Mikel Pérez
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2021-11-25 Thread Nate Graham
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2021-04-12 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=414559 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b |

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2020-11-29 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=414559 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2020-10-05 Thread Nate Graham
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

2020-10-05 Thread Patrick Silva
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

2020-10-05 Thread Nate Graham
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

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2020-10-05 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=414559 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b |

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2020-06-27 Thread David
https://bugs.kde.org/show_bug.cgi?id=414559 David changed: What|Removed |Added CC||david...@hotmail.com --- Comment #12 from David ---

[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade

2020-06-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=414559 Nate Graham changed: What|Removed |Added Summary|Running "sudo udevadm |Running "sudo udevadm |trigger