[Wayland-bugs] [Bug 98904] Race condition when mouse and/or keyboard randomly doesn't work upon fresh boot - Thinkpad Yoga S1

2016-12-01 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=98904

Peter Hutterer  changed:

   What|Removed |Added

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

--- Comment #1 from Peter Hutterer  ---
fwiw, xinput list from within wayland doesn't provide us with much info, all
you get is the xwayland emulated devices. something is going wrong here, can
you attach the journalctl -b -k output here please.

I guess this means you can't get past the login screen? What happens if you
boot into a tty, does it work then?

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

2016-12-01 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=757942

--- Comment #36 from Christian Stadelmann  ---
Hm, I'm still seeing this issue¹ rarely, and it is not limited to XWayland
applications. Can you please reopen this bug or shall I create a new one?

¹ to be more specific: under high load, letters typed into text fields of any
application get repeated.

I'm running Fedora 25 with
xorg-x11-server-Xwayland-1.19.0-1.fc25.x86_64
gnome-shell-3.22.2-2.fc25.x86_64
mutter-3.22.2-1.fc25.x86_64
libwayland-client-1.12.0-1.fc25.x86_64

-- 
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 98927] rotation

2016-12-01 Thread bugzilla-daemon 
https://bugs.freedesktop.org/show_bug.cgi?id=98927

Bug ID: 98927
   Summary: rotation
   Product: Wayland
   Version: unspecified
  Hardware: Other
OS: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: wayland
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: c...@wpi.edu

-- 
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 775470] GdkWindow does not always unref all GdkFrameClockIdle it creates

2016-12-01 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=775470

Olivier Fourdan  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #5 from Olivier Fourdan  ---


*** This bug has been marked as a duplicate of bug 774915 ***

-- 
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 774915] [Wayland]: Destroying the parent of a subsurface causes _gdk_window_destroy_hierarchy: assertion failed

2016-12-01 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=774915

Olivier Fourdan  changed:

   What|Removed |Added

 CC||sixty...@inwind.it

--- Comment #3 from Olivier Fourdan  ---
*** Bug 775470 has been marked as a duplicate of this bug. ***

-- 
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 775470] GdkWindow does not always unref all GdkFrameClockIdle it creates

2016-12-01 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=775470

--- Comment #4 from Olivier Fourdan  ---
With attachment 340598  I see "GdkFrameClockIdle  ref_count=1" in all cases
(ITERATIONS=1, ITERATIONS=2 and even ITERATIONS=100)

-- 
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 775470] GdkWindow does not always unref all GdkFrameClockIdle it creates

2016-12-01 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=775470

--- Comment #3 from Massimo  ---
(In reply to Olivier Fourdan from comment #2)
> Ah! my bad, the patch is not reviewed/merged yet, so I guess this might be a
> duplicate of bug 774915, can you try attachment 340598 [details] [review] to
> see if this helps here as well?

yes that attachment would fix the problem.

-- 
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 775470] GdkWindow does not always unref all GdkFrameClockIdle it creates

2016-12-01 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=775470

--- Comment #2 from Olivier Fourdan  ---
Ah! my bad, the patch is not reviewed/merged yet, so I guess this might be a
duplicate of bug 774915, can you try attachment 340598 to see if this helps
here as well?

-- 
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 775470] GdkWindow does not always unref all GdkFrameClockIdle it creates

2016-12-01 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=775470

Olivier Fourdan  changed:

   What|Removed |Added

 CC||ofour...@redhat.com

--- Comment #1 from Olivier Fourdan  ---
(In reply to Massimo from comment #0)
> [...]
> The problem is that on Wayland popover GdkWindow have window_type
> GDK_WINDOW_SUBSURFACE
> 
> and gdk_window_destroy (_gdk_window_destroy_hierarchy) does nearly nothing
> for this kind of GdkWindow:
> [...]

In current master and gtk-3-22 git branch, this is not the case anymore, does
commit 893ed4e from bug 774915 help here?

-- 
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 775470] New: GdkWindow does not always unref all GdkFrameClockIdle it creates

2016-12-01 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=775470

Bug ID: 775470
   Summary: GdkWindow does not always unref all GdkFrameClockIdle
it creates
Classification: Platform
   Product: gtk+
   Version: 3.22.x
OS: Linux
Status: NEW
  Severity: normal
  Priority: Normal
 Component: Backend: Wayland
  Assignee: gtk-b...@gtk.org
  Reporter: sixty...@inwind.it
QA Contact: gtk-b...@gtk.org
CC: r...@robster.org.uk, wayland-bugs@lists.freedesktop.org
 GNOME version: ---

After setting GOBJECT_DEBUG=objects comparing the outputs
of the following program run with ITERATIONS set to 2 and 1:

#include 

#ifndef ITERATIONS
#define ITERATIONS 1
#endif

int
main (int   argc,
  char *argv[])
{
  if (gtk_init_check (, ))
{
  int i;
  for (i = 0; i < ITERATIONS; ++i)
{
  GtkWidget *dialog;
  dialog = gtk_file_chooser_dialog_new ("Open File",
NULL,
GTK_FILE_CHOOSER_ACTION_OPEN,
"Cancel", GTK_RESPONSE_CANCEL,
NULL);
  gtk_widget_show_all (dialog);
  gtk_widget_destroy (dialog);
}
}

  return 0;
}

on Wayland the number of objects alive at exit increases for the 
presence of few GdkFrameClockIdle objects.

The problem is that on Wayland popover GdkWindow have window_type
GDK_WINDOW_SUBSURFACE

https://git.gnome.org/browse/gtk+/tree/gtk/gtkwindow.c?h=gtk-3-22#n6647

and gdk_window_destroy (_gdk_window_destroy_hierarchy) does nearly nothing
for this kind of GdkWindow:

https://git.gnome.org/browse/gtk+/tree/gdk/gdkwindow.c?h=gtk-3-22#n2019

in particular it does not unref GdkFrameClockIdle objects it
creates.

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

2016-12-01 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=769835

Jean-François Fortin Tam  changed:

   What|Removed |Added

 CC||nekoh...@gmail.com
 Blocks||695806

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

2016-12-01 Thread gtk+ 
https://bugzilla.gnome.org/show_bug.cgi?id=769835

Jonas Ådahl  changed:

   What|Removed |Added

 CC||r...@robster.org.uk,
   ||wayland-bugs@lists.freedesk
   ||top.org
  Component|wayland |Backend: Wayland
   Assignee|mutter-ma...@gnome.bugs |gtk-b...@gtk.org
Product|mutter  |gtk+
 QA Contact|mutter-ma...@gnome.bugs |gtk-b...@gtk.org

--- Comment #9 from Jonas Ådahl  ---
(moving back to gtk+ since this is about frame throttling getting away of
unrelated IO)

I think that, for whatever reason a frame is scheduled (be it because some
focus-out animation or an application deliberately asking for it for whatever
reason), we should still handle the situation where we actually don't want to
paint because of the vsync throttling.

As far as I can see, we use _gdk_frame_clock_freeze() and
_gdk_frame_clock_thaw() to do the throttling, but maybe what we really should
do is gdk_window_freeze_updates()/gdk_window_thaw_updates()? We handle those
here and there in gdkwindow-wayland.c (the checking of
window->update_freeze_count).

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