[Wayland-bugs] [Bug 101139] Acceleration still too fast with slow and slow-medium finger movements

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101139

--- Comment #30 from Greg Reichow  ---
See video attached.  This was using the lowclip patch I mentioned with accel @
0.  For reference, the physical trackpad distance covered in the video is about
90mm in 3 seconds.  So roughly 30mm/sec.  

I roughly measured the distance covered on the screen, it is about 110mm-120mm. 

https://www.dropbox.com/s/g32jmah45so38ck/IMG_6781.MOV?dl=0

I then did another video with far faster movements, see below:

https://www.dropbox.com/s/9yytyaydw26u5xt/IMG_6782.MOV?dl=0

Even with these movements at a significantly higher speed, I am still only
covering about 50-75% of the screen width.

Greg

-- 
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 101139] Acceleration still too fast with slow and slow-medium finger movements

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101139

--- Comment #29 from Peter Hutterer  ---
https://github.com/whot/libinput/tree/wip/evemu-v3 is the closest I have so
far. It's still WIP so the output format isn't stable. Run with:

sudo ./build/libinput-record --with-libinput /dev/input/eventX (for the
touchpad device). That will print the evdev events along with the libinput
events. It's not evemu in that I don't have the python wrappers to process the
data but that'll come eventually.

I tested the lowclip patch - the base speed is too slow for my liking but I can
accept how this could be a preference. The acceleration is still too fast with
the pointer shooting off as soon as I move a bit faster than the speed in the
video from comment #26

-- 
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 105407] Xorg assertion failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105407

--- Comment #5 from Daniel van Vugt  ---
I'm not too concerned. The bugs are all linked and with enough detail to judge
if and when this can be closed post-1.10.2 without further work. Fingers
crossed.

-- 
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 105407] Xorg assertion failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105407

--- Comment #4 from Peter Hutterer  ---
If you can't reproduce it yourself, please don't upstream bugs until you've
verified it happens with vanilla upstream. For all we know this is a
side-effect of the other two bugs and has already been fixed.

-- 
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 105407] Xorg assertion failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105407

--- Comment #3 from Daniel van Vugt  ---
I'm not someone experiencing the crash myself. But we can easily wait to see
what happens in Ubuntu 18.04 once libinput 1.10.2 arrives there.

That said, an almost-amusing way to reproduce the crash is described here:
https://launchpad.net/bugs/1754487

-- 
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 105409] Touchpad deadzone on Razer Blade Stealth

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105409

--- Comment #1 from Dave  ---
Created attachment 137922
  --> https://bugs.freedesktop.org/attachment.cgi?id=137922&action=edit
evemu-describe output

Also attached, the evemu-describe output

-- 
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 105409] Touchpad deadzone on Razer Blade Stealth

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105409

Bug ID: 105409
   Summary: Touchpad deadzone on Razer Blade Stealth
   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: therav...@gmail.com

Created attachment 137921
  --> https://bugs.freedesktop.org/attachment.cgi?id=137921&action=edit
libinput-debug-events

I've noticed with the touchpad on the late-2017 Razer Blade Stealth (with the
i7-8550U), there's a deadzone slightly off-center.

Running kernel: 4.16.0-041600rc4-generic
libinput: built from master at cd966460

The touchpad works fine in Windows, however does not work under Ubuntu (tested
17.10 and 18.04) or Fedora 27. It also occurs on both Wayland and X, and with
both the Synaptics drivers and libinput. The issue appears less significant
when using libinput, but still constant.
If a finger enters this zone, it will register the following in the logs:
> touch 0 from BUTTON_STATE_AREA, event BUTTON_EVENT_UP to BUTTON_STATE_NONE

Occasionally, when a finger is held in that zone, the cursor will seemingly
vibrate.

The device information is:
Device:   1A586753:00 06CB:8323 Touchpad
Kernel:   /dev/input/event16
Group:9
Seat: seat0, default
Size: 102x60mm
Capabilities: pointer gesture
Tap-to-click: disabled
Tap-and-drag: enabled
Tap drag lock:disabled
Left-handed:  disabled
Nat.scrolling:disabled
Middle emulation: disabled
Calibration:  n/a
Scroll methods:   *two-finger edge 
Click methods:*button-areas clickfinger 
Disable-w-typing: enabled
Accel profiles:   none
Rotation: n/a

-- 
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 105407] Xorg assertion failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105407

Peter Hutterer  changed:

   What|Removed |Added

 CC||peter.hutte...@who-t.net
 Status|NEW |NEEDINFO

--- Comment #2 from Peter Hutterer  ---
I'll need an evemu recording for this, it's likely some tap state/palm
detection confusion again. And a verification that it's happening on git master
(or at least 1.10.2), thanks.

-- 
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 105108] Lenovo Yoga 11S touchpad is jittery

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105108

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #25 from Peter Hutterer  ---
thanks for testing, merged and pushed

commit ea7498ef971350454db9c78b9ba160e7d6bb455b
Author: Peter Hutterer <>
Date:   Wed Feb 21 13:41:31 2018 +1000

 touchpad: use the fuzz value (if any) for the hysteresis margin

commit 1b64888a2248af2a287365598cf520e4e2be33fd
Author: Peter Hutterer <>
Date:   Fri Feb 23 11:44:23 2018 +1000

 touchpad: enable hysteresis based on a 0 fuzz value

commit 1523d8bb2e066bec297f7a03ce4a0d8cada8f383
Author: Peter Hutterer <>
Date:   Mon Mar 5 13:17:43 2018 +1000

 Extract and reset the abs fuzz value for the x/y axes

-- 
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 104828] Wobbly AlpsPS/2 ALPS DualPoint TouchPad

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104828
Bug 104828 depends on bug 105108, which changed state.

Bug 105108 Summary: Lenovo Yoga 11S touchpad is jittery
https://bugs.freedesktop.org/show_bug.cgi?id=105108

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
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 105108] Lenovo Yoga 11S touchpad is jittery

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105108
Bug 105108 depends on bug 105303, which changed state.

Bug 105303 Summary: Kernel absfuzz handling is inconsistent
https://bugs.freedesktop.org/show_bug.cgi?id=105303

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
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 104828] Wobbly AlpsPS/2 ALPS DualPoint TouchPad

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104828
Bug 104828 depends on bug 105303, which changed state.

Bug 105303 Summary: Kernel absfuzz handling is inconsistent
https://bugs.freedesktop.org/show_bug.cgi?id=105303

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
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 105303] Kernel absfuzz handling is inconsistent

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105303

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Peter Hutterer  ---
commit 1523d8bb2e066bec297f7a03ce4a0d8cada8f383
Author: Peter Hutterer <>
Date:   Mon Mar 5 13:17:43 2018 +1000

 Extract and reset the abs fuzz value for the x/y axes

-- 
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 101139] Acceleration still too fast with slow and slow-medium finger movements

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101139

--- Comment #28 from Greg Reichow  ---
Couple comments to answer above:

1. Not using a Hi-dpi display. Reported resolution is 1680 x 1050.

2. Exact machine is a 2011 MacBook Pro 8,2 

3. Agree the earlier patch was too fast.  I also found I did not like the
exponential acceleration from my first patch and have since switched full time
to the last patch I submitted (lowclip_patch) which has a simple linear accel
curve yet starts slower to enable precision at low speeds.  For reference, my
comfortable setting is 0.

4. I will try to get some similar video with the slow finger movement and share
back with you.

Is there a utility you have that records both physical input speed and also
resulting cursor speed on screen? I wonder if something is not happening
further up the stack from libinput and causing the differences in resulting
pointer movement?  (As I keep going through the libinput code and do not
understand why we are seeing such different results from similar input speeds
as you have shown above.)

-- 
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 105407] Xorg assertion failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105407

--- Comment #1 from Daniel van Vugt  ---
This is happening in libinput 1.10.1 and 1.10.0 so far.

-- 
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 105407] Xorg assertion failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105407

Bug ID: 105407
   Summary: Xorg assertion failure: Xorg:
../src/evdev-mt-touchpad-tap.c:1002:
tp_tap_handle_state: Assertion `tp->tap.nfingers_down
> 0' failed.
   Product: Wayland
   Version: unspecified
  Hardware: Other
OS: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: libinput
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: daniel.van.v...@canonical.com

Xorg assertion failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002:
tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.

Sounds like it might be something fixed in libinput 1.10.2 but those fixes seem
to describe different assertions to this one.

https://launchpad.net/bugs/1751086

-- 
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 105407] Xorg assertion failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105407

Daniel van Vugt  changed:

   What|Removed |Added

   See Also||https://launchpad.net/bugs/
   ||1751086

-- 
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 101139] Acceleration still too fast with slow and slow-medium finger movements

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101139

--- Comment #27 from Nate Graham  ---
> [1] having said that, I'm now wondering what's going on there, because if I
move 10mm, it moves by ~10mm on the screen, not 3.7

And that, I think, is exactly the bug we're trying to get to the bottom of.

-- 
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 105265] Disable speed-based thumb detection on semi-mt devices

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105265

--- Comment #3 from Peter Hutterer  ---
*** Bug 104889 has been marked as a duplicate of this bug. ***

-- 
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 101139] Acceleration still too fast with slow and slow-medium finger movements

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101139

--- Comment #26 from Peter Hutterer  ---
And here's the thing - libinput's acceleration works in physical distances. So
the hw shouldn't really matter because a speed of 10mm/s is always that,
regardless of the hardware. As long as touchpad-edge-detector and you agree on
the ranges/dimensions on the hardware, there shouldn't be much difference.

That acceleration in the attachment is actually a slowdown, we multiply the
calculated input speed by a magic constant (0.37) so that a physical delta of
10mm should end up in a delta of 3.7mm [1], give or take with the changing
screen resolution. Greg's patch just slows things down even further and a -0.75
should then make this even slower.

The question was directed at anyone btw, sorry, should've made that clear.
If you have a compositor that doesn't support hidpi, you'd see a slowdown
because with twice the pixel density (which libinput knows nothing about) your
delta is half as fast - but that's something the compositor has to take care of
(mutter already does).

It would be good if you could attach an evemu recording from a finger movement.
Close your eyes, put your finger down and move from left to right at about
20mm/s - hard to guess I know but it's basically a medium movement. Then I can
try to reproduce this here, maybe, hopefully.

For reference: here's a video of me moving the finger and the corresponding
cursor movement in the libinput debug-gui:
https://photos.app.goo.gl/BTED3UdQwYqw5iW22

[1] having said that, I'm now wondering what's going on there, because if I
move 10mm, it moves by ~10mm on the screen, not 3.7

-- 
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 101139] Acceleration still too fast with slow and slow-medium finger movements

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101139

--- Comment #25 from Nate Graham  ---
Funny, I notice a MASSIVE difference (all Mac touchpads feel the same; there's
no moderl/year difference in touchpad feel). I'm the kind of person who wants a
touchpad so good that I don't feel the urge to use a mouse, so maybe I'm just
picky. But I really really really do notice the difference.

With Greg's patch, I have to use a -0.75 accel value, and it feels perfect. But
there may be hardware-specific factors at play. My touchpad hardware is
definitely not the highest quality in the world.

I'm not married to Greg's patch per se; my issue with libinput's default
acceleration curve is pretty simple to articulate: it accelerates too much at
slow and slow-medium speeds. Check out the graph attached at
https://bugs.freedesktop.org/attachment.cgi?id=136584: Up to 50 mm/s, the
default acceleration is faster than with Greg's patch, and there's a very
abrupt cliff where the acceleration increases. Aside from technical matters,
I'm just not sure what the justification is for accelerating small movements
that much. It makes precise control very difficult.

I do not have a HiDPI screen (didn't know it was directed at me, sorry).
Regular old 1920x1080 @ 13". Not sure it's relevant now since I'm using KDE
Plasma with KWin, not GNOME with Mutter.

-- 
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 101139] Acceleration still too fast with slow and slow-medium finger movements

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101139

--- Comment #24 from Peter Hutterer  ---
I do, a 2015 macbook air. And while I admit there are differences, I don't
think they're that big. And that's the biggest puzzle, I can switch between the
air and the t440 and notice a bit of a difference but it's not massive. Whereas
the patch above that makes things useful for you makes the cursor absolutely
uncontrollable - and with that I don't mean "i don't like it" but "i cannot hit
a 200x200 size target with it" as soon as I'm going beyond crawling speed. So,
*something* is off and I still have not yet identified what it is.

Again: "please confirm that you do *not* have a hidpi screen"

-- 
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 101139] Acceleration still too fast with slow and slow-medium finger movements

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101139

Nate Graham  changed:

   What|Removed |Added

Summary|Acceleration still too slow |Acceleration still too fast
   |with slow and slow-medium   |with slow and slow-medium
   |finger movements|finger movements

-- 
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 101139] Acceleration still too slow with slow and slow-medium finger movements

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101139

--- Comment #23 from Nate Graham  ---
Peter, do you happen to have access to a Mac running macOS? IMHO that's the
benchmark of A+ touchpad experience. Yes, a lot of this is the good hardware,
but a lot of it is also the acceleration curve; I continue to find libinput
unusable with the default curve, but a joy using  Greg's that patch mimics the
macOS acceleration curve. With this, I have been able to finally switch from
synaptics and use libinput full-time.

-- 
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 101139] Acceleration still too slow with slow and slow-medium finger movements

2018-03-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101139

Nate Graham  changed:

   What|Removed |Added

Summary|Acceleration still too slow |Acceleration still too slow
   |with medium finger  |with slow and slow-medium
   |movements   |finger movements

-- 
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 774065] Entry completion drop-down is misplaced on external monitor when on Wayland

2018-03-08 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=774065

--- Comment #13 from Guillaume Ayoub  ---
(In reply to Guillaume Ayoub from comment #12)
> I've updated to Gtk+-3.22.28 (with Gnome libs 3.27.92), the bug is fixed for
> me. Applying the patch even breaks my current installation.

Forget that, sorry for the noise. I was using Xorg instead of Wayland.

So, as said before, it's broken with the patch on Xorg and broken without the
patch on Wayland.

-- 
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 774065] Entry completion drop-down is misplaced on external monitor when on Wayland

2018-03-08 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=774065

--- Comment #12 from Guillaume Ayoub  ---
I've updated to Gtk+-3.22.28 (with Gnome libs 3.27.92), the bug is fixed for
me. Applying the patch even breaks my current installation.

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