[Wayland-bugs] [Bug 740969] wayland: Provide GIR introspection typelibs

[gtk+]

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

Matthias Clasen  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #6 from Matthias Clasen  ---
I'm going to close this. If somebody is interested enough to work on this, they
can open a new bug or reopen this one. I don't really know what
wayland-specific calls you'd want to make, anyway - I haven't yet found a
reason to use wayland-specific API in gtk itself.

-- 
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 94474] Middle button support on Asus Zenbooks

[bugzilla-daemon]

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

--- Comment #9 from Peter Hutterer  ---
for the archives: Pander's actual device is one of the Asus Zenbook Prime
UX31A/UX21A/UX32V, see the gnome bug.

I looked at a few pictures, afacit the line is just a line drawn onto the
touchpad. there is nothing inherent about the line from a physical point and
the touchpad doesn't care where in relation to the line you touch.

testing this on my touchpad here with software buttons enabled: middle-button
emulation works on software buttons and it works for middle button dragging.
click with a finger in both the left and right area simultaneously, then use
either finger to move while keeping the other finger to hold the button down.
The middle button is not released until the click releases.

the same is true for clickfinger, click with three fingers to trigger a middle
button click, release two fingers and use the remaining finger to drag. The
middle button is not released until the click releases.

-- 
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 763859] New: gdkdevice-wayland.c cleanups

[gtk+]

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

Bug ID: 763859
   Summary: gdkdevice-wayland.c cleanups
Classification: Platform
   Product: gtk+
   Version: unspecified
OS: Linux
Status: NEW
  Severity: normal
  Priority: Normal
 Component: Backend: Wayland
  Assignee: gtk-b...@gtk.org
  Reporter: carl...@gnome.org
QA Contact: gtk-b...@gtk.org
CC: r...@robster.org.uk, wayland-bugs@lists.freedesktop.org
 GNOME version: ---

When GdkSeat was introduced, the older GdkWaylandDeviceData (that mostly
represented a seat) was renamed to GdkWaylandSeat, but a typedef to
GdkWaylandDeviceData was kept around, as the changes were too many, too
unrelated, and would create many conflicts with patches/branches that were
pending merging.

Now that the situation is more or less clear, I'm attaching some patches doing
this cleanup. Further future refactoring might split this into
gdkseat-wayland.[ch] and gdkdevice-wayland.[ch] so we don't manage all of
GdkSeat+GdkDeviceManager+GdkDevice (+ parts of GdkDragContext) in a single C
file, I'll refrain from this till wip/tablet-support is merged though.

The patches are basically a manual search and replace, sanity checks/review
appreciated though.

-- 
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 763859] gdkdevice-wayland.c cleanups

[gtk+]

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

Matthias Clasen  changed:

   What|Removed |Added

 Attachment #324248|none|reviewed
 status||

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

Does the gdkdevice-wayland.c belong into the previous patch ? Or maybe a
separate one. In any case, it might be nice to have "Remove unused typedef" be
a separate patch that does just that.

-- 
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 93448] Trackpoint speed lock

[bugzilla-daemon]

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

--- Comment #6 from Juraj Fiala  ---
Created attachment 122420
  --> https://bugs.freedesktop.org/attachment.cgi?id=122420=edit
trackpoint speed lock recording

-- 
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 94601] unexpected scroll event 0 in area state

[bugzilla-daemon]

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

Bug ID: 94601
   Summary: unexpected scroll event 0 in area state
   Product: Wayland
   Version: 1.2.x
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
  Severity: normal
  Priority: medium
 Component: libinput
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: ma...@crepererum.net

Created attachment 122389
  --> https://bugs.freedesktop.org/attachment.cgi?id=122389=edit
evemu record

Description:
Sometimes the touch pad "tab" function stops working. See "steps to reproduce"
for more details. The problem was introduced recently (before the system worked
totally fine for over 6 months)


Additional info:
* libinput 1.2.2
* xf86-input-libinput 0.17.0
* system is a Lenovo Carbon X1, 2015 edition (3rd gen)
* touchpad dimensions: 100mm w X 55mm h
* kernel is 4.4.5.201603142220-1-grsec (Arch Linux)


evemu recording:
see attachement, the bug happens somewhere at the end, than I used the
"scroll-around" work-around and got a tab-driven click working (see "Steps to
reproduce" section)


/sys/class/dmi/id/modalias:
dmi:bvnLENOVO:bvrN14ET31W(1.09):bd06/26/2015:svnLENOVO:pn20BTS2EJ00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS2EJ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:


xinput list-props:
Device 'SynPS/2 Synaptics TouchPad':
Device Enabled (138):   1
Coordinate Transformation Matrix (140): 1.00, 0.00, 0.00,
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Tapping Enabled (277): 1
libinput Tapping Enabled Default (278): 0
libinput Tapping Drag Enabled (279):1
libinput Tapping Drag Enabled Default (280):1
libinput Tapping Drag Lock Enabled (281):   0
libinput Tapping Drag Lock Enabled Default (282):   0
libinput Accel Speed (283): 0.488789
libinput Accel Speed Default (284): 0.00
libinput Natural Scrolling Enabled (285):   1
libinput Natural Scrolling Enabled Default (286):   0
libinput Send Events Modes Available (261): 1, 1
libinput Send Events Mode Enabled (262):0, 0
libinput Send Events Mode Enabled Default (263):0, 0
libinput Left Handed Enabled (287): 0
libinput Left Handed Enabled Default (288): 0
libinput Scroll Methods Available (289):1, 1, 0
libinput Scroll Method Enabled (290):   1, 0, 0
libinput Scroll Method Enabled Default (291):   1, 0, 0
libinput Click Methods Available (292): 1, 1
libinput Click Method Enabled (293):1, 0
libinput Click Method Enabled Default (294):1, 0
libinput Disable While Typing Enabled (295):1
libinput Disable While Typing Enabled Default (296):1
Device Node (264):  "/dev/input/event10"
Device Product ID (265):2, 7
libinput Drag Lock Buttons (297):   
libinput Horizonal Scroll Enabled (266):1





Kernel synaptics boot log:
psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758]
psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..]
psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps:
0xf003a3/0x943300/0x12e800/0x1, board id: 3072, fw id: 1795685
psmouse serio1: synaptics: serio: Synaptics pass-through port at
isa0060/serio1/input0



Steps to reproduce:
Work with the touchpad (tab and scroll around), after a while, the tab feature
isn't working anymore, but scrolling and mouse movement seems to behave as
expected. The logs show the following information
/usr/lib/gdm/gdm-x-session[]: (EE) libinput bug: unexpected scroll event 0
in area state

The tab feature can be restored using one of the following work-arounds:
* go to the GNOME system settings and disable and re-enable the tab settings
* try to "scroll" using 3 fingers, after some tries the libinput seems to
behave normally again

-- 
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 763350] drawing performance worse than X

[gtk+]

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

Ray Strode [halfline]  changed:

   What|Removed |Added

 Attachment #324154|none|accepted-commit_after_freez
 status||e

--- Comment #44 from Ray Strode [halfline]  ---
Review of attachment 324154:

Makes sense.  If we can avoid allocating the extra buffer in the first place,
since the size isn't changing that then that seems like the right way to go 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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #50 from Ray Strode [halfline]  ---
Created attachment 324185
  --> https://bugzilla.gnome.org/attachment.cgi?id=324185=edit
mutter: hack in some timings

-- 
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 89966] protocol: XML files need to be installed and discoverable

[bugzilla-daemon]

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

--- Comment #2 from Pekka Paalanen  ---
Just a minor correction: weston-desktop-shell.xml has nothing to do with
xdg-shell.xml. Weston-desktop-shell.xml is the private protocol used between
the DE components specific to Weston, while xdg-shell.xml is a public protocol
for all apps.

Proposals to generalize or publish things related to weston-desktop-shell.xml
should be new protocol extensions of their own. That stuff does not belong in
xdg-shell.xml.

Of course, nothing prevents promoting weston-desktop-shell.xml into
wayland-protocols, *if* it is deemed necessary. But while libweston is still
seeking form, I'd advice to wait.

-- 
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 91949] Add support for drag actions

[bugzilla-daemon]

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

Michael Catanzaro  changed:

   What|Removed |Added

 CC||mcatanz...@gnome.org
 Resolution|--- |FIXED
 Status|NEW |RESOLVED

