[Wayland-bugs] [Bug 104828] Jumpy AlpsPS/2 ALPS DualPoint TouchPad
https://bugs.freedesktop.org/show_bug.cgi?id=104828 Bug ID: 104828 Summary: Jumpy AlpsPS/2 ALPS DualPoint TouchPad Product: Wayland Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: libinput Assignee: wayland-bugs@lists.freedesktop.org Reporter: grouik.gro...@yahoo.fr Hi, Running Ubuntu 18.04 (dev) and libinput 1.9.4-2ubuntu1 on a Dell Precision 7510. Since the patch applied in Ubuntu ( https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1696929 ) from 1.9.4-2 version, my touchpad is jumpy. Pointing is jumpy when I need some precision (row size setting, e.g.), pointer is jumpy (very small jumps) when I keep my finger at the same place. Two-fingers scrolling is jumpy as well. Daniel van Vugt says in LP bug report : "The patch in 1.9.4-2ubuntu1 is the same as what's coming soon in libinput release 1.10. So a fix for your specific touchpad should be done upstream. Simply reverting the patch won't help you after we update to libinput 1.10, and besides most laptops seem to need that patch." https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1745816 -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 102649] Mouse taps (?) detected while typing
https://bugs.freedesktop.org/show_bug.cgi?id=102649 --- Comment #43 from Peter Hutterer--- "thee cursor jumped between "t" and "ermina"." - wait, I though we're talking about mouse taps detected? Now that I'm reading the log again: the problem seems to be that your trackpoint sends random motion events. This is one case of movement while typing: event0 KEYBOARD_KEY +15.72s *** (-1) pressed event0 KEYBOARD_KEY +15.78s *** (-1) released -event14 POINTER_MOTION +15.90s -0.26/ -0.09 -event0 KEYBOARD_KEY +15.91s *** (-1) pressed event0 KEYBOARD_KEY +15.91s *** (-1) pressed -event14 POINTER_MOTION +15.91s -0.73/ -0.29 -event0 KEYBOARD_KEY +15.98s *** (-1) released event0 KEYBOARD_KEY +15.98s *** (-1) released event14 is your trackpoint and it's not captured by the disable-while-typing because that's for touchpads only. So the question now is *why* is this thing sending the occasional movement? Are you touching it or just hammering on the keyboard hard enough? As for starting multiple commands at the same time, screen is your friend: $> cat test.screenrc zombie kr screen ls -lR screen echo "hello" $> screen -c test.screenrc Will start 2 screens with ls and echo. Adjusting this example should give you almost exact timestamps in evemu and libinput debug-events. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 792889] On kwin_wayland, GTK3 applications started with GDK_BACKEND=wayland *always* request CSD despite preferring SSD
https://bugzilla.gnome.org/show_bug.cgi?id=792889 --- Comment #17 from Drew DeVault--- My understanding of the protocol is that once the client binds to the decoration manager, it will use the server advertised mode by default and will only send an event if it wants to use something else. -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 792889] On kwin_wayland, GTK3 applications started with GDK_BACKEND=wayland *always* request CSD despite preferring SSD
https://bugzilla.gnome.org/show_bug.cgi?id=792889 --- Comment #18 from Kyle De'Vir--- Curious... kwin_wayland must be doing something odd, then, if LibreOffice doesn't make CSD requests on Sway, but does on kwin_wayland. It's almost like... on kwin_wayland, your code is, for whatever reason, marking said applications' windows as always being priv->client_decorated, even though they're obviously not, thus always triggering gdk_wayland_window_announce_csd. But... that makes zero sense. WTF? :/ -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 792889] On kwin_wayland, GTK3 applications started with GDK_BACKEND=wayland *always* request CSD despite preferring SSD
https://bugzilla.gnome.org/show_bug.cgi?id=792889 --- Comment #14 from Drew DeVault--- Created attachment 367548 --> https://bugzilla.gnome.org/attachment.cgi?id=367548=edit WAYLAND_DEBUG log of lowriter on Sway -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 792889] On kwin_wayland, GTK3 applications started with GDK_BACKEND=wayland *always* request CSD despite preferring SSD
https://bugzilla.gnome.org/show_bug.cgi?id=792889 --- Comment #16 from Kyle De'Vir--- I see... on kwin_wayland, MyPaint, LibreOffice, DarkTable and RawTherapee do not have SSD, but they seem to be request CSD from kwin_wayland regardless. >From said applications, it is always invariably: [3347746.113] org_kde_kwin_server_decoration_manager@15.default_mode(2) ... [334.597] -> org_kde_kwin_server_decoration@32.request_mode(1) I noticed that in your LibreOffice log for Sway, that it never makes any requests. Why does this happen on kwin_wayland, then? Broken assumptions? -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 792889] On kwin_wayland, GTK3 applications started with GDK_BACKEND=wayland *always* request CSD despite preferring SSD
https://bugzilla.gnome.org/show_bug.cgi?id=792889 --- Comment #13 from Drew DeVault--- I just tested this again on Sway and it worked as expected. I tested gtk-demos, nautilus, and lowriter; all worked correctly. The expected behavior is that gtk-demos use CSD and disable SSD, individual demos in gtk-demos use SSD and disable CSD, nautilus uses CSD and disables SSD, and lowriter uses SSD and disables CSD. -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 792889] On kwin_wayland, GTK3 applications started with GDK_BACKEND=wayland *always* request CSD despite preferring SSD
https://bugzilla.gnome.org/show_bug.cgi?id=792889 --- Comment #20 from Kyle De'Vir--- An examination of the GTK3 code suggests that the application must set priv->client_decorated, but that still doesn't explain why the same GTK3 applications will request this on kwin_wayland, but not Sway. This is... confusing. -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 792889] On kwin_wayland, GTK3 applications started with GDK_BACKEND=wayland *always* request CSD despite preferring SSD
https://bugzilla.gnome.org/show_bug.cgi?id=792889 --- Comment #19 from Kyle De'Vir--- Not your code, specifically, sorry, but rather, GTK3 is, somewhere else. -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 792889] On kwin_wayland, GTK3 applications started with GDK_BACKEND=wayland *always* request CSD despite preferring SSD
https://bugzilla.gnome.org/show_bug.cgi?id=792889 --- Comment #15 from Drew DeVault--- Created attachment 367549 --> https://bugzilla.gnome.org/attachment.cgi?id=367549=edit WAYLAND_DEBUG log of gtk4-demo on Sway -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs