[Wayland-bugs] [Bug 782694] Copy and paste when on wayland not working well

2018-02-02 Thread gtk+
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

[Wayland-bugs] [Bug 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI

2018-02-02 Thread gtk+
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 seco

[Wayland-bugs] [Bug 793062] [Wayland] Crash under gdk_wayland_window_attach_image()

2018-02-02 Thread gtk+
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 = {ou

[Wayland-bugs] [Bug 793062] [Wayland] Crash under gdk_wayland_window_attach_image()

2018-02-02 Thread gtk+
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] [Bug 793062] [Wayland] Crash under gdk_wayland_window_attach_image()

2018-02-02 Thread gtk+
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 bein

[Wayland-bugs] [Bug 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI

2018-02-02 Thread gtk+
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 indic

[Wayland-bugs] [Bug 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI

2018-02-02 Thread gtk+
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. -- Y

[Wayland-bugs] [Bug 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI

2018-02-02 Thread gtk+
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 becaus

[Wayland-bugs] [Bug 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI

2018-02-02 Thread gtk+
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 a

[Wayland-bugs] [Bug 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI

2018-02-02 Thread gtk+
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

[Wayland-bugs] [Bug 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI

2018-02-02 Thread gtk+
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] [Bug 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI

2018-02-02 Thread gtk+
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 th

[Wayland-bugs] [Bug 778926] [gnome-terminal] Very poor scrolling performance on wayland with high DPI

2018-02-02 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=778926 Egmont Koblinger changed: What|Removed |Added CC||egm...@gmail.com --- Comment #15 from

[Wayland-bugs] [Bug 793062] [Wayland] Crash under gdk_wayland_window_attach_image()

2018-02-02 Thread gtk+
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

[Wayland-bugs] [Bug 793062] [Wayland] Crash under gdk_wayland_window_attach_image()

2018-02-02 Thread gtk+
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=10

[Wayland-bugs] [Bug 793062] [Wayland] Crash under gdk_wayland_window_attach_image()

2018-02-02 Thread gtk+
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