[Wayland-bugs] [Bug 94910] The cursor "jump" sometimes

https://bugs.freedesktop.org/show_bug.cgi?id=94910 --- Comment #44 from Peter Hutterer --- do you see the error message in the logs though? that should tell us whether the fw above fixed it or whether it's the fix in libinput. -- You are receiving this mail because:

[Wayland-bugs] [Bug 766566] Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766566 Jonas Ådahl changed: What|Removed |Added CC||jad...@gmail.com ---

[Wayland-bugs] [Bug 763852] gdk/wayland: event source is not multi-thread aware

https://bugzilla.gnome.org/show_bug.cgi?id=763852 Matthias Clasen changed: What|Removed |Added Attachment #327362|accepted-commit_now |committed

[Wayland-bugs] [Bug 763852] gdk/wayland: event source is not multi-thread aware

https://bugzilla.gnome.org/show_bug.cgi?id=763852 Matthias Clasen changed: What|Removed |Added Status|NEW |RESOLVED

[Wayland-bugs] [Bug 766314] Spurious leave-notify event after touch up

https://bugzilla.gnome.org/show_bug.cgi?id=766314 Matthias Clasen changed: What|Removed |Added Attachment #327697|none|accepted-commit_now

[Wayland-bugs] [Bug 766566] Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766566 Matthias Clasen changed: What|Removed |Added Attachment #328083|none|reviewed

[Wayland-bugs] [Bug 766566] Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766566 Matthias Clasen changed: What|Removed |Added Attachment #328080|none|reviewed

[Wayland-bugs] [Bug 766566] Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766566 Matthias Clasen changed: What|Removed |Added Attachment #328079|none|accepted-commit_now

[Wayland-bugs] [Bug 95290] synaptics touchpad jitter

https://bugs.freedesktop.org/show_bug.cgi?id=95290 --- Comment #8 from l...@fightingcrane.com --- Created attachment 123862 --> https://bugs.freedesktop.org/attachment.cgi?id=123862=edit screencast of evemu-play with "another evemu scrolling jitter recording" (In reply to Peter Hutterer from

[Wayland-bugs] [Bug 95169] Touchscreen function broken on F24 Alpha

https://bugs.freedesktop.org/show_bug.cgi?id=95169 --- Comment #11 from Jason Gerecke --- Apologies for the delay -- this slipped off my radar... It would be good to get another evemu-record log to see if there's any difference between the stock driver and the

[Wayland-bugs] [Bug 95393] ELAN1000 touchpad erratic pointer after 1.2.4 -> 1.3.0 upgrade

https://bugs.freedesktop.org/show_bug.cgi?id=95393 Peter Hutterer changed: What|Removed |Added Status|NEEDINFO|ASSIGNED ---

[Wayland-bugs] [Bug 94910] The cursor "jump" sometimes

https://bugs.freedesktop.org/show_bug.cgi?id=94910 --- Comment #42 from Paviluf --- (In reply to Dudley Du from comment #41) > Created attachment 123765 [details] > V2.0 frimware for Cypress CYTRA-101008-00 trackpad device > > The last formally released v2.0 firmware image

[Wayland-bugs] [Bug 94910] The cursor "jump" sometimes

https://bugs.freedesktop.org/show_bug.cgi?id=94910 --- Comment #43 from Paviluf --- (In reply to Peter Hutterer from comment #19) > fwiw, I just pushed a patch to libinput to at least detect these jumps and > discard them. This doesn't fix the problem (and indeed it can

[Wayland-bugs] [Bug 95458] option to disable new "middle click" functionality

https://bugs.freedesktop.org/show_bug.cgi?id=95458 Bug ID: 95458 Summary: option to disable new "middle click" functionality Product: Wayland Version: unspecified Hardware: Other OS: All Status: NEW

[Wayland-bugs] [Bug 766284] [Wayland] gtk_window_present() not working

https://bugzilla.gnome.org/show_bug.cgi?id=766284 --- Comment #11 from Matthias Clasen --- (In reply to Michael Catanzaro from comment #9) > We really need a reliable way to force present the window when apps don't > set a time in DESKTOP_STARTUP_ID. Such apps include

[Wayland-bugs] [Bug 766284] [Wayland] gtk_window_present() not working

https://bugzilla.gnome.org/show_bug.cgi?id=766284 --- Comment #10 from Matthias Clasen --- > We really need a reliable way to force present the window The wayland protocol doesn't have api for this at all. As far as Wayland is concerned, managing the stacking order and focus

[Wayland-bugs] [Bug 766284] [Wayland] gtk_window_present() not working

