[Wayland-bugs] [Bug 759299] wayland: possible infinite loop in gdkwindow-wayland

https://bugzilla.gnome.org/show_bug.cgi?id=759299 Olivier Fourdan changed: What|Removed |Added See Also|

[Wayland-bugs] [Bug 755947] wayland: gnome-terminal does not fill entire area when tiled

https://bugzilla.gnome.org/show_bug.cgi?id=755947 Matthias Clasen changed: What|Removed |Added CC||mcla...@redhat.com

[Wayland-bugs] [Bug 755947] wayland: gnome-terminal does not fill entire area when tiled

https://bugzilla.gnome.org/show_bug.cgi?id=755947 Matthias Clasen changed: What|Removed |Added Status|NEW |RESOLVED

[Wayland-bugs] [Bug 759429] Wayland windows don't have minimize and maximize buttons

https://bugzilla.gnome.org/show_bug.cgi?id=759429 --- Comment #5 from Matthias Clasen --- What does echo $XDG_CURRENT_DESKTOP say ? The wayland backend reads the button-layout setting from either of these places, depending on the value of that environment variable #define

[Wayland-bugs] [Bug 759299] wayland: possible infinite loop in gdkwindow-wayland

https://bugzilla.gnome.org/show_bug.cgi?id=759299 --- Comment #12 from Matthias Clasen --- (In reply to Olivier Fourdan from comment #11) > I reckon you need to set the transient_for first to walk up the tree and > detect all possibilities. > > Consider this case, two valid

[Wayland-bugs] [Bug 754110] inconsistent interpretation of preserved modifiers with xkbcommon

https://bugzilla.gnome.org/show_bug.cgi?id=754110 --- Comment #27 from Carlos Garnacho --- The bit counting (and why I think Daniel things it's not such a general fix) was added because I'm not sure what's best to do if there's more than one modifier pressed in the mask, I see

[Wayland-bugs] [Bug 755625] wayland: support dnd actions

https://bugzilla.gnome.org/show_bug.cgi?id=755625 Matthias Clasen changed: What|Removed |Added CC||mcla...@redhat.com

[Wayland-bugs] [Bug 93315] Automatically scale windows?

https://bugs.freedesktop.org/show_bug.cgi?id=93315 --- Comment #10 from Olivier Fourdan --- (In reply to Daniel Stone from comment #9) > (In reply to Alexander Larsson from comment #8) > > Could we run two xwayland instances? first display is lodpi, and second is > > hidpi?

[Wayland-bugs] [Bug 759299] wayland: possible infinite loop in gdkwindow-wayland

https://bugzilla.gnome.org/show_bug.cgi?id=759299 --- Comment #5 from Olivier Fourdan --- Right. Actually I think it's even worse than that, because by walking up the transient tree, we may run into the cycle loop. And checking for transient depth here won't help, because

[Wayland-bugs] [Bug 759429] Wayland windows don't have minimize and maximize buttons

https://bugzilla.gnome.org/show_bug.cgi?id=759429 --- Comment #6 from Ben --- XDG_CURRENT_DESKTOP = 'GNOME' Both GSettings entries have minimize and maximize Additionally, if i run a program from jhbuild it works fine, but I don't know whether jhbuild has a separate

[Wayland-bugs] [Bug 93315] Automatically scale windows?

https://bugs.freedesktop.org/show_bug.cgi?id=93315 --- Comment #14 from Daniel Stone --- (In reply to Alexander Larsson from comment #12) > I don't think that is really a problem though. > > not dynamic: We could just always allocate a scale 2 screen. > > can't blit

[Wayland-bugs] [Bug 759299] wayland: possible infinite loop in gdkwindow-wayland

https://bugzilla.gnome.org/show_bug.cgi?id=759299 --- Comment #7 from Olivier Fourdan --- (In reply to Matthias Clasen from comment #6) > Well, walking up the tree, you check for either hitting NULL (good) or > yourself (bad). Yes, exactly, we don't need a transient depth,

[Wayland-bugs] [Bug 759299] wayland: possible infinite loop in gdkwindow-wayland

https://bugzilla.gnome.org/show_bug.cgi?id=759299 --- Comment #6 from Matthias Clasen --- (In reply to Olivier Fourdan from comment #5) > Right. > > Actually I think it's even worse than that, because by walking up the > transient tree, we may run into the cycle loop. Well,

[Wayland-bugs] [Bug 759299] wayland: possible infinite loop in gdkwindow-wayland

https://bugzilla.gnome.org/show_bug.cgi?id=759299 Olivier Fourdan changed: What|Removed |Added Attachment #317380|0 |1 is

[Wayland-bugs] [Bug 759299] wayland: possible infinite loop in gdkwindow-wayland

https://bugzilla.gnome.org/show_bug.cgi?id=759299 --- Comment #8 from Olivier Fourdan --- Created attachment 317426 --> https://bugzilla.gnome.org/attachment.cgi?id=317426=edit wayland: Check transient loop Note, this patch tries to avoid the problem by setting the

[Wayland-bugs] [Bug 759299] wayland: possible infinite loop in gdkwindow-wayland

https://bugzilla.gnome.org/show_bug.cgi?id=759299 --- Comment #9 from Olivier Fourdan --- Created attachment 317427 --> https://bugzilla.gnome.org/attachment.cgi?id=317427=edit A slightly more elaborate reproducer This reproducer will hang mutter/gnome-shell with an

[Wayland-bugs] [Bug 93315] Automatically scale windows?

https://bugs.freedesktop.org/show_bug.cgi?id=93315 --- Comment #11 from Daniel Stone --- (In reply to Olivier Fourdan from comment #10) > Not sure if that'd be workable, but What about 2 screens of the same display > then (:0.0 and :0.1)? Each could have its own

[Wayland-bugs] [Bug 759299] wayland: possible infinite loop in gdkwindow-wayland

https://bugzilla.gnome.org/show_bug.cgi?id=759299 --- Comment #13 from Olivier Fourdan --- Yeah, you're right of course, it's obvious... Let's blame that on a temporary (or so I hope ^_~) mental fog on my side :-) -- You are receiving this mail because: You are on the CC

[Wayland-bugs] [Bug 759299] wayland: possible infinite loop in gdkwindow-wayland

https://bugzilla.gnome.org/show_bug.cgi?id=759299 Matthias Clasen changed: What|Removed |Added Attachment #317426|none|reviewed

[Wayland-bugs] [Bug 93315] Automatically scale windows?

https://bugs.freedesktop.org/show_bug.cgi?id=93315 --- Comment #12 from Alexander Larsson --- I don't think that is really a problem though. not dynamic: We could just always allocate a scale 2 screen. can't blit across screens: When would you need that. Apps would generally

[Wayland-bugs] [Bug 759299] wayland: possible infinite loop in gdkwindow-wayland

https://bugzilla.gnome.org/show_bug.cgi?id=759299 --- Comment #11 from Olivier Fourdan --- I reckon you need to set the transient_for first to walk up the tree and detect all possibilities. Consider this case, two valid and distinct transient trees (where "->" means "is