[Wayland-bugs] [Bug 99283] No click methods on MacBookPro3,1

[bugzilla-daemon]

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

--- Comment #6 from Peter Hutterer  ---
found some spare cycles
https://lists.freedesktop.org/archives/wayland-devel/2017-January/032581.html

-- 
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 99267] Cursor resolution/refresh rate decreases when a thumb is resting on the pad, especially with clickfinger behavior

[bugzilla-daemon]

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

--- Comment #10 from Peter Hutterer  ---
yeah, there are still a few bits missing, you'll have to grab benjamin's kernel
to get everything working. the 4.10 kernel is missing the intertouch
parameters, etc.

-- 
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 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

[bugzilla-daemon]

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

--- Comment #16 from Frank  ---
I have the hysteresis value at 1/10mm atm. I'll probably keep playing with the
value a little bit to find the best balance for me.

-- 
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 99338] Weston, please allow command line options to Xwayland. with firejail, this can prevent non x11 apps spying on x11 apps

[bugzilla-daemon]

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

Bug ID: 99338
   Summary: Weston, please allow command line options to Xwayland.
with firejail, this can prevent non x11 apps spying on
x11 apps
   Product: Wayland
   Version: unspecified
  Hardware: Other
OS: Linux (All)
Status: NEW
  Severity: normal
  Priority: medium
 Component: XWayland
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: pixelfa...@gmail.com
QA Contact: xorg-t...@lists.x.org

for example, Xwayland could have command instead of path

[xwayland]
command=/usr/bin/Xwayland -nolisten tcp -nolisten local

then sandboxes like firejail can make local x servers for apps that cant see
eachother, or prevent an app from seeing x11 at all, without having to make a
new network namespace.

-- 
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 99318] xwayland lets apps see the whole screen

[bugzilla-daemon]

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

pixelfa...@gmail.com changed:

   What|Removed |Added

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

--- Comment #3 from pixelfa...@gmail.com ---
whatevers default in fedora25. it looked like gnome-shell in pstree. 

the last update seems to have fixed it. what i didnt mention in the last report
was a black border around all windows. if your curious, i saved that window
dump, but now im also getting the failed request. so its good now :)

the fix still allows xwd without -root, and only works on x11 windows. would
have preferred no such functionality, but i guess its a compromise.

-- 
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 99200] Elantech touchpad with libinput has wrong number of buttons

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEEDINFO|ASSIGNED

--- Comment #15 from Peter Hutterer  ---
https://lists.freedesktop.org/archives/wayland-devel/2017-January/032571.html

-- 
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 98400] Multimedia Keys not recognized

[bugzilla-daemon]

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

--- Comment #3 from Peter Hutterer  ---
sorry about the delay, this fell through.

short summary: this would need to go into systemd's hwdb (60-keyboard.hwdb) but
I fail to see any identifying information for that keyboard, so I'm not sure we
can make a generic match here. Is this a laptop? The dmi only includes the
gigabyte motherboard's information and the keyboard claims it's connected via
serial bus.

either way, the solution to this would be a blurb simliar to others in the
60-keyboard.hwdb file. A match string, together with the scancode to event code
mappings. example here:

evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*Presario*CQ*:pvr*
 KEYBOARD_KEY_d8=f21
 KEYBOARD_KEY_d9=f21

You'll need to convert the scancodes into hex (e.g. 159 -> 0x9f) and then add
the entries. the key names are in /usr/linux/input-event-codes.h, just
lowercase it and remove the KEY_ prefix.

If we can't find any identifying information, you'll have to keep this as a
local override in /etc/udev/hwdb.d/

-- 
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 86223] RFE: Expose SW_LID and SW_TABLET_MODE to compositors

[bugzilla-daemon]

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

--- Comment #6 from Peter Hutterer  ---
updated patchset:
https://lists.freedesktop.org/archives/wayland-devel/2017-January/032540.html

-- 
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 86223] RFE: Expose SW_LID and SW_TABLET_MODE to compositors

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

Summary|Expose SW_LID and   |RFE: Expose SW_LID and
   |SW_TABLET_MODE to   |SW_TABLET_MODE to
   |compositors |compositors

-- 
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 98400] Multimedia Keys not recognized

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEEDINFO|ASSIGNED

-- 
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 98536] RFE: Ignore tablet puck after a timeout

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

Summary|Ignore tablet puck after a  |RFE: Ignore tablet puck
   |timeout |after a timeout
 CC||peter.hutte...@who-t.net

