[Wayland-bugs] [Bug 782694] Copy and paste when on wayland not working well
https://bugzilla.gnome.org/show_bug.cgi?id=782694 --- Comment #23 from Daniel Rowe --- I am also still seeing this bug and it make gedit not usable really on wayland. Feb 03 11:10:27 vulcan.fathom13.com gedit[7043]: Error writing selection data: Error writing to file descriptor: Broken pipe Feb 03 11:10:33 vulcan.fathom13.com gedit[7043]: Error writing selection data: Error writing to file descriptor: Broken pipe Feb 03 11:10:34 vulcan.fathom13.com gnome-terminal-[2427]: gdkselection-wayland.c:267: error reading selection buffer: Operation was cancelled Feb 03 11:10:35 vulcan.fathom13.com gedit[7043]: Error writing selection data: Error writing to file descriptor: Broken pipe Its a basic function and its broken. -- 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 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI
https://bugzilla.gnome.org/show_bug.cgi?id=778926 --- Comment #23 from Egmont Koblinger --- (In reply to François Guerraz from comment #22) > Looking back on it, I do not think it's a very scientific comparison [...] Anything along the lines of 30%+ CPU usage for scrolling every tenth of a second is obviously pretty bad, no need for more accurate CPU measurement 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 793062] [Wayland] Crash under gdk_wayland_window_attach_image()
https://bugzilla.gnome.org/show_bug.cgi?id=793062
--- Comment #10 from Olivier Fourdan ---
“old_state = GDK_WINDOW_STATE_FOCUSED, state = (GDK_WINDOW_STATE_WITHDRAWN |
GDK_WINDOW_STATE_FOCUSED)” seems weird, how can a window be withdrawn and
focused?
Another weird thing is:
display_server = {outputs = 0x0, wl_surface = 0x0, xdg_surface = 0x0,
xdg_toplevel = 0x0, xdg_popup = 0x0, gtk_surface = 0x0, wl_subsurface = 0x0,
egl_window = 0x0, dummy_egl_window = 0x0, xdg_exported = 0x0, server_decoration
= 0x0}, egl_surface = 0x0, dummy_egl_surface = 0x0, initial_configure_received
= 0, mapped = 0, use_custom_surface = 0, pending_buffer_attached = 0,
pending_commit = 0, awaiting_frame = 0
All values are 0, as if the surface was withdrawn.
Also hint = GDK_WINDOW_TYPE_HINT_UTILITY,
This comes from Firefox code:
3517 nsresult
3518 nsWindow::Create(nsIWidget* aParent,
3519 nsNativeWidget aNativeParent,
3520 const LayoutDeviceIntRect& aRect,
3521 nsWidgetInitData* aInitData)
3522 {
...
3690 switch (aInitData->mPopupHint) {
3691 case ePopupTypeMenu:
3692 // Use GDK_WINDOW_TYPE_HINT_UTILITY on Wayland
which
3693 // guides Gtk to create the popup as subsurface
3694 // instead of xdg_shell popup (see Bug 1423598).
3695 gtkTypeHint = mIsX11Display ?
GDK_WINDOW_TYPE_HINT_POPUP_MENU :
3696
GDK_WINDOW_TYPE_HINT_UTILITY;
So the window causing this issue would be a “ePopupTypeMenu”.
--
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 793062] [Wayland] Crash under gdk_wayland_window_attach_image()
https://bugzilla.gnome.org/show_bug.cgi?id=793062 --- Comment #9 from Ray Strode [halfline] --- that's a weird combo: state = (GDK_WINDOW_STATE_WITHDRAWN | GDK_WINDOW_STATE_FOCUSED) -- 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 793062] [Wayland] Crash under gdk_wayland_window_attach_image()
https://bugzilla.gnome.org/show_bug.cgi?id=793062
--- Comment #8 from Olivier Fourdan ---
OK, I managed to reproduce a couple of times (every time that occured while
switching back to the FF window, when it changes from “unfocused” to “focused”
state) and take a closer look at hte GdkWindow being “end-painted”:
gdb) p *window
$1 = {parent_instance = {g_type_instance = {g_class = 0x76a6b6b0},
ref_count = 10, qdata = 0x7fffb60d3580},
impl = 0x7fffb6f09400 [GdkWindowImplWayland], parent = 0x76abf050
[GdkWaylandWindow], transient_for = 0x7fffcf0f1250 [GdkWaylandWindow],
visual = 0x76abd180 [GdkWaylandVisual], user_data = 0x7fffb6f09260, x =
238, y = 101, event_mask = 6553366, window_type = 3 '\003',
depth = 32 ' ', resize_count = 0 '\000', toplevel_window_type = -1 '\377',
filters = 0x0, children = 0x7fffb799c630 = {0x7fffb799c5d0},
children_list_node = {data=0x7fffb799c440, next=0x7fffac145310,
prev=0x7fffb799c950}, native_children = 0x0, background = 0x7fffabe11060,
current_paint = {surface = 0x7fffacdf2b00, region = 0x7fffb610fd00,
flushed_region = 0x7fffb63702e0, need_blend_region = 0x7fffb6370300,
surface_needs_composite = 0, use_gl = 0}, gl_paint_context = 0x0,
update_area = 0x0, update_freeze_count = 0,
active_update_area = 0x7fffb610f0e0, old_updated_area = {0x0, 0x0}, old_state
= GDK_WINDOW_STATE_FOCUSED,
state = (GDK_WINDOW_STATE_WITHDRAWN | GDK_WINDOW_STATE_FOCUSED), alpha = 255
'\377', fullscreen_mode = 0 '\000', input_only = 0,
pass_through = 0, modal_hint = 0, composited = 0, has_alpha_background = 0,
destroyed = 0, accept_focus = 1, focus_on_map = 1, shaped = 0,
support_multidevice = 0, synthesize_crossing_event_queued = 1,
effective_visibility = 3, visibility = 2, native_visibility = 0, viewable = 0,
applied_shape = 0, in_update = 1, geometry_dirty = 1, event_compression = 1,
frame_clock_events_paused = 0,
impl_window = 0x7fffb799c440 [GdkWaylandWindow],
update_and_descendants_freeze_count = 0, abs_x = 0, abs_y = 0, width = 314,
height = 200,
shadow_top = 0, shadow_left = 0, shadow_right = 0, shadow_bottom = 0,
num_offscreen_children = 0, clip_region = 0x7fffb6370720, cursor = 0x0,
device_cursor = 0x7fffabe249a0, shape = 0x0, input_shape = 0x0,
devices_inside = 0x0, device_events = 0x0, source_event_masks = 0x0,
device_added_handler_id = 0, device_changed_handler_id = 0, frame_clock =
0x7fffabad3cb0 [GdkFrameClockIdle], invalidate_handler = 0x0,
drawing_context = 0x7fffb84358e0 [GdkDrawingContext], opaque_region = 0x0}
(gdb) p (GdkWindowImplWayland) *window->impl
$2 = {parent_instance = {parent = {g_type_instance = {g_class =
0x76a19c00}, ref_count = 3, qdata = 0x0}},
wrapper = 0x7fffb799c440 [GdkWaylandWindow], display_server = {outputs = 0x0,
wl_surface = 0x0, xdg_surface = 0x0, xdg_toplevel = 0x0,
xdg_popup = 0x0, gtk_surface = 0x0, wl_subsurface = 0x0, egl_window = 0x0,
dummy_egl_window = 0x0, xdg_exported = 0x0,
server_decoration = 0x0}, egl_surface = 0x0, dummy_egl_surface = 0x0,
initial_configure_received = 0, mapped = 0, use_custom_surface = 0,
pending_buffer_attached = 0, pending_commit = 0, awaiting_frame = 0, hint =
GDK_WINDOW_TYPE_HINT_UTILITY,
transient_for = 0x7fffcf0f1250 [GdkWaylandWindow], popup_parent = 0x0,
position_method = POSITION_METHOD_MOVE_RESIZE,
staging_cairo_surface = 0x7fffacdf2b00, committed_cairo_surface = 0x0,
backfill_cairo_surface = 0x0, pending_buffer_offset_x = 0,
pending_buffer_offset_y = 0, title = 0x7fffabf4c4b0 "Firefox", application =
{was_set = 0, application_id = 0x0, app_menu_path = 0x0,
menubar_path = 0x0, window_object_path = 0x0, application_object_path =
0x0, unique_bus_name = 0x0}, geometry_hints = {min_width = 1,
min_height = 2, max_width = 32767, max_height = 32767, base_width = 1,
base_height = 2, width_inc = 13, height_inc = 0,
min_aspect = 6.9533024459871814e-310, max_aspect = 0, win_gravity =
GDK_GRAVITY_NORTH_WEST},
geometry_mask = (GDK_HINT_POS | GDK_HINT_MIN_SIZE | GDK_HINT_BASE_SIZE |
GDK_HINT_WIN_GRAVITY), grab_input_seat = 0x0,
pending_frame_counter = 0, scale = 1, margin_left = 0, margin_right = 0,
margin_top = 0, margin_bottom = 0, margin_dirty = 0,
initial_fullscreen_monitor = -1, opaque_region = 0x0, opaque_region_dirty =
1, input_region = 0x0, input_region_dirty = 1,
staged_updates_region = 0x0, saved_width = -1, saved_height = -1,
parent_surface_committed_handler = 0, pending_move_to_rect = {rect = {x = 0,
y = 0, width = 0, height = 0}, rect_anchor = 0, window_anchor = 0,
anchor_hints = 0, rect_anchor_dx = 0, rect_anchor_dy = 0}, pending = {
width = 0, height = 0, state = (unknown: 0)}, exported = {handle = 0x0,
export_count = 0, closures = 0x0, idle_source_id = 0},
imported_transient_for = 0x0, shortcuts_inhibitors = 0x7fffabe24a00 =
{[0x621] = 0x621}}
--
You are receiving this mail because:
You are on the CC list for the bug.___
wayland-bugs maili
[Wayland-bugs] [Bug 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI
https://bugzilla.gnome.org/show_bug.cgi?id=778926 --- Comment #22 from François Guerraz --- When I reported the bug, I was comparing performance on the same machine with HiDPI in both cases. Looking back on it, I do not think it's a very scientific comparison as "CPU usage" is a vary vague indication of actual performance on a laptop with CPU frequency scaling. It may be that it was using more % on wayland, but actually fewer or same amount of CPU cycles. -- 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 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI
https://bugzilla.gnome.org/show_bug.cgi?id=778926 --- Comment #21 from Jan Alexander Steffens (heftig) --- GNOME Shell lagging is much more noticeable on Wayland as it's also responsible for input handling and updating the mouse cursor. On X this happens independently from the compositor. -- 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 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI
https://bugzilla.gnome.org/show_bug.cgi?id=778926 --- Comment #20 from Jan Alexander Steffens (heftig) --- Performance suffers a lot with scale 2 drawing (and large window sizes), so maybe what performance you remember from X was from before we had Hi-DPI. -- 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 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI
https://bugzilla.gnome.org/show_bug.cgi?id=778926 --- Comment #19 from François Guerraz --- I don't see any major improvement with this commit but it seems to me now that vte3 performance is comparable on X11 & Wayland, but unrelated to this commit. -- 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 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI
https://bugzilla.gnome.org/show_bug.cgi?id=778926 --- Comment #18 from Egmont Koblinger --- Great to hear this! (In reply to jean-louis from comment #16) > [...] But not yet the speed we had on X. Could you please elaborate on this? How "usable" is this now, does it still lag the whole desktop (as you reported at https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1746949)? Or just simply a "bit" slower than on X? -- 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 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI
https://bugzilla.gnome.org/show_bug.cgi?id=778926 --- Comment #17 from Jan Alexander Steffens (heftig) --- Yes, there is now little difference in performance between with and without scrollbar. -- 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 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI
https://bugzilla.gnome.org/show_bug.cgi?id=778926 --- Comment #16 from jean-lo...@dupond.be --- Just tested that commit (0.50.2-4ubuntu2 + that patch) on Ubuntu artful, and it seems to make ALOT of difference already. Its way faster now. But not yet the speed we had on X. -- 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 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI
https://bugzilla.gnome.org/show_bug.cgi?id=778926 Egmont Koblinger changed: What|Removed |Added CC||egm...@gmail.com --- Comment #15 from Egmont Koblinger --- Could you guys please check whether, by any chance, this recent VTE commit: https://git.gnome.org/browse/vte/commit/?id=809e79770 [bug 771899] causes any noticeable performance improvement? -- 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 793062] [Wayland] Crash under gdk_wayland_window_attach_image()
https://bugzilla.gnome.org/show_bug.cgi?id=793062 --- Comment #5 from Olivier Fourdan --- (In reply to Martin Stransky from comment #4) > You can use this package to do the testing: > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1022923 > > it runs natively under Wayland. Yeah, but it's hardly usable to be honest. I'm not even sure how to reproduce with it. -- 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 793062] [Wayland] Crash under gdk_wayland_window_attach_image()
https://bugzilla.gnome.org/show_bug.cgi?id=793062 --- Comment #6 from Martin Stransky --- (In reply to Olivier Fourdan from comment #5) > (In reply to Martin Stransky from comment #4) > > You can use this package to do the testing: > > > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1022923 > > > > it runs natively under Wayland. > > Yeah, but it's hardly usable to be honest. I'm not even sure how to > reproduce with it. :) well only issue I'm aware of is missing clipboard selection (mouse middle button paste). If you see crashes it may be caused by this bug - you need to enable ABRT to catch the crashes probably or run the browser under gdb. Or is there anything else? -- 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 793062] [Wayland] Crash under gdk_wayland_window_attach_image()
https://bugzilla.gnome.org/show_bug.cgi?id=793062 --- Comment #7 from Olivier Fourdan --- Nope, no crash (yet), but it's hardly usable for me because all menus are truncated, missing most of the entries. Seems like restarting FF has fixed it now... weird. -- 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
