[Wayland-bugs] [Bug 775313] Clipboard contents are not available when exited application in wayland

[mutter]

https://bugzilla.gnome.org/show_bug.cgi?id=775313

--- Comment #11 from Strangiato  ---
Same thing in Gnome 3.28, Arch Linux.

-- 
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 766284] [Wayland] gtk_window_present() not working

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=766284

Bastien Nocera  changed:

   What|Removed |Added

 CC||bugzi...@hadess.net

--- Comment #47 from Bastien Nocera  ---
(In reply to Matthias Clasen from comment #14)
> But look at this code in gtk_window_present_with_time:
> 
>   /* Translate a timestamp of GDK_CURRENT_TIME appropriately */
>   if (timestamp == GDK_CURRENT_TIME)
> {
> #ifdef GDK_WINDOWING_X11
>   if (GDK_IS_X11_WINDOW(gdk_window))
> {
>   GdkDisplay *display;
> 
>   display = gtk_widget_get_display (widget);
>   timestamp = gdk_x11_display_get_user_time (display);
> }
>   else
> #endif
> timestamp = gtk_get_current_event_time ();
> }
> 
>   gdk_window_focus (gdk_window, timestamp);
> 
> 
> I don't think GDK_CURRENT_TIME should reach gdk

I think that, under Wayland, we should be using the current time from the
system if gtk_get_current_event_time() returns 0. Either in
gdk_wayland_window_focus() (probably a bit late), or
gtk_window_present_with_time() (better, IMO).

I don't remember whether GTK+ Wayland expects monotonic time, and in which
unit, but the output of g_get_monotonic_time() should be what you're looking to
fallback to. Anyone to cook up a patch?

-- 
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 105640] Lenovo T440p - slow fine touchpad movement makes cursor jump

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105640

--- Comment #10 from L Holland  ---
By the way, FWIW, I get lots of these in my logs:

(EE) event19 - Synaptics tm2964-001: kernel bug: Touch jump detected and
discarded.

Not sure if this is connected - they don't necessarily occur at the same time
as I try to do fine movement.

-- 
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 105696] Apple Magic Trackpad scrolling sensitivity too low (libinput 1.10)

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105696

--- Comment #2 from Maximilian Böhm  ---
Created attachment 138321
  --> https://bugs.freedesktop.org/attachment.cgi?id=138321=edit
evemu-record of a scroll sequence that doesn't get detected correctly

-- 
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 777693] Input event (e. g. typing on keyboard) is sent repeatedly during high load

[gnome-shell]

https://bugzilla.gnome.org/show_bug.cgi?id=777693

--- Comment #17 from Strangiato  ---
Still happening in Gnome 3.28 Wayland on Arch Linux.
I noticed that the problem occurs when Gnome-shell shows a notification while
I'm typing something.

-- 
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 794612] crash on wayland session

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=794612

Daniel Boles  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
URL||https://gitlab.gnome.org/GN
   ||OME/gtk/issues/114
 CC||dboles@gmail.com
 Resolution|--- |OBSOLETE

--- Comment #2 from Daniel Boles  ---
seems like a dupe of https://gitlab.gnome.org/GNOME/gtk/issues/114

-- 
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 105022] Lenovo P50 - Slow fine touchpad movement makes it jump

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105022

--- Comment #31 from Krasi  ---
Created attachment 138303
  --> https://bugs.freedesktop.org/attachment.cgi?id=138303=edit
dmesg_journalctl

-- 
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 105640] Lenovo T440p - slow fine touchpad movement makes cursor jump

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105640

--- Comment #9 from L Holland  ---
It's certainly possible that the patch helped somewhat; it's just really hard
to distinguish subjectively between the level of "jumpiness" between restarts.
All I can say is that as things stand it is still challenging to do finer work
with the trackpad.

Maybe there's a problem with what I've done, however. You say that one of the
categories of jump in the latest recording ought to be fixed by the patch; but
the recording was made *after* I applied the hwdb changes, so this jump
shouldn't be showing up at all now but as you can see from the udevadm info
output, that variable does appear to be set, so I'm confused. Have I
misunderstood here or is there some other way to check that the updated
behaviour really is being used?

-- 
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