=== maclin1 is now known as maclin
[07:18] <didrocks> good morning!
[07:31] <jibel> morning didrocks
[07:34] <didrocks> salut jibel
[07:36] <jibel> didrocks, are you feeling better?
[07:39] <didrocks> jibel: a little bit, after a night of sweating, I feel the virus is slowely exiting finally…
[07:39] <didrocks> so feeling better than yesterday, far from being in full shape though
[07:40] <didrocks> and you? All good?
[07:42] <jibel> didrocks, yes, i'm all right.
[08:00] <oSoMoN> good morning desktoppers!
[08:04] <didrocks> salut oSoMoN !
[08:08] <oSoMoN> salut didrocks
[08:14] <Nafallo> morning o/
[08:37] <seb128> lut didrocks oSoMoN jibel
[08:37] <seb128> hey Nafallo
[08:37] <seb128> good morning desktopers
[08:38] <oSoMoN> salut seb128, ça va?
[08:38] <seb128> ouais, nickel, et toi ?
[08:39] <oSoMoN> très bien
[08:39] <didrocks> salut seb128 !
[08:40] <oSoMoN> libreoffice 5.4.3 is now in bionic
[08:41] <Nafallo> seb128: heh, I didn't get the french hello. not sure if I should feel special or left out :-P
[08:49] <willcooke> morning
[08:49] <didrocks> good morning willcooke
[08:51] <seb128> oSoMoN, great!
[08:51] <seb128> hey willcooke
[08:52] <Nafallo> morning willcooke :-)
[08:53] <oSoMoN> good morning willcooke
[08:53] <willcooke> So, Nafallo wins the dentist prize!  No fillings, but I need 4 wisdom teeth out :/
[08:53] <oSoMoN> ouch
[08:54] <Nafallo> willcooke: the big question then, what did you ask them to put in instead? :-)
[08:54] <willcooke> wooden ones, it's the British way
[08:55] <Nafallo> that doesn't sounds efficient at all. would just taste like beer all the time once they've had a chance to soak it up :-P
[08:55] <willcooke> wait, that sounds awesome ;)
[08:56] <didrocks> willcooke: ok, I won't tell you tomorrow my 4 wisdom teeth story. Once it's done however, I'm happy to share :)
[08:57] <Nafallo> didrocks: you could tell beforehand what YOU replaced them with :-P
[08:58] <oSoMoN> is it a known issue that the lock screen is very laggy when there's a CPU-intensive task running (like building chromium), to the point that when revealing the login entry after starting to type my password, half (or more) of the keystrokes are lost?
[08:58] <didrocks> Nafallo: haha, I just lost wisdom on that day, no replacement :p
[08:59] <didrocks> oSoMoN: well, not known, but not surprised (it's under the same users and the Shell in general is really laggy with intensie CPU tasks
[08:59] <didrocks> intensive*
[08:59] <didrocks> missing inputs and such
[09:00] <oSoMoN> didrocks, is it worth filing a bug? IIRC the unity lock screen didn't exhibit this problem
[09:00] <didrocks> oSoMoN: please, file one upstream, on the bz tracker (gnome-shell)
[09:00] <oSoMoN> ok
[09:00] <willcooke> (I saw something about upstream tracking bugs on gitlab now - is that only for certain projects?)
[09:01] <oSoMoN> I keep having to type my password twice to unlock my screen, it's annoying
[09:01] <jamesh> oSoMoN: I see it too.  I'm not seeing lost keystrokes though: rather repeated keystrokes
[09:02] <didrocks> willcooke: yeah, only for some, transitionning slowly
[09:02] <didrocks> g-s didn't yet, but +1 on the move
[09:02] <Nafallo> would it depend on what sort of keyboard connection you use perhaps?
[09:02] <willcooke> seb128, jibel  - Bluetooth is (most probably) cancelled today as koza is in Taipei.
[09:02] <jamesh> i.e. the number of dots is more than the number of characters in my password
[09:03] <didrocks> jamesh: indeed, due to how mutter handles key inputs for repeated keys
[09:03] <didrocks> (end time - start time, which can be long on a hanging CPU)
[09:04] <oSoMoN> jamesh, I also sometimes see repeated keystrokes in gnome-terminal or gedit when under a heavy load, indeed
[09:05] <jamesh> didrocks: I read that Wayland handles key repeat in the client rather than the server, so it can happen pretty much anywhere
[09:05] <didrocks> indeed
[09:05] <oSoMoN> I initially thought it might be due to using an external USB keyboard, but I see the issue with the laptop’s builtin keyboard too
[09:08] <jamesh> https://bugzilla.gnome.org/show_bug.cgi?id=777693 seems to be the relevant bug, which also notes XWayland implementing a work around
[09:08] <ubot5> Gnome bug 777693 in general "Input event (e. g. typing on keyboard) is sent repeatedly during high load" [Normal,Needinfo]
[09:12] <oSoMoN> https://bugzilla.gnome.org/show_bug.cgi?id=790973
[09:12] <ubot5> Gnome bug 790973 in lock-screen "Unlock dialog laggy when under heavy load, drops keystrokes" [Normal,New]
[09:18] <seb128> willcooke, +1 for not doing the bluetooth one without koza & duflu
[09:40] <willcooke> bbiab, errands
[10:09] <willcooke> back
[10:42] <Nafallo> hmm. my lockscreen shortcut changed. is that a bug? :-P
[10:45] <didrocks> the default is Super + L under GNOME Shell (and so, on 17.10)
[10:46] <Nafallo> hmm. mine was set to ctrl+alt+l...
[10:46] <Nafallo> *shrugs* let's ignore it then :-P
[10:47] <Nafallo> now I'm not sure how I locked it on 17.04 anymore :-P
[10:56] <seb128> it's a known issue
[10:56] <seb128> we should support the old one since quite some users have trained muscle memory on that combo for over a decade
[10:57] <seb128> it's easy to change in the settings but annoying and can be seen a security issue since some people are likely to ctrl-alt-l -> walk away from the laptop and have it unlocked
[11:10] <oSoMoN> yeah, that happened to me quite a few times when I upgraded to artful during the development cycle, and I had to re-train muscle memory to use Super+L
[11:12] <Nafallo> ooooh
[11:12] <Nafallo> both super+l and ctrl+alt+l works on 16.04 :-P
[11:13] <Nafallo> and it's set to ctrl+alt+l in settings
[11:13] <Nafallo> is this some kind of unity thing? :-)
[11:13] <didrocks> yeah, it was an array, upstream GNOME has a single key which may do the distro-patch hard to maintain
[11:14] <didrocks> this is why we let default upstream for 17.10 and wait to revisit that for 18.04, but seems we'll add a second key
[11:14] <Nafallo> well, if we don't want users leaving their computers unlocked in open space offices... ;-)
[11:14] <Nafallo> thankfully I got hit by it in my home office when getting another coffee :-P
[13:39] <frechdachs69> Q: how do I select which desktop to use (e.g. 'kubuntu-desktop') within a preseed file?
[13:41] <andyrock> how can I generate a quilt patch with "diff --git ..." lines
[13:45] <didrocks> andyrock: hum, if you committed, git format-patch is compatible
[13:48] <andyrock> didrocks: I'm generating a debdiff
[13:49] <andyrock> and the debdiff is dirty because it removes all the "diff --git google-..." lines
[13:49] <didrocks> ah, you want to do the other way around, hum
[13:50] <didrocks> I'm generally doing the other way, editing on the git, and then backporting as a quilt patch
[13:51] <didrocks> you have a --diffstat, but this isn't what you want I guess
[13:55] <andyrock> well I'll proposed the debdiff as it is :D
[13:56] <Trevinho> morning
[13:57] <didrocks> morning Trevinho!
[13:57] <Trevinho> hi didrocks, ca va?
[13:57] <didrocks> Trevinho: still a little bit sick, but starting to get better, and you?
[13:57] <Trevinho> I'm good, I took almost a week to recover :o
[14:27] <jbicha> didrocks: I'm doing some work on LP: #1585903 and I'm wondering your opinion of how we should handle light-themes
[14:27] <ubot5> Launchpad bug 1585903 in Ubuntu GNOME "Make it possible to remove gtk2" [Wishlist,Triaged] https://launchpad.net/bugs/1585903
[14:28] <jbicha> how likely is it that the 18.04 theme will be shipped in light-themes? will there be a separate Ambiance theme in a separate binary package for users to install?
[14:30] <jbicha> (the problem is that gtk2 themes depend on libgtk2.0-0)
[14:30] <didrocks> jbicha: answered! I guess splitting is fine
[14:30] <didrocks> we will have Ambiance by default, need just to have the gtk2 Ambiance variant installed by default
[14:30] <didrocks> we can relax the dep if needed manually
[14:31] <didrocks> (as we did in the past for sni-qt to not dep on Qt)
[14:31] <jbicha> so currently, you expect the 18.04 theme to still be named Ambiance?
[14:31] <didrocks> jbicha: good chance, making a new theme isn't straightfoward and we should plan for the worst case :)
[14:32] <jbicha> I think this is a great usecase for conditional dependencies: if gtk2 and Numix is installed, then install numix-gtk2 for instance
[14:32] <didrocks> well, we don't have that in apt
[14:33] <didrocks> so, the way we dealt with this in the past is this ^ hacking the ${Depends}
[14:33] <didrocks> the first app which will need it will dep on GTK2, and so, will pull the dep
[14:35] <jbicha> right, that's basically my strategy for the default install. Once gtk2 is no longer installed by default, I guess it can recommend all the popular gtk2 themes :|
[14:36] <didrocks> well, we still want the default experience to be fine for people installing it
[14:36] <didrocks> like people pulling any app that is dep on GTK2
[14:36] <didrocks> that's why we still want Ambiance to be installed by default
[14:37] <didrocks> (GTK2 & GTK3 versions)
[14:37] <didrocks> however, relaxing the deps is fine IMHO
[14:37] <didrocks> so that it doesn't pull gtk2
[14:37] <jbicha> my plan was to have libgtk2.0-0 Recommend light-themes-gtk2 (it can't be a Depends unless we don't care about the circular dependency problem)
[14:38] <didrocks> but still having light-themes-gtk2 seeded, correct?
[14:38] <jbicha> not explicitly no
[14:38] <didrocks> hum, this isn't what I just explained on how we do it :/
[14:38] <didrocks> there is no reason for libgtk2.0-0 to recommend a particular theme
[14:39] <jbicha> Ubuntu's libgtk2.0-0 arguably should recommend Ubuntu's gtk2 theme as long as we don't have a conditional dependency feature
[14:40] <jbicha> as of yesterday, Debian unstable's gtk2 recommends Adwaita for instance
[14:41] <didrocks> sounds weird
[14:41] <didrocks> but still, my advise is to do the same way we handled optional modules and features:
[14:41] <didrocks> advice*
[14:42] <didrocks> - have light-themes-gtk2 seeded by default
[14:42] <didrocks> - relax (in debian/rules, hack the generated shlib dep) the dep between light-themes-gtk2 to libgtk2 to not be listed
[14:42] <didrocks> That way, people will have the theme available, and the first application needed GTK2 will fullfil the necessary dep
[14:43] <jbicha> oh, ugh
[14:44] <jbicha> that sounds a bit horrible but it might work
[14:44] <didrocks> it does
[14:44] <jbicha> I mean I guess my proposal is a bit horrible too!
[14:44] <didrocks> that's how we handled for a long time having Qt modules with ubuntu's behavior without pulling Qt
[14:44] <didrocks> yeah, at least, we don't pull our theme for other derivatives
[14:44] <didrocks> contrary to having a recommends
[14:45] <didrocks> which will impact all flavors
[14:47] <jbicha> I guess it might not even be worth splitting light-themes if we can do the shlibs hack
[14:47] <didrocks> not mandatory, still an option if you want
[14:48] <didrocks> I don't have strong opinions
[14:48] <didrocks> jbicha: just override dh_shlibdeps with -X
[15:36] <oSoMoN> didrocks, do you mind if I merge https://github.com/ubuntu/snapcraft-desktop-helpers/pull/87 ?
[15:36] <oSoMoN> or do you want to review it too?
[15:37] <kenvandine> oSoMoN, i was about hit merge that :)
[15:37] <oSoMoN> kenvandine, then please go ahead!
[15:38] <kenvandine> oSoMoN, can you give PR 86 a test?
[15:38] <kenvandine> it works great with the platform snap
[15:39] <oSoMoN> checking
[15:39] <didrocks> oSoMoN: yeah, kenvandine is maintaining it more than I do now :)
[15:39] <kenvandine> oSoMoN, thx
[15:40] <oSoMoN> I pinged didrocks out of habit…
[15:41] <didrocks> :)
[16:08] <oSoMoN> kenvandine, what generates the mime.cache file in the gnome platform snap?
[16:13] <kenvandine> oSoMoN, http://bazaar.launchpad.net/~ubuntu-desktop/+junk/gnome-3-26-1604/view/head:/snapcraft.yaml#L85
[16:14] <oSoMoN> ok, so I could do something similar in the libreoffice snap
[16:14] <oSoMoN> PR #86 seems to work well, +1 from me
[16:18] <oSoMoN> kenvandine, feel free to merge
[16:20]  * oSoMoN → chiropractor
[16:21] <kenvandine> oSoMoN, thx
[17:23]  * kenvandine triggers rebuilds of all the gnome snaps to pickup the new helpers
[17:52] <cyphermox> willcooke: around?
[17:52] <willcooke> cyphermox, otp, but can reply async
[17:52] <cyphermox> ack
[18:23] <willcooke> night all.  London tomorrow so won't be around first thing probably.
[20:29] <robert_ancell> kenvandine: hi!
[20:29] <kenvandine> hey robert_ancell