-- 
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 763859] gdkdevice-wayland.c cleanups

[gtk+]

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

--- Comment #2 from Carlos Garnacho  ---
Created attachment 324248
  --> https://bugzilla.gnome.org/attachment.cgi?id=324248=edit
wayland: Remove GdkWaylandDeviceData typedef

And let GdkWaylandSeat be the only one. All the remaining places
using GdkWaylandDeviceData have been updated, and so are its variable
names.

-- 
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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #48 from Ray Strode [halfline]  ---
So i did a scratch patch (will attach it) just to get some timings with and
without christian's fix:

a time to draw: 8.5ms
b time from wl_event_loop_dispatch until wl_surface_commit is called: 4.4ms
c time spent allocating the texture in mutter: 6ms
d time spent copying the buffer to the texture in mutter: 5ms

with patch

a time to draw: 3.8ms
b time from wl_event_loop_dispatch until wl_surface_commit is called: .055ms
c time spent allocating the texture in mutter: .004ms
d time spent copying the buffer to the texture in mutter: 5.7ms

-- 
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 91943] weston-dnd leaks memory allocated in create_drag_icon()

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=91943
Bug 91943 depends on bug 91944, which changed state.

Bug 91944 Summary: wl_data_source should have an event to indicate completion 
of a drag session
https://bugs.freedesktop.org/show_bug.cgi?id=91944

   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 91948] Tracker bug for issues with drag-and-drop

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=91948
Bug 91948 depends on bug 91945, which changed state.

Bug 91945 Summary: Protocol documentation should indicate when 
wl_data_offer::receive requests should be sent
https://bugs.freedesktop.org/show_bug.cgi?id=91945

   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 86956] Adjusting screen brightness has long delay, hard to use slider

[bugzilla-daemon]

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

Bryce Harrington  changed:

   What|Removed |Added

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

--- Comment #1 from Bryce Harrington  ---
That sounds like a problem with the settings application for GNOME, rather than
something pertaining to the Wayland protocol.

I suspect chances are good that in the intervening time since this was
reported, the issue has already been resolved.  But if not, please re-file the
bug with Fedora rather than here.

-- 
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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #46 from Ray Strode [halfline]  ---
One other thing I don't quite understand is why your scratch patch to allocate
the 2nd buffer up front didn't help.

-- 
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 94582] git url not working

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

 CC||peter.hutte...@who-t.net
 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED

--- Comment #1 from Peter Hutterer  ---
anongit was taken offline to handle the git CVE. you can still clone via
http://anongit...

closing as WORKSFORME, there's a workaround and I expect this to be back very
soon. please reopen if it's still broken in a day or two

-- 
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 763859] gdkdevice-wayland.c cleanups

[gtk+]

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

--- Comment #7 from Matthias Clasen  ---
Review of attachment 324249:

Sure, looks fine 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 91944] wl_data_source should have an event to indicate completion of a drag session

[bugzilla-daemon]

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

Michael Catanzaro  changed:

   What|Removed |Added

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

--- Comment #1 from Michael Catanzaro  ---
We now have wl_data_offer::finish

