=== meetingology` is now known as meetingology
=== davidcalle_ is now known as davidcalle
=== tedg_ is now known as tedg
=== floccula1t is now known as flocculant
=== jlnr_ is now known as jlnr
[05:30] <flocculant> jbicha: we likely to see an update to gvfs before release? bug 1739537
[05:30] <ubot5`> bug 1739537 in gvfs (Ubuntu) "mtp volume is not removed when unplugging" [Undecided,New] https://launchpad.net/bugs/1739537
[08:18] <seb128> good morning desktopers
[08:27] <duflu> Morning seb128
[08:29] <seb128> hey duflu, how are you?
[08:36] <duflu> seb128, I was hungry so snacked. Fine now :) You?
[08:36] <seb128> I'm good :)
[08:37] <dupondje> Hi guys. Small question, what could be the cause that gnome-terminal laggs my whole pc when there is fast output in it (like when I tail -f some logfile)
[08:39] <dupondje> gnome-terminal goes to like 60% cpu :s
[08:49] <duflu> dupondje, that sounds familiar but I can't fine the Ubuntu bug reports. You would have more luck looking upstream closer to the source: https://bugzilla.gnome.org/buglist.cgi?quicksearch=gnome%20terminal%20performance
[08:49] <duflu> I also can't *find* them
[08:56] <duflu> dupondje, maybe https://bugzilla.gnome.org/show_bug.cgi?id=778926
[08:56] <ubot5> Gnome bug 778926 in Backend: Wayland "[gnome-terminal] Very poor scrolling performance on wayland with high DPI" [Normal,New]
[08:57] <duflu> One surprising side-effect of using Wayland instead of X11 is that there is now no 2D acceleration where previously there was in Xorg. So some simple things like clearing a rectangle to a colour or scrolling could be much more CPU intensive with Wayland
[08:58] <duflu> So I discovered when working on GTK performance issues in 17.10
[08:59] <dupondje> That seems the be the issue indeed :) Cause its since I'm using a new laptop with HiDPi
[08:59] <dupondje> 2D acceleration still needs to be added or ?
[09:01] <duflu> dupondje, OK then two separate issues. (1) Please subscribe to that bug. (2) I don't think 2D acceleration is planned at all, AFAIK. Devs would probably prefer instead that more people used OpenGL instead of software blitting. Fortunately GTK4 does exactly that, compared to GTK3
[09:02] <duflu> And Qt already does. So only GTK3 is a problem really
[09:02] <duflu> Only GTK3 on Wayland is a problem really
[09:04] <duflu> dupondje, solving the problem you describe is one of the main goals of GTK4, as far as I have heard
[09:05] <dupondje> but gtk4 is for 20xx? :D
[09:05] <duflu> Yes, probably this century
[09:06]  * duflu has no idea on the timeline for that
[09:06] <dupondje> so until then we have to live with gnome-terminal eating 60% cpu? :D
[09:07] <duflu> dupondje, if you scroll fast enough then yes. You have to keep in mind the computer will and must display each frame accurately. So if you scroll really fast it's like asking the machine to play a 3D game with software rendering
[09:11] <duflu> That's what GPUs are *mostly* for. To avoid that bottleneck and push hundreds of millions of unique pixels to the screen each second, more efficiently than a CPU can
[09:18] <duflu> Then there is the argument that it's not really an important bug. If your terminal is scrolling so fast that it uses significant CPU then it's already too fast to read, and not useful. Maybe redirect your output so it doesn't scroll
[09:22] <dupondje> well partly agree :) thing is, it worked fine, and now (on wayland) its broken, which is not cool ofcourse
[09:30] <duflu> dupondje, yeah I experienced similar when testing window (actually just decorations) redraw performance. It was much faster with X11 vs Wayland
[09:30] <duflu> But that's somewhat intentional. No fast path exists for GTK3 on Wayland yet
[09:35] <dupondje> in fact its better to stay on X11 then :)
[09:35] <dupondje> in this stage
[09:38] <duflu> dupondje, there are benefits and drawbacks. It's also possible gnome-terminal just contains some bug that is fixable without needing GTK4 acceleration
[09:39] <duflu> But in general you can't animate in software a largish window like a terminal that is scrolling without using noticeable CPU
=== bluesabre_ is now known as bluesabre
[12:08] <LyzardKing_> willcooke: Hi! I'm the maintainer for ubuntu-make. I just updated the wiki.ubuntu.com page to reflect the recent changes (snap, ppa, and other details.). At the moment the updated ppa is on my personal launchapd account. Is the ubuntu team interested in keeping instead the ubuntu-desktop ppa (aka the old one...)?
=== Dmitrii-Sh is now known as Dmitrii-Sh-PTO
[12:40] <jbicha> flocculant: do you mean for bionic or for artful? (gvfs)
[12:56] <alexarnaud> jbicha: Hello, do you plan to package BRLTTY 5.5 for Ubuntu 18.04 ? Do I have to fill a bug for that ? It's braille display driver for GNU/Linux.
[12:59] <jbicha> alexarnaud: I'm not working on brltty now
[13:02] <alexarnaud> I know but who is in charge of this package ? Do you plan to migrate the BRLTTY package from main to community to use the Debian package ?
[13:04] <alexarnaud> The new BRLTTY release 5.5 comes in April 2017 and Ubuntu BRLTTY package stays on 5.4.
[13:04] <jbicha> no, brltty needs to stay in main
[13:05] <jbicha> lots of people are on holiday now
[13:06] <jbicha> maybe ask in #ubuntu-devel in January, maybe you can find someone from the Foundations Team to work on doing the merge (updating the package)
[13:07] <jbicha> you can file a bug if you like. If you do, add the tags upgrade-software-version and needs-debian-merge
[13:08] <alexarnaud> OK :), to be honest I don't exactly why BRLTTY needs to be in main. But you're more experienced than me. I just want to inform you about the current situation of BRLTTY on Ubuntu. As I've to help blind people to use Ubuntu since few months I think it could better to have an up-to-date BRLTTY package on 18.04.
[13:08] <alexarnaud> Thanks, I'll do that.
[13:22] <jbicha> it needs to be in main so that it can be used in the installer
[13:54] <alexarnaud> Oh, thanks for the explanation.
[17:27] <flocculant> jbicha: bionic :p
[17:27] <jbicha> flocculant: sure, we'll package a new release eventually
[17:28] <jbicha> gvfs follows the GNOME release schedule so if we package GNOME 3.28, that's around February https://wiki.gnome.org/ThreePointTwentyseven
[17:29] <flocculant> jbicha: okey doke - thanks for the info
[17:29] <flocculant> was a bit disconcerting when I had a bunch of phones and tablets apparently :p
[17:34] <kenvandine> heber, popey just invited you to be a mentor, can you please accept it?
[17:42] <heber> kenvandine, sure let me check
[21:13] <robert_ancell> jackpot51, hello, looking at https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216
[21:13] <ubot5> Launchpad bug 1699216 in gnome-initial-setup (Ubuntu) "Encrypted home support" [Wishlist,Confirmed]
[21:23] <robert_ancell> jackpot51, I updated the bug with some feedback.
[22:02] <jackpot51> Thanks robert_ancell
[22:02] <jackpot51> I will get to work on updating it
[22:15] <robert_ancell> jackpot51, note I haven't got confirmation from the original authors that is a valid use of account type but it seems reasonable to me. The other option was a CreateUser2 method that took params arg of type "a{sv}" so we could add any other future options into it.
[22:16] <jackpot51> That makes sense
=== ochosi_ is now known as ochosi