[Wayland-bugs] [Bug 96953] dri2_wl_swrast crashes on 64 bit, but not on 32 bit
https://bugs.freedesktop.org/show_bug.cgi?id=96953 --- Comment #3 from n3rdopolis --- I tried a recent recompile, this still appears to be happening, 64 bit only. 32 bit is fine -- 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 771915] [Wayland]: Totem window misplaced after a state change
https://bugzilla.gnome.org/show_bug.cgi?id=771915 --- Comment #10 from Bjørn Lie --- Well damn... I have irccloud.com as a epbiy webapp, and that one just keeps on working fine (before it would crash and die as soon as I tried to resize/maximize the window), so I went ahead and made bugzilla.gnome.org a web-app, and that does indeed crash and die as soon as I try to launch it. Sorry for the noise. -- 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 771913] [gnome-terminal][wayland] can't tear off tab to new window
https://bugzilla.gnome.org/show_bug.cgi?id=771913 Matthias Clasen changed: What|Removed |Added CC||mcla...@redhat.com --- Comment #3 from Matthias Clasen --- (In reply to Christian Persch from comment #1) > I think this was fixed by bug 763387. > > (Note that DND tab detaching was disabled in gnome-terminal >= 3.20.3 due to > it crashing the application.) If it was fixed, will tab detaching be reenabled at some point ? -- 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 771553] Shrinking window generates a black patch when gl is used
https://bugzilla.gnome.org/show_bug.cgi?id=771553 Gustavo Noronha (kov) changed: What|Removed |Added CC||dyske...@gmail.com --- Comment #12 from Gustavo Noronha (kov) --- *** Bug 771944 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 97932] wl_shell: Does not emit configure event
https://bugs.freedesktop.org/show_bug.cgi?id=97932 --- Comment #1 from Nicolas Dufresne --- I just tested on weston 1.10, and this works properly, so I can confirm now this is a recent regression. -- 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 97932] wl_shell: Does not emit configure event
https://bugs.freedesktop.org/show_bug.cgi?id=97932 Bug ID: 97932 Summary: wl_shell: Does not emit configure event Product: Wayland Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: weston Assignee: wayland-bugs@lists.freedesktop.org Reporter: nico...@ndufresne.ca Created attachment 126789 --> https://bugs.freedesktop.org/attachment.cgi?id=126789&action=edit Modified presentation example to trace the wl_shell configure event I haven't tried before, so I can't say if it's a regression, though the configure event is never emmited (while it seems to work with xdg_shell). This was tested using GStreamer waylandsink (master) with combination of Weston super+right-click operation. To help reproduce, I have modified presentation-shm to trace this event. When I try to resize, I only get notified sometimes, and with the same width/height as the current one. -- 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 771915] [Wayland]: Totem window misplaced after a state change
https://bugzilla.gnome.org/show_bug.cgi?id=771915 --- Comment #9 from Olivier Fourdan --- (In reply to Olivier Fourdan from comment #5) > I suspect this bug here is caused by the correct shadow border being applied > sooner (required to set the correct min/max size, see bug 771561), which > sets the right container size sooner and somehow shortcuts the update of > abs_x/abs_y in recompute_visible_regions_internal(), or something along > these lines... Quick folllow-up on my previous comment, the shortcut in question is in gtk_widget_size_allocate_with_baseline(): https://git.gnome.org/browse/gtk+/tree/gtk/gtkwidget.c#n6101 6102: if (!alloc_needed && !size_changed && !position_changed && !baseline_changed) 6103:goto out; That prevents the size_allocate to be propagated to clutter-gtk's gtk_clutter_embed_size_allocate() which reposition the sub-surface where it should be. Removing this test fixes the issue, but it's still not an /acceptable/ fix. -- 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 771915] [Wayland]: Totem window misplaced after a state change
https://bugzilla.gnome.org/show_bug.cgi?id=771915 --- Comment #8 from Olivier Fourdan --- (In reply to Bjørn Lie from comment #7) > Sure, but with my current "patch" set (I noticed that I have a couple of > mutter patches in plus), I can not reproduce bug 771561 anymore. Not even with attachment 335854 ? If so, can you list your current patch set applied? -- 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 771915] [Wayland]: Totem window misplaced after a state change
https://bugzilla.gnome.org/show_bug.cgi?id=771915 --- Comment #7 from Bjørn Lie --- (In reply to Olivier Fourdan from comment #6) > Comment on attachment 336192 [details] [review] > [PATCH] gtkwindow: Update on state event only for unrealized > > Just to make it clear, this patch is a no-go, as it's in effect a revert of > the fix for bug 771561 which is a (more) serious issue. > > The goal here is to fix this issue without reintroducing bug 771561 again. Sure, but with my current "patch" set (I noticed that I have a couple of mutter patches in plus), I can not reproduce bug 771561 anymore. -- 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 771915] [Wayland]: Totem window misplaced after a state change
https://bugzilla.gnome.org/show_bug.cgi?id=771915 Olivier Fourdan changed: What|Removed |Added Attachment #336192|needs-work |rejected status|| --- Comment #6 from Olivier Fourdan --- Comment on attachment 336192 --> https://bugzilla.gnome.org/attachment.cgi?id=336192 [PATCH] gtkwindow: Update on state event only for unrealized Just to make it clear, this patch is a no-go, as it's in effect a revert of the fix for bug 771561 which is a (more) serious issue. The goal here is to fix this issue without reintroducing bug 771561 again. -- 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 771915] [Wayland]: Totem window misplaced after a state change
https://bugzilla.gnome.org/show_bug.cgi?id=771915 --- Comment #5 from Olivier Fourdan --- (In reply to Bjørn Lie from comment #4) > See https://bugzilla.gnome.org/show_bug.cgi?id=771553#c10 No, not here, attachment 336250 from bug 771553 does not help afaics, this is not actually an issue with fullscreen, but with maximize and attachment 336250 wouldn't help here. I suspect this bug here is caused by the correct shadow border being applied sooner (required to set the correct min/max size, see bug 771561), which sets the right container size sooner and somehow shortcuts the update of abs_x/abs_y in recompute_visible_regions_internal(), or something along these lines... -- 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 771553] Shrinking window generates a black patch when gl is used
https://bugzilla.gnome.org/show_bug.cgi?id=771553 Olivier Fourdan changed: What|Removed |Added CC||ofour...@redhat.com --- Comment #11 from Olivier Fourdan --- (In reply to Bjørn Lie from comment #10) > I can add that when built combined with the patch from bug 771915 -> totem > fullscreen is fine too Nope, not here, and I fail to see how attachment 336250 could help with bug 771915 -- 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 771915] [Wayland]: Totem window misplaced after a state change
https://bugzilla.gnome.org/show_bug.cgi?id=771915 --- Comment #4 from Bjørn Lie --- (In reply to Olivier Fourdan from comment #3) > Oops, this patch reintroduces bug 771561 that commit 4cb1b96 fixed, so no > go... See https://bugzilla.gnome.org/show_bug.cgi?id=771553#c10 -- 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 97919] [weston-terminal] xterm mouse tracking protocol
https://bugs.freedesktop.org/show_bug.cgi?id=97919 Pekka Paalanen changed: What|Removed |Added Severity|normal |enhancement Priority|medium |low --- Comment #1 from Pekka Paalanen --- This is a request for an enhancement. weston-terminal has been on kind of maintenance mode without new development. It's the fallback terminal for cases when everything else fails or nothing else is available. I'm not sure how much sense it makes to make it featureful, I hope there would be better alternatives for development. -- 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 771553] Shrinking window generates a black patch when gl is used
https://bugzilla.gnome.org/show_bug.cgi?id=771553 --- Comment #10 from Bjørn Lie --- (In reply to Bjørn Lie from comment #9) > (In reply to Gustavo Noronha (kov) from comment #6) > > Created attachment 336250 [details] [review] [review] > > wayland: always sync state after a frame is painted > > > > It is indeed the sync_opaque_region call that fixes it. Moving the sync > > calls worked for me. =) > > This works for me too +1 for this patch! I can add that when built combined with the patch from bug 771915 -> totem fullscreen is fine 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 771553] Shrinking window generates a black patch when gl is used
https://bugzilla.gnome.org/show_bug.cgi?id=771553 --- Comment #9 from Bjørn Lie --- (In reply to Gustavo Noronha (kov) from comment #6) > Created attachment 336250 [details] [review] > wayland: always sync state after a frame is painted > > It is indeed the sync_opaque_region call that fixes it. Moving the sync > calls worked for me. =) This works for me too +1 for this 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 771553] Shrinking window generates a black patch when gl is used
https://bugzilla.gnome.org/show_bug.cgi?id=771553 --- Comment #8 from Bjørn Lie --- (In reply to Gustavo Noronha (kov) from comment #7) > (In reply to Bjørn Lie from comment #4) > > Created attachment 336105 [details] > > "boken" overview (hidpi) > > > > Sure I still got it :-) > > How do you reproduce that? Do you just start yelp or do you resize it > somehow to get that result? Have webkitgtk 2.14.0 installed. Start yelp, epiphany or evolution (any webkitgtk based app). Resize the app, get black areas (when making smaller) or get areas not "sensitive" when making bigger. -- 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 771553] Shrinking window generates a black patch when gl is used
https://bugzilla.gnome.org/show_bug.cgi?id=771553 --- Comment #7 from Gustavo Noronha (kov) --- (In reply to Bjørn Lie from comment #4) > Created attachment 336105 [details] > "boken" overview (hidpi) > > Sure I still got it :-) How do you reproduce that? Do you just start yelp or do you resize it somehow to get that result? -- 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 771553] Shrinking window generates a black patch when gl is used
https://bugzilla.gnome.org/show_bug.cgi?id=771553 --- Comment #6 from Gustavo Noronha (kov) --- Created attachment 336250 --> https://bugzilla.gnome.org/attachment.cgi?id=336250&action=edit wayland: always sync state after a frame is painted It is indeed the sync_opaque_region call that fixes it. Moving the sync calls worked for 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