-- 
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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #56 from Ray Strode [halfline]  ---
(In reply to Ray Strode [halfline] from comment #45)
> I don't think the frame clock timings are used

So just to follow up here. We had a discussion with Owen on IRC.  The frame
timings are intentionally unused by the frame clock for regular updates. frame
rate is throttled by the compositor, so we don't need separate timers client
side.  The frame timings are mainly for video player type applications such as
this:

https://git.gnome.org/browse/gtk+/tree/tests/video-timer.c

-- 
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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #47 from Ray Strode [halfline]  ---
(In reply to Christian Hergert from comment #42)
> Created attachment 324158 [details] [review]
> updated cogl patch for clock discovery
> 
> It still requires investigation to determine why this patch for cogl and the
> mutter patch cause frame timings to be invalid. But, figured I'd update this
> for future reference.

maybe CLOCK_MONOTONIC_RAW versus CLOCK_MONOTONIC ?  why doesn't it just use
g_get_monotonic_clock instead of calling clock_gettime directly btw?

-- 
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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #55 from Ray Strode [halfline]  ---
(In reply to Matthias Clasen from comment #53)
> this may just be because we were unconditionally throwing away both buffers
> in the configure event ?

I guess that's possible, but sysprof showed the shmem fault overhead going away
after his 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 763852] gdk/wayland: event source is not multi-thread aware

[gtk+]

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

Matthew Waters (ystreet00)  changed:

   What|Removed |Added

 Attachment #324239|0   |1
is obsolete||

--- Comment #8 from Matthew Waters (ystreet00)  ---
Created attachment 324334
  --> https://bugzilla.gnome.org/attachment.cgi?id=324334=edit
gdk/wayland: use the multi-thread safe wayland dispatching API

This contains a small change to fix a deadlock explained below.

The scenario is two GMainLoops with separate GSource's polling the same wayland
fd.

Source 1 in Thread 1 can be woken up from another GSource (timeout, idle, frame
clock, ...) becoming ready calling _check(). There has been no write/activity
on the wayland fd so revents is 0.  Thread 2, Source 2 is still in poll() as it
has not been woken up.  Source 1 calling wl_display_read_events() in _check()
in this case will block on a condition waiting for Source 2 to exit poll() and
call wl_display_read_events() or wl_display_cancel_read() which will not occur
until e.g. the user provides some input and causes Thread 2's poll() to wake
up.

Fix is to only wl_display_read_events() on actual fd activity (signalled
through (revents & G_IO_IN)) and _cancel_read() in all other cases.

-- 
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 94562] compositor-drm.c memcmp use incorrect pointer leads stack-buffer-overflow

[bugzilla-daemon]

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

Pekka Paalanen  changed:

   What|Removed |Added

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

--- Comment #3 from Pekka Paalanen  ---
commit 7a5c562d1aa7e893f0a0910a3f6860b450127acd
Author: comic fans 
Date:   Thu Mar 17 14:29:27 2016 +0200

compositor-drm: fix memcmp using a bad pointer in
drm_outout_choose_initial_mode

-- 
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 91948] Tracker bug for issues with drag-and-drop

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=91948
Bug 91948 depends on bug 91944, which changed state.

Bug 91944 Summary: wl_data_source should have an event to indicate completion 
of a drag session
https://bugs.freedesktop.org/show_bug.cgi?id=91944

   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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #49 from Ray Strode [halfline]  ---
so a is 5ms shorter because we don't have to allocate the buffer before drawing
   b is 4ms shorter because the compositor doesn't have to import the new
buffer
   c is a noop with the patch since the texture is already set
   d is about the same (which makes sense)

-- 
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 94429] Weston dosn't start with gma500 (Poulsbo) driver

[bugzilla-daemon]

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

--- Comment #18 from Pekka Paalanen  ---
(In reply to Pietro Sam from comment #17)
> Created attachment 122374 [details]
> Xwayland error log

You have not installed Xwayland yet.

I'd be more worried about the "queueing pageflip failed" messages, though.
Maybe the poulsbo driver in the kernel is... lacking.

Anyway, nothing we can do for you here about the GMA500.

-- 
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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #39 from Christian Hergert  ---
Created attachment 324154
  --> https://bugzilla.gnome.org/attachment.cgi?id=324154=edit
avoid dropping our shm-based surface on configure-event

Here is an easy one.

The memfd_create() was getting called not because the committed buffer had not
yet been returned, but simply because a configure-event came in due to
animation widget resizing. We unconditionally dropped the surfaces when we
could reuse the existing ones if sizing did not actually change.

-- 
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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #53 from Matthias Clasen  ---
(In reply to Ray Strode [halfline] from comment #46)
> One other thing I don't quite understand is why your scratch patch to
> allocate the 2nd buffer up front didn't help.

this may just be because we were unconditionally throwing away both buffers in
the configure event ?

-- 
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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #51 from Ray Strode [halfline]  ---
Created attachment 324186
  --> https://bugzilla.gnome.org/attachment.cgi?id=324186=edit
gdk-wayland: hack in some timings

-- 
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 763859] gdkdevice-wayland.c cleanups

[gtk+]

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

--- Comment #3 from Carlos Garnacho  ---
Created attachment 324249
  --> https://bugzilla.gnome.org/attachment.cgi?id=324249=edit
wayland: Rename internal functions with misleading naming

Now that GdkWaylandDeviceData is gone, the functions prefixed
"gdk_wayland_device_" and taking a GdkWaylandSeat as first
parameter feel out of place. Renaming those makes it more obvious
that it's seat functions.

-- 
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 94474] Middle button support on Asus Zenbooks

[bugzilla-daemon]

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

--- Comment #10 from Pander  ---
"click with a finger in both the left and right area simultaneously, then use
either finger to move while keeping the other finger to hold the button down."
will not work. I will send you an email with a link to a movie where I
demonstrate this.

-- 
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 83429] Wayland documentation meta-bug

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=83429
Bug 83429 depends on bug 91947, which changed state.

Bug 91947 Summary: Protocol documentation should indicate when 
wl_data_source::cancelled events will be sent
https://bugs.freedesktop.org/show_bug.cgi?id=91947

   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 763859] gdkdevice-wayland.c cleanups

[gtk+]

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

--- Comment #10 from Carlos Garnacho  ---
Created attachment 324269
  --> https://bugzilla.gnome.org/attachment.cgi?id=324269=edit
wayland: Remove GdkWaylandDataDevice typedef

It's no longer used.

-- 
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 763350] drawing performance worse than X

[gtk+]

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

Christian Hergert  changed:

   What|Removed |Added

 Attachment #324038|0   |1
is obsolete||

--- Comment #42 from Christian Hergert  ---
Created attachment 324158
  --> https://bugzilla.gnome.org/attachment.cgi?id=324158=edit
updated cogl patch for clock discovery

It still requires investigation to determine why this patch for cogl and the
mutter patch cause frame timings to be invalid. But, figured I'd update this
for future reference.

-- 
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 763852] gdk/wayland: event source is not multi-thread aware

[gtk+]

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

Matthew Waters (ystreet00)  changed:

   What|Removed |Added

 CC||ystree...@gmail.com

--- Comment #1 from Matthew Waters (ystreet00)  ---
Created attachment 324232
  --> https://bugzilla.gnome.org/attachment.cgi?id=324232=edit
gdk/wayland: use the multi-thread safe wayland dispatching API

-- 
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 763859] gdkdevice-wayland.c cleanups

[gtk+]

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

--- Comment #1 from Carlos Garnacho  ---
Created attachment 324247
  --> https://bugzilla.gnome.org/attachment.cgi?id=324247=edit
wayland: Remove GdkWaylandDeviceData pointer in GdkWaylandDevice

It's the same than gdk_device_get_seat() nowadays. Also, rename the
usages of GdkWaylandDeviceData to GdkWaylandSeat in the functions
affected by the removal.

-- 
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 763859] gdkdevice-wayland.c cleanups

[gtk+]

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

Matthias Clasen  changed:

   What|Removed |Added

 Attachment #324249|none|accepted-commit_after_freez
 status||e

--- Comment #6 from Matthias Clasen  ---
Review of attachment 324249:

Sure, looks fine 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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #40 from Christian Hergert  ---
Created attachment 324156
  --> https://bugzilla.gnome.org/attachment.cgi?id=324156=edit
predicted presentation times

I'm going to add some updated patches for cogl and mutter, but I'm unconvinced
that we need them yet. Simply applying the gdk-wayland patch above gets us
almost all the way there.

The reason I'm suggesting not using the cogl and mutter patches will be obvious
by looking at the attached graph.

Notice how the predicted timing is 25msec across the board. This is what
happens when GdkFrameClock can't predict the timing and so it guesses "half-way
between frame". 16.7+8.35=25.5

I've been playing around with various tweaks in mutter and cogl and so far have
been unable to improve that. I thought that was the original problem and so I
focused on it far longer than I'm happy to admit.

-- 
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 763350] drawing performance worse than X

[gtk+]

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

--- Comment #54 from Christian Hergert  ---
(In reply to Ray Strode [halfline] from comment #47)
> > It still requires investigation to determine why this patch for cogl and the
> > mutter patch cause frame timings to be invalid. But, figured I'd update this
> > for future reference.
> 
> maybe CLOCK_MONOTONIC_RAW versus CLOCK_MONOTONIC ?  why doesn't it just use
> g_get_monotonic_clock instead of calling clock_gettime directly btw?

I played with this about 20 different ways. Every clock type, fudging values,
etc etc.

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