-- 
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 99306] Extremely jittery touchpad

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Peter Hutterer  ---
OK, thanks. I sent a PR to systemd for the override (please give it a test if
you can).

https://github.com/systemd/systemd/pull/5053

I'm closing this bug now but if it's still an issue with this in place, please
re-open, 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 775846] gdk/wayland: Add support for the gtk-enable-primary-paste gsetting

[gtk+]

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

Matthias Clasen  changed:

   What|Removed |Added

 Attachment #343170|none|accepted-commit_now
 status||

--- Comment #5 from Matthias Clasen  ---
Review of attachment 343170:

ok

-- 
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 83884] Recover from missing DRM completion events

[bugzilla-daemon]

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

--- Comment #2 from Link Mauve  ---
I sent an updated and improved version of this patch to wayland-devel, rebased
against master.

Please review: https://patchwork.freedesktop.org/patch/131766/

-- 
You are receiving this mail because:
You are the QA Contact for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 769835] On Wayland, application containing GtkGLArea stops responding if it's not on current workspace

[gtk+]

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

Carlos Garnacho  changed:

   What|Removed |Added

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

--- Comment #25 from Carlos Garnacho  ---
\o/

Attachment 342427 pushed as ab66c3d - wayland: Disable EGL swap interval

-- 
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 769835] On Wayland, application containing GtkGLArea stops responding if it's not on current workspace

[gtk+]

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

Carlos Garnacho  changed:

   What|Removed |Added

 Attachment #342427|accepted-commit_now |committed
 status||

-- 
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 99332] call eglSwapBuffers causes app execution block

[bugzilla-daemon]

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

--- Comment #3 from Daniel Stone  ---
(In reply to Sergey Stepanov from comment #2)
> wl_resource_queue_event(ref->buffer->resource, WL_BUFFER_RELEASE); is
> calling in weston_buffer_reference. Pay attention that
> wl_resource_QUEUE_event used, not wl_resource_POST_event. wl_buffer.release
> event is not sent at this point.
> 
> And, client will NOT receive this event until weston flushes event queue for
> this client. It will happen on wl_resource_post_event (another event posted)
> or wl_client_flush. And there is no proper wl_client_flush. I suppose it is
> some kind of mistake because it is not complies with the protocol.

It's not a mistake, it's a very deliberate choice of behaviour. It's not always
the most optimal behaviour, but it's the behaviour Weston does have, and has
had for years now. Anyone writing an EGL driver must take this into account:
even if it does change in future (and it may), then old versions will still
always behave the same way. And as you are on either version 1.6 or 1.9, any
change upstream would take quite a long time to trickle down to you.

> It works with frame callback because it force to flush events to client
> (wl_resource_post_event flushes queue ). And it works with
> wl_display_roundtrip_queue in the same way.

I'm aware of this.

> I don't think it's a EGL vendor error don't use a frame callback. According
> to wayland protocol it is not obligatory.

Using a frame callback is the only sensible way to implement an EGL swap
interval of 1. A swap interval of 0 does not require frame events, but then it
also requires something to flush the compositor's event queue.

> I'm not sure, but I suppose if we
> use Mesa EGL implementation
> create surface which will not mapped (IVI surface with wrong id for example)
> call eglSwapBuffer twice
> it will block app on eglSwapBuffer call because frame calback will not be
> sent (surface is unmapped), and event queue on the server side will not be
> flushed (and buffer release will not be sent)

That's correct, yes. Sending roundtrips down will provoke the queue being
flushed.

Like I say, it's not necessarily the best behaviour (I argued against it at the
time), but it is well-established behaviour, and any EGL implementation needs
to cope with this if it wants to work with Weston. Even if it were to change in
future, the fact you're using 1.6 means that such a change would take at least
2.5 years to propagate down to you; your EGL implementation could surely be
changed in that 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 775846] gdk/wayland: Add support for the gtk-enable-primary-paste gsetting

[gtk+]

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

--- Comment #4 from Rui Matos  ---
Created attachment 343170
  --> https://bugzilla.gnome.org/attachment.cgi?id=343170=edit
gdk/wayland: Handle non-existant gsettings keys

Since we're a library, crashing on gsettings keys, whose presence is out
of our control, isn't appropriate.
--

I was going to push but realized that unlike other modules, I don't
think gtk+ (particularly the 3-22 branch) can depend on a new enough
gsettings-desktop-schemas, so I think we'll need something like this
patch too.

-- 
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 99332] call eglSwapBuffers causes app execution block

[bugzilla-daemon]

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

--- Comment #2 from Sergey Stepanov  ---
wl_resource_queue_event(ref->buffer->resource, WL_BUFFER_RELEASE); is calling
in weston_buffer_reference. Pay attention that wl_resource_QUEUE_event used,
not wl_resource_POST_event. wl_buffer.release event is not sent at this point.

And, client will NOT receive this event until weston flushes event queue for
this client. It will happen on wl_resource_post_event (another event posted) or
wl_client_flush. And there is no proper wl_client_flush. I suppose it is some
kind of mistake because it is not complies with the protocol.

It works with frame callback because it force to flush events to client
(wl_resource_post_event flushes queue ). And it works with
wl_display_roundtrip_queue in the same way.

I don't think it's a EGL vendor error don't use a frame callback. According to
wayland protocol it is not obligatory.

I'm not sure, but I suppose if we
use Mesa EGL implementation
create surface which will not mapped (IVI surface with wrong id for example)
call eglSwapBuffer twice
it will block app on eglSwapBuffer call because frame calback will not be sent
(surface is unmapped), and event queue on the server side will not be flushed
(and buffer release will not be sent)

-- 
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 776232] [wayland] second click goes to previously right clicked item in titlebar

[gtk+]

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

--- Comment #7 from Olivier Fourdan  ---
Created attachment 343164
  --> https://bugzilla.gnome.org/attachment.cgi?id=343164=edit
[PATCH] wayland: release implicit grab when showing window menu

That patch seems to fix the issue.

--

An implicit grab is set when pressing a button, but when that button
press triggers the xdg-shell show_window_menu, the client never gets
the button release, and the grab remains active, causing the wrong
widget to be triggered when another button press/release is issued.

To avoid this, force a release of the grab when issuing a
show_window_menu so that the next button click works as expected.

-- 
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 769835] On Wayland, application containing GtkGLArea stops responding if it's not on current workspace

[gtk+]

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

Emmanuele Bassi (:ebassi)  changed:

   What|Removed |Added

 Attachment #342427|none|accepted-commit_now
 status||

--- Comment #24 from Emmanuele Bassi (:ebassi)  ---
Review of attachment 342427:

Looks good to me.

-- 
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 99332] call eglSwapBuffers causes app execution block

[bugzilla-daemon]

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

Daniel Stone  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |NOTOURBUG

--- Comment #1 from Daniel Stone  ---
(In reply to Sergey Stepanov from comment #0)
> if we call eglSwapBuffers twice (or even call glClear in EGL mode) it can
> causes app execution block.
>
> I found 2 independent cases:
> 1. eglSwapBuffers implementation does not request wl_surface.frame
> callback(as Mesa do)

You need to take this up with whoever provides your driver. This is your SoC
vendor, not the upstream Wayland project. We (well, most of us) have never seen
that particular driver, and we are unable to supply fixes for it.

> 2. surface is not mapped in weston
> 
> I believe in both cases EGL driver is blocked on waiting wl_buffer.release
> event.
> I suppose it happens because of the next code 
> 
> in function weston_buffer_reference:
> wl_resource_queue_event(ref->buffer->resource,
> WL_BUFFER_RELEASE);
> 
> If there is no other events for the client a message buffer will not be
> flushed. So, client will not receive wl_buffer.release event until other
> event occurred.
> We can implement a workaround by calling display_roundtrip after each
> swapBuffers call, but i believe it is not a proper way.
> 
> I did not check current version (but I took a look at source code,
> implementation is the same) but it is true for 1.6 and 1.9

Yes, the EGL implementation needs to properly ensure that it polls for the
event. The documentation for wl_display_roundtrip_queue() will be useful to
your EGL driver supplier to help figure this out. And also, now that it seems
you have been able to move past libwayland 1.2, your EGL implementation _must_
use a separate event queue on the display, and manage its display queue in
accordance with the suggestions in the documentation.

-- 
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 99332] call eglSwapBuffers causes app execution block

[bugzilla-daemon]

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

Bug ID: 99332
   Summary: call eglSwapBuffers causes app execution block
   Product: Wayland
   Version: unspecified
  Hardware: All
OS: All
Status: NEW
  Severity: minor
  Priority: medium
 Component: weston
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: sergey.stepa...@lge.com

Hi all,