https://bugzilla.gnome.org/show_bug.cgi?id=766284 Michael Catanzaro changed: What|Removed |Added CC|

[Wayland-bugs] [Bug 759626] Clipboard (copy-and-paste) Wayland→Wayland or Wayland→X11 from closed applications is broken

https://bugzilla.gnome.org/show_bug.cgi?id=759626 --- Comment #9 from Matthias Clasen --- There are some other clipboard ui patterns that would require us maintain a 'history' of past clipboard contents. Not sure if there is interest in implementing a 'shelf' or something

[Wayland-bugs] [Bug 766543] Missing cursors under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766543 --- Comment #6 from Michael Catanzaro --- (In reply to Matthias Clasen from comment #5) > talk to your cursor theme dealer about compat symlinks I'm using Adwaita. Somehow these cursors that I complained about missing

[Wayland-bugs] [Bug 766543] Missing cursors under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766543 --- Comment #5 from Matthias Clasen --- talk to your cursor theme dealer about compat symlinks -- You are receiving this mail because: You are on the CC list for the bug.___

[Wayland-bugs] [Bug 766543] Missing cursors under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766543 Michael Catanzaro changed: What|Removed |Added Status|NEW |RESOLVED

[Wayland-bugs] [Bug 759626] Clipboard (copy-and-paste) Wayland→Wayland or Wayland→X11 from closed applications is broken

https://bugzilla.gnome.org/show_bug.cgi?id=759626 --- Comment #8 from Michael Catanzaro --- (In reply to Jonas Ådahl from comment #7) > So when would one do a wl_data_device.set_selection() but not a > wp_clipboard_manager.store()? The clipboard manager only ever needs

[Wayland-bugs] [Bug 766566] Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766566 Olivier Fourdan changed: What|Removed |Added Attachment #328081|reviewed|none

[Wayland-bugs] [Bug 766566] Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766566 Emmanuele Bassi (:ebassi) changed: What|Removed |Added Attachment #328081|none|reviewed

[Wayland-bugs] [Bug 766566] Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766566 --- Comment #3 from Olivier Fourdan --- Created attachment 328081 --> https://bugzilla.gnome.org/attachment.cgi?id=328081=edit [PATCH 3/3] wayland: Add get_monitor_at_window to Wayland backend Given that Wayland has no

[Wayland-bugs] [Bug 766566] Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766566 --- Comment #2 from Olivier Fourdan --- Created attachment 328080 --> https://bugzilla.gnome.org/attachment.cgi?id=328080=edit [PATCH 2/3] wayland: Add API to retrieve the Wayland output In Wayland, surfaces get an

[Wayland-bugs] [Bug 766566] Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766566 --- Comment #1 from Olivier Fourdan --- Created attachment 328079 --> https://bugzilla.gnome.org/attachment.cgi?id=328079=edit [PATCH 1/3] display: Add vfunc for get_monitor_at_window Some backends (namely Wayland) do not

[Wayland-bugs] [Bug 766566] New: Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766566 Bug ID: 766566 Summary: Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland Classification: Platform Product: gtk+ Version: unspecified OS: Linux

[Wayland-bugs] [Bug 759626] Clipboard (copy-and-paste) Wayland→Wayland or Wayland→X11 from closed applications is broken

https://bugzilla.gnome.org/show_bug.cgi?id=759626 --- Comment #6 from Matthias Clasen --- And yes, its still relevant -- You are receiving this mail because: You are on the CC list for the bug.___ wayland-bugs mailing list

[Wayland-bugs] [Bug 759626] Clipboard (copy-and-paste) Wayland→Wayland or Wayland→X11 from closed applications is broken

https://bugzilla.gnome.org/show_bug.cgi?id=759626 Matthias Clasen changed: What|Removed |Added CC||mcla...@redhat.com

[Wayland-bugs] [Bug 766543] Missing cursors under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766543 --- Comment #3 from Matthias Clasen --- and of course, the cursor theme also figures into this. I should have said: "If any of those names does not give you a suitable cursor _with the Adwaita cursor theme_..." -- You are

[Wayland-bugs] [Bug 766543] Missing cursors under Wayland

https://bugzilla.gnome.org/show_bug.cgi?id=766543 Matthias Clasen changed: What|Removed |Added CC||mcla...@redhat.com

[Wayland-bugs] [Bug 759626] Clipboard (copy-and-paste) Wayland→Wayland or Wayland→X11 from closed applications is broken

https://bugzilla.gnome.org/show_bug.cgi?id=759626 --- Comment #4 from Michael Catanzaro --- (In reply to Jonas Ådahl from comment #3) > Why would there be a need for a new request? Is it for making the client > control what selections would be more "persistent" than others