[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

https://bugs.kde.org/show_bug.cgi?id=476368 --- Comment #10 from Niels Ruitenbeek --- One interesting thing is that the touch assignment does seem to work properly once the configuration is applied. The problems occur as soon is the computer is restarted and the configuration is loaded again as K

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

https://bugs.kde.org/show_bug.cgi?id=476368 --- Comment #9 from Niels Ruitenbeek --- Created attachment 162815 --> https://bugs.kde.org/attachment.cgi?id=162815&action=edit Output of 'udevadm info --attribute-walk' for one of the touch devices -- You are receiving this mail because: You are w

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

https://bugs.kde.org/show_bug.cgi?id=476368 --- Comment #8 from Niels Ruitenbeek --- (In reply to Nate Graham from comment #7) > Is there any way we could look at the serial number of the devices too, as > an additional data point? I'm not sure if that would work, since udev at least doesn't sho

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

https://bugs.kde.org/show_bug.cgi?id=476368 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

https://bugs.kde.org/show_bug.cgi?id=476368 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #7 from Nate Graham ---

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

https://bugs.kde.org/show_bug.cgi?id=476368 --- Comment #6 from Niels Ruitenbeek --- (In reply to Nicolas Fella from comment #5) > Thanks. > > This is a tough one. Currently the identification is done via (USB?) > vendor/product/name triple. I'm not sure what else we could use to identify > a de

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

https://bugs.kde.org/show_bug.cgi?id=476368 --- Comment #5 from Nicolas Fella --- Thanks. This is a tough one. Currently the identification is done via (USB?) vendor/product/name triple. I'm not sure what else we could use to identify a device that isn't inherently unstable/volatile -- You are

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

https://bugs.kde.org/show_bug.cgi?id=476368 --- Comment #4 from Niels Ruitenbeek --- Some version information about my system I forgot to add in the original report: KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-arch2-1 (64-bit) Graphics Pla

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

https://bugs.kde.org/show_bug.cgi?id=476368 --- Comment #3 from Niels Ruitenbeek --- (In reply to Nicolas Fella from comment #1) > Can you please attach the output of "sudo libinput list-devices" when the > two devices are connected? I have added the output of that command in the attachments. In

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

https://bugs.kde.org/show_bug.cgi?id=476368 --- Comment #2 from Niels Ruitenbeek --- Created attachment 162765 --> https://bugs.kde.org/attachment.cgi?id=162765&action=edit Output of 'sudo libinput list-devices' -- You are receiving this mail because: You are watching all bug changes.

[systemsettings] [Bug 476368] Output mapping of identical touchscreen devices doesn't remain after reboot

https://bugs.kde.org/show_bug.cgi?id=476368 --- Comment #1 from Nicolas Fella --- Can you please attach the output of "sudo libinput list-devices" when the two devices are connected? -- You are receiving this mail because: You are watching all bug changes.