if we call eglSwapBuffers twice (or even call glClear in EGL mode) it can
causes app execution block.
I found 2 independent cases:
1. eglSwapBuffers implementation does not request wl_surface.frame callback(as
Mesa do)
2. surface is not mapped in weston

I believe in both cases EGL driver is blocked on waiting wl_buffer.release
event.
I suppose it happens because of the next code 

in function weston_buffer_reference:
wl_resource_queue_event(ref->buffer->resource, 
WL_BUFFER_RELEASE);

If there is no other events for the client a message buffer will not be
flushed. So, client will not receive wl_buffer.release event until other event
occurred.
We can implement a workaround by calling display_roundtrip after each
swapBuffers call, but i believe it is not a proper way.

I did not check current version (but I took a look at source code,
implementation is the same) but it is true for 1.6 and 1.9

-- 
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 769835] On Wayland, application containing GtkGLArea stops responding if it's not on current workspace

[gtk+]

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

--- Comment #23 from Michael Catanzaro  ---
Going to keep poking about this, since all apps using WebKit are in a really
bad state on Wayland right now:

(In reply to Michael Catanzaro from comment #22)
> (Just want to add: I hope we can do a 3.22 release with this fix soon, since
> it's an extremely high-impact issue for WebKit. Thanks Carlos. :)

-- 
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 776232] [wayland] second click goes to previously right clicked item in titlebar

[gtk+]

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

--- Comment #6 from Olivier Fourdan  ---
The initial button 3 press which triggers the window menu will add a grab (in
proxy_button_event() from gdkwindow.c) and because we don't get a button
release, the grab remains in effect until another press/release occurs, which
triggers the original button.

-- 
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 776232] [wayland] second click goes to previously right clicked item in titlebar

[gtk+]

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

--- Comment #5 from Olivier Fourdan  ---
Still digging...

When the window menu is mapped, the client gets a pointer leave notify (which
is correct, as the menu will show up), and when the menu is dismissed, it gets
an enter notify again.

But then, get_event_window() in gdkwindow.c returns the original button window,
not the actual gdk window, which is what is causing the issue, because gtk will
pick the wrong widget (the GtkButton) based on that wrong gdk window.

-- 
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 99306] Extremely jittery touchpad

[bugzilla-daemon]

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

--- Comment #2 from bitter.ta...@gmx.com ---
(Of course the 7.3mm is an error heh, I meant 73mm)
The output of the `touchpad-edge-detector' is given below:
---
# 
evdev:name:ETPS/2 Elantech
Touchpad:dmi:bvnAmericanMegatrendsInc.:bvrS550CB.201:bd03/04/2013:svnASUSTeKCOMPUTERINC.:pnS550CB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS550CB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:*
 EVDEV_ABS_00=0:3249:31
 EVDEV_ABS_01=0:2223:30
 EVDEV_ABS_35=0:3249:31
 EVDEV_ABS_36=0:2223:30
---

I've manually applied the rule and now the reported size is:
---
Size: 104.81x74.10mm
---

so I guess it's now fine as I couldn't reproduce the "shakey" behaviour during
the brief time I tested the touchpad usage.

-- 
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 772840] [Wayland] clutter stage subsurface needs clipping on Wayland

[clutter]

https://bugzilla.gnome.org/show_bug.cgi?id=772840
Bug 772840 depends on bug 771320, which changed state.

Bug 771320 Summary: [Wayland] Maps widget is displayed at wrong position inside 
gnome-contacts
https://bugzilla.gnome.org/show_bug.cgi?id=771320

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

-- 
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 771320] [Wayland] Maps widget is displayed at wrong position inside gnome-contacts

[clutter-gtk]

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

Olivier Fourdan  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #22 from Olivier Fourdan  ---
Positioning of the widget is now fixed by using gdk subsurfaces (bug 774546)

-- 
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 771320] [Wayland] Maps widget is displayed at wrong position inside gnome-contacts

[clutter-gtk]

https://bugzilla.gnome.org/show_bug.cgi?id=771320
Bug 771320 depends on bug 774546, which changed state.

Bug 774546 Summary: [Wayland][gdk][stage] Use GDK API instead of Wayland 
directly
https://bugzilla.gnome.org/show_bug.cgi?id=774546

   What|Removed |Added

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

-- 
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 99200] Elantech touchpad with libinput has wrong number of buttons

[bugzilla-daemon]

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

--- Comment #14 from Luke  ---
$ cat /sys/class/dmi/id/modalias
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:

Thanks for tying to make the experience less painful.

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