[05:53] <Trevinho> duflu: thanks for that bug :)
[06:32] <duflu> Trevinho, you're welcome. Although it reminded me how unsure about upstream's fix I am
[06:37] <didrocks> good morning
[06:41] <duflu> Morning didrocks
[06:45] <didrocks> hey duflu
[07:19] <seb128> hey Trevinho duflu didrocks
[07:19] <duflu> Hi seb128
[07:19] <Trevinho> morning seb128
[07:19] <Trevinho> and didrocks
[07:19] <didrocks> hey Trevinho, seb128 :)
[07:26] <dupondje> I quite recently (since the libinput upgrade?) see the following bug: When I type, it sometimes gives a short hang, and then the char i'm typing is repeated like 5-15 times
[07:31] <seb128> do you use wayland?
[07:32] <dupondje> yes
[07:32] <seb128> don't :p
[07:33] <seb128> https://bugzilla.gnome.org/show_bug.cgi?id=777693
[07:33] <ubot5`> Gnome bug 777693 in general "Input event (e. g. typing on keyboard) is sent repeatedly during high load" [Normal,Needinfo]
[07:33] <ubot5-ng> bugzilla.gnome.org bug 777693 in general "Input event (e. g. typing on keyboard) is sent repeatedly during high load" [Normal, Needinfo] - Assigned to gnome-shell-maint
[07:33] <ubot5`> bug 777693 in PernillaSYS "Crash-bug when trying to view registrations if none of the users conferences is locked" [Medium,Fix released] https://launchpad.net/bugs/777693
[07:34] <didrocks> seb128: so, ubiquity on 16.04 a11y support is even worse: it's in english both in the installer and in the live session
[07:34] <didrocks> here, we would have it in english only the installer mode, not in the live session
[07:37] <Trevinho> and... night time here, bye
[07:37] <didrocks> bye bye Trevinho
[07:38] <seb128> night Trevinho
[07:38] <seb128> didrocks, Laney managed to make the callback work yesterday
[07:38] <didrocks> oh?
[07:38]  * didrocks bzr pull
[07:38] <Trevinho> seb128: got the mail?
[07:38] <didrocks> hum, not in bzr
[07:38]  * didrocks looks at logs
[07:38] <seb128> Trevinho, yes, you forgot the status of your milestoned bugs again :p
[07:39] <seb128> didrocks, workaround, not fix
[07:39] <Trevinho> seb128: I didn't forget... there's no news :-D
[07:39] <seb128> didrocks, https://irclogs.ubuntu.com/2018/04/23/%23ubuntu-desktop.html#t19:35
[07:39] <didrocks> better than the subprocess I guess?
[07:39] <didrocks> thx!
[07:39] <duflu> Night Trevinho
[07:39] <seb128> Trevinho, we are supposed to include those anyway, even if you say "no news, planned for SRU"
[07:40] <dupondje> seb128: hehe :) Xorg doesn't allow scaling 1 screen, but not the other I guess? :) So thats why I need wayland
[07:41] <seb128> unsure about that, it might be the case
[07:41] <Nafallo> morning
[07:41] <seb128> hey Nafallo
[07:41] <seb128> didrocks, so yeah, at least that helps understanding the issue, now for how to workaround in a nice way...
[07:42] <didrocks> seb128: well, this is what we understood yesterday basically… being root and dbus rejecting sending the message
[07:42] <seb128> right, but I didn't understand why the drop privileges calls were not working
[07:43] <seb128> Trevinho, thanks! and have a good night :)
[07:43] <didrocks> seb128: because the uid stays the same
[07:43] <Trevinho> :)
[07:43] <didrocks> you keep being 0
[07:43] <didrocks> only the euid is changed
[07:43] <didrocks> when you drop priviledges without subprocessing
[07:44] <didrocks> (as ubiquity wants to gain again root privileges later on)
[07:44]  * duflu is also seeing error messages that tell me I am uid 0
[07:44] <didrocks> the whole issue is that ubiquity is one process gaining/dropping privileges as needed. And we start to get the limitation of that architecture IMHO
[07:47] <seb128> didrocks, sorry, door bell...
[07:47] <seb128> so
[07:48] <willcooke> morning all
[07:48] <seb128> didrocks, yeah, I was just puzzled at why the drop privilege is not working for dbus but it is, we just regain the privilege before the check is done in an async way
[07:48] <duflu> Hi willcooke
[07:48] <seb128> didrocks, that explains the bit I didn't understand
[07:48] <seb128> hey willcooke
[07:48] <didrocks> seb128: hem, I mentioned that yesterday to you :)
[07:49] <didrocks> hey willcooke
[07:49] <willcooke> hi duflu - was justing thinking about the mem leak patches.. I dont think we've had any problems with it.  Worst case feedback seems to be "no change", a few people have said it helps.
[07:49] <seb128> didrocks, I didn't understood properly/realize that a sleep before the restore would be enough
[07:49] <willcooke> you think we can release it?
[07:49] <duflu> willcooke, I think we already released it(?)
[07:50] <seb128> didrocks, you said that the callback was probably coming after we restored the privilege and such discarded
[07:50] <didrocks> seb128: I'm a little bit vary about a sleep… What happens if the user press Super + Alt + S later on?
[07:50] <didrocks> yeah
[07:50] <seb128> though now I'm unsure
[07:50] <didrocks> isn't what you said?
[07:50] <seb128> does the signal register needs to happen during that time
[07:50] <seb128> or does the change need to happen?
[07:50] <didrocks> ah
[07:50] <didrocks> my theory for #2
[07:50] <didrocks> not #1
[07:50] <seb128> I understand from L_aney's comment that the register was enough
[07:50] <seb128> let me test
[07:50] <duflu> willcooke, I changed the bug to in progress the other day, awaiting more fixes. But definitely an improvement already
[07:51] <didrocks> seb128: that would be better, I'm worried if it's #2, as it can happen anytime
[07:51] <seb128> right, let me see
[07:51] <didrocks> also, are we sure nothing else happens in parallel which can gain privileges?
[07:51] <didrocks> tell me if you need any help
[07:51] <Laney> sup
[07:51] <seb128> willcooke, duflu, we "failed" at blocking the gjs update in proposed so it went to bionic proper directly on thursday
[07:52] <duflu> Yeah, 5 days ago
[07:52] <duflu> All good
[07:52] <seb128> right
[07:52] <didrocks> hey Laney
[07:52] <willcooke> ah, "problem" "solved" then :)
[07:52] <willcooke> morning Laney, how's London?
[07:52] <seb128> willcooke, Lucaks probably didn't see your request on the email, but yeah, that solves a problem for us
[07:52] <duflu> willcooke, just as well because bug 1763878 was desperate for the release
[07:52] <ubot5`> bug 1763878 in gjs (Ubuntu) "[regression] Many programs crashing at exit with assert failure: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed. Called from cairo_debug_reset_static_data()" [High,Fix released] https://launchpad.net/bugs/1763878
[07:53] <Laney> hey didrocks willcooke
[07:53] <Laney> yeah it's alright
[07:53] <Laney> seems to be a nice looking coffee shop across the road now
[07:53] <Laney> will check it out later
[07:53] <willcooke> duflu,  the other one on my radar was classic snaps crashing the session in Wayland, I think that's related to the xwayland issue.  Less pressing for release.
[07:53] <willcooke> duflu, was that on your list, or should we find someone to look at it?
[07:54] <willcooke> Laney, there was talk of free coffee to Blue Fin residents, might be worth asking Stef
[07:54] <duflu> willcooke, it wasn't no. The reason is that we have many much noisier issues. Probably hundreds. I didn't mean to be rude
[07:54] <willcooke> duflu, np
[07:54] <Laney> iiiiiiiiiiiiiiiiinteresting
[07:55] <seb128> willcooke, duflu, I asked tjaalton if he could upstream/handle the xwayland one, unsure what's the status
[07:55] <duflu> Heh. Which Xwayland one, seb128?
[07:56] <tjaalton> mesa 18.0.1 was released, best to test that first
[07:56] <seb128> duflu, the one willcooke was asking about, classic snaps making xwayland segfault
[07:56] <seb128> duflu, https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1754693
[07:56] <ubot5`> Ubuntu bug 1754693 in mesa (Ubuntu) "Xwayland crashed with SIGABRT in st_renderbuffer_delete()" [High,Confirmed]
[07:56] <duflu> Oh yes. I recall he assigned it to Mesa
[07:56] <seb128> tjaalton, do you have that update in a ppa?
[07:56] <tjaalton> not yet
[07:57] <seb128> can you let us know once you do?
[07:57] <didrocks> some people didn't understand that it's a bot posting the snap: https://github.com/ubuntu/gnome-shell-communitheme/pull/122#issuecomment-383327290 :)
[07:57] <ubot5-ng> ubuntu bug (Pull request) 122 in gnome-shell-communitheme "enhance selected day" (comments: 2) [Closed]
[07:57] <seb128> I'm sure willcooke would be happy to give it a try :)
[07:57] <seb128> willcooke, right? ;)
[07:57] <didrocks> at least, people are trying the PR snap and confirming!
[07:57] <tjaalton> sure
[07:57] <seb128> thx
[07:57] <seb128> didrocks, :)
[07:58] <willcooke> the xwayland crashing classic snaps - yes indeed - will test that
[07:58] <willcooke> oh, didrocks, using communitheme, can you open gnome calculator and tell me what you see? ;)
[07:58] <willcooke> I think you'll say "nothing at all"
[07:58] <seb128> willcooke, transparent bg?
[07:58] <willcooke> yeah
[07:58] <willcooke> darn, I thought I'd found something new
[07:58] <seb128> bug #1760818
[07:58] <ubot5`> bug 1760818 in ubuntu-themes (Ubuntu) "gedit and gnome-calculator transparency/graphics corruption issue" [Undecided,Confirmed] https://launchpad.net/bugs/1760818
[07:59] <seb128> well that one is with our current/old themes
[07:59] <seb128> but likely the same issue
[08:00] <seb128> Laney, your ubiquity changes work in -dm, no reset of keys or second dconf-service anymore
[08:01] <Laney> thx!
[08:01] <seb128> thank you for the fix!
[08:01] <didrocks> willcooke: I worked on it for some times and that was part of my weekly report :)
[08:02] <didrocks> discussed on the hub, snapcraft forum, and bug reports ;)
[08:02] <didrocks> basically, gtk-common-themes now has communitheme in as a workaround (never got an answer from the snapd team to have a proper theme support :/)
[08:02] <didrocks> and kenvandine, when he will have time, need to update the snaps to use the theme plugs
[08:03] <didrocks> but it means that any snap not declaring and supporting the theme plugs will be transparent…
[08:03] <seb128> didrocks, was that about the transparent bg?
[08:03] <didrocks> yeah
[08:03] <seb128> are you sure about that?
[08:03] <didrocks> yes
[08:03] <seb128> we have transparent bg issues with the old theme as well
[08:03] <seb128> see the bug reference I gave
[08:03] <seb128> I'm not sure it's snap specific?
[08:04] <seb128> we had reports with the deb as well (at least on the old theme)
[08:04] <seb128> there might be a snap issue on top?
[08:04] <didrocks> well, it's different
[08:04] <didrocks> here, the whole UI is transparent
[08:04] <didrocks> not part of it
[08:04] <didrocks> and switching themes make it works
[08:04] <didrocks> basically, you have apparmor denials on /snap/communitheme/current…
[08:04] <seb128> ah ok, sounds different indeed then
[08:04] <didrocks> yes
[08:05] <seb128> shame, I though it could help us to understand the issue with ambiance :p
[08:05] <didrocks> ;)
[08:05] <didrocks> I still think the "gtk-common-theme" + special plug won't address the bigger issue with themes and snaps
[08:05] <didrocks> as not all snaps will declare those plugs
[08:05] <didrocks> and thus, will render transparently :/
[08:05] <didrocks> tried to get the snapd team on it, but never got a respond…
[08:05] <seb128> yeah, if that's not handled on the snapd level it's not going to be great
[08:06] <didrocks> yeah, once kenvandine updates our default snaps, at least, those works
[08:06] <didrocks> until someone start a another snap and will trigger the bug
[08:07] <didrocks> https://forum.snapcraft.io/t/snap-application-and-snap-themes/4946/9?u=didrocks
[08:07] <didrocks> see my last comment
[08:10] <seb128> willcooke, k, well known issue in any case :)
[08:11] <didrocks> yep
[08:11] <willcooke> thx
[08:11] <willcooke> Different note, I think the u7 theme is pulling in g-calculator deb
[08:11] <willcooke> s/theme/packages
[08:12] <willcooke> session
[08:12] <didrocks> ubuntu-unity-desktop
[08:12] <didrocks> is a reverse dep
[08:12] <didrocks> so yeah
[08:12] <willcooke> yeah, that makes sense
[08:12] <didrocks> (also unity-scope-calculator)
[08:13] <didrocks> willcooke: tip of the day for you: apt rdepends gnome-calculator ;)
[08:13] <didrocks> it's nicer since the move from apt-cache to apt, shows you if it's a recommends, deps, suggests…
[08:13] <seb128> with --show-installed=yes if you want to limit to what is installed
[08:14] <seb128> which usually makes easier to understand your local install situation
[08:14] <didrocks> ah, not on apt show though…
[08:15]  * didrocks doesn't find an equivalent in the manpage…
[08:17] <c-lobrano> hi all
[08:17] <willcooke> thanks didrocks!
[08:18] <didrocks> hey c-lobrano
[08:18] <c-lobrano> didrocks: thank you for taking time to repeat again and again the same snap story every time someone asks :D
[08:19] <didrocks> c-lobrano: see, it was a combo this time, github AND here ;)
[08:19] <c-lobrano> too bad github doesn't have aliases for messages :)
[08:19] <didrocks> I was just typing the answer when I got the question on that channel :p
[08:19] <didrocks> yeah
[08:19] <didrocks> I'll make a stock response soon :p
[08:20] <didrocks> kenvandine: FYI, I can't assign it to you, but as we discussed theming in snap: https://github.com/ubuntu/gtk-communitheme/issues/354#issuecomment-383845039
[08:20] <ubot5-ng> ubuntu bug 354 in gtk-communitheme "None of the default provided snaps in 18.04 work properly with the snap community theme" (comments: 3) [Snap, Open]
[08:20] <ubot5`> Ubuntu bug 354 in gnomad2 (Ubuntu) "gnomad2 needs superuser access" [Medium,Fix released] https://launchpad.net/bugs/354
[08:20] <didrocks> at least, now, people won't mix it up with the evince issue anymore (even if both are due to the same root case: apparmor denials)
[08:20] <c-lobrano> :D
[08:27] <mvo> RAOF: hey, if you are around, I would love to chat about 1763266 (the mountinfo bug) a) does it still prevent snapd from starting with 2.32.5? b) do you see more ill effects, like snaps stop working when you try to run them?
[08:27] <mvo> RAOF: also I added some more info (and a potential kernel patch) in the bug, would love to hear if that helps
[08:29] <Laney> seb128: ummmmmmmmmmmmmmmmmmm
[08:29] <seb128> didrocks, Laney, so, back to this screen reader issue
[08:29] <seb128> lol, good timing :p
[08:29] <Laney> think we might have figured it
[08:29] <seb128> oh?
[08:29] <Laney> not sure you need to drop there ...
[08:29] <Laney> think the regain was actually causing problems
[08:29] <seb128> how so?
[08:30] <seb128> well, without the drop/restore the callback is never called either, we tried that
[08:30] <Laney> on_screen_reader_enabled_changed
[08:30] <seb128> time to rewrite ubiquity to be an user process and call to polkit to privileged actions? :p
[08:31] <Laney> that was printed
[08:31] <seb128> interested, what did you do exactly?
[08:31] <Laney>         self.a11y_settings = Gio.Settings.new("org.gnome.desktop.a11y.applications")
[08:31] <Laney>         self.a11y_settings.connect("changed::screen-reader-enabled", on_screen_reader_enabled_changed)
[08:31] <Laney>         print("current value is: %s" % self.a11y_settings.get_boolean("screen-reader-enabled"))
[08:32] <seb128> in gtk_ui.py?
[08:32] <Laney> yeah
[08:33] <seb128> I'm not sure how that's different from what I do in http://people.canonical.com/~seb128/ubiquity-screen-reader.patch
[08:33] <Laney> you do drop and regain
[08:34] <Laney> and it's not an instance variable, maybe that matters
[08:34] <seb128> in a second blob
[08:34] <seb128> +        settings_a11y1 = Gio.Settings.new("org.gnome.desktop.a11y.applications")
[08:34] <seb128> +        settings_a11y1.connect("changed", on_a11y_changed1)
[08:34] <seb128> +        print(settings_a11y1.get_boolean("screen-reader-enabled"))
[08:34] <seb128> then
[08:34] <seb128> +        misc.drop_privileges_save()
[08:34] <seb128> +        settings_a11y = Gio.Settings.new("org.gnome.desktop.a11y.applications")
[08:34] <seb128> the *1 variant is not under drop/Restore
[08:34] <Laney> ok
[08:34] <Laney> well give that a try please
[08:34] <seb128> yours?
[08:34] <seb128> sure
[08:34] <Laney> there's also a self.a11y_settings = None at the top
[08:35]  * didrocks doesn't see the difference apart from only listening to one key and not the whole schema subfolder
[08:36] <Laney> what if settings_a11y1 goes out of scope and the handlers are disconnected
[08:36] <seb128> that could well be
[08:36] <didrocks> hum, interesting idea
[08:37] <seb128> shrug, maybe lost days of poking around due something as stupîd :/
[08:37] <seb128> stupid
[08:37] <didrocks> well, it's stupid in some way, but as you have an handler, gobject-introspection python bindings should get an hold on the reference…
[08:38] <didrocks> but yeah, not a bad idea at all if this is the cause
[08:44] <RAOF> mvo: sure!
[08:45] <RAOF> That bug doesn't prevent me from using snaps *until* something tries to run `snap refresh`, at which point all snaps irreparably break.
[08:46] <RAOF> (that something might be the systemd unit that runs `snap refresh` around boot time 😀)
[08:47] <RAOF> Bug #1763266
[08:47] <ubot5`> bug 1763266 in snapd (Ubuntu) "Snapd fails to start (failed to parse /proc/self/mountinfo)" [Undecided,Incomplete] https://launchpad.net/bugs/1763266
[08:48] <tseliot> apw: hey, apparently nvidia-driver-390 is in the "libs" section rather than in "restricted/misc" (I tested this with python-apt). This causes the Additional Drivers tool to see it as "open source". Can you fix this, please?
[08:48] <apw> tseliot, looking
[08:49] <tseliot> thanks
[08:51] <apw> tseliot, restricted/libs/optional/100% it is in restricted, but as you say restricted/libs
[08:51] <mvo> RAOF: ok, so you can run snaps and interact with snapd until a refresh happens. and at that point you get an error from snapd (it stops running?) and when you "snap run test-snapd-tools.echo hello" it will fail? if so, I would love to get the error message from snap run (assuming you have test-snapd-tools installed) and the output of "journalctl -u snapd" after it starts failing. I think we need to make it more rob
[08:51] <mvo> ust :) however the underlying issue is a bcachefs bug (see LP bug)
[08:51] <tseliot> apw: I suspect that moving it to restricted/misc would solve the problem
[08:51] <apw> tseliot, is it not the restricted bit which tells us it is a dangerous thing ?
[08:52] <RAOF> mvo: sure! I'll get that info next time I trigger it, and forward that patch upstream. Thanks!
[08:53] <tseliot> apw: python-apt doesn't really return the "restricted" part from restricted/libs, but it does return the full "restricted/misc" for some reason
[08:53] <apw> tseliot, you mean because it is libs it is '' sort of thing, and restricted is lost ?
[08:54] <mvo> RAOF: thank you! woah, if you forward it, let me just fix the one tiny issue I noticed in it
[08:54] <tseliot> apw: I'll show you with a python script
[08:55] <apw> tseliot, /me trusts you ... lets try moving it
[08:55] <tseliot> apw: thanks
[08:55] <apw> tseliot, the publisher is grinding hard, so it will be a while for sure
[08:55] <RAOF> I won't do anything with it until tomorrow, so you've got like 12 hours before I touch it again 😀
[08:55] <alexarnaud> Hello all
[08:56] <tseliot> apw: that would be fine. Still less work than me changing the detection code again
[08:57] <tjaalton> seb128: pushed mesa-18.0.1 to ppa:canonical-x/x-staging, building now
[08:57] <seb128> tjaalton, nice, thanks
[08:57] <seb128> willcooke, ^
[08:57] <willcooke> installing
[08:58] <tjaalton> still building
[08:58] <tjaalton> not available yet
[08:58] <willcooke> ack, will watch it
[08:58] <tjaalton> maybe in 20min
[09:00] <didrocks> hey alexarnaud
[09:01] <seb128> didrocks, Laney, so yeah, it works with the self.a11y_settings = None definition...
[09:02] <duflu> Hmm. Is this meant to take zero time?
[09:02] <duflu> Apr 24 17:01:34 haz systemd[1]: Starting Stop ureadahead data collection...
[09:02] <duflu> Apr 24 17:01:34 haz systemd[1]: Started Stop ureadahead data collection.
[09:02] <seb128> well, I'm trying https://paste.ubuntu.com/p/ZWww3TFdNy/ but I'm having some weird issue now, the dconf/user in /run is owned by root and gsettings is unhappy, trying without the misc.py changes
[09:03] <didrocks> seb128: \o/
[09:03] <didrocks> good call Laney ;)
[09:03] <tseliot> Laney: hey, any chance you can have a look at this? It would be good to have a working Additional Drivers tool in time for the 18.04 release: https://code.launchpad.net/~albertomilone/software-properties/software-properties/+merge/343882
[09:03] <didrocks> duflu: I think ureadahead is disabled on ssd?
[09:04]  * duflu shrugs. "never trust log messages"
[09:05] <duflu> seb128, those login problems are suddenly gone btw. I was trying to get detailed logs. Plus I can't reproduce on other machines
[09:06] <seb128> :/
[09:06] <Nafallo> I had a login problem this morning. not sure what happened.
[09:06] <seb128> heisenbug
[09:07] <Nafallo> after login I just had a purple screen, and could move the bluetooth mouse
[09:07] <seb128> did you had a failed login first?
[09:07] <duflu> Nafallo, bug 1766137
[09:07] <ubot5`> bug 1766137 in gnome-shell (Ubuntu) "[regression] Login fails when preceded by incorrect password" [High,Incomplete] https://launchpad.net/bugs/1766137
[09:07] <Nafallo> nope. pretty sure it wasn't a failed login...
[09:07] <Nafallo> but then again, perhaps.
[09:08] <duflu> Nafallo, sorry bad bug description
[09:08] <alexarnaud> jbicha: Do you plan to add a symlink on the sane package to avoid work around describe on this bug: https://bugs.launchpad.net/bugs/1707352
[09:08] <ubot5`> Ubuntu bug 1707352 in sane-backends (Debian) "the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane" [Unknown,New]
[09:08] <Nafallo> once I did the ctrl+alt dance to a different terminal and back, gdm came back with a login screen.
[09:08] <Nafallo> after that it worked :-)
[09:08] <duflu> bug 1766137 :)
[09:08] <ubot5`> bug 1766137 in gnome-shell (Ubuntu) "[regression] Login fails (blank purple screen and mouse pointer only)" [High,Incomplete] https://launchpad.net/bugs/1766137
[09:08]  * Nafallo takes a look
[09:09] <seb128> didrocks, Laney, k, so that works in the sense the callback is called but it's screwed. I'm going to try again the drop/restore priviledge but keeping the definition so it doesn't get out of scope.
[09:09] <Nafallo> I thought the interesting thing was that the bluetooth mouse was already working, but perhaps that happens earlier on a system level?
[09:09] <Laney> seb128: don't, I tried that
[09:09] <seb128> didrocks, Laney, with that current change the dconf user file is root owned and the callback always return" false"
[09:09] <Laney> that is what I was describing yesterday
[09:10] <seb128> so I think it spawns a dconf-service as root
[09:10] <duflu> Nafallo, yes the BT mouse will work system-wide
[09:10] <seb128> and fails to read the user value
[09:10] <seb128> it gets the changed signal
[09:10] <seb128> but it always read as "false"
[09:10] <didrocks> probably due to different $HOME as well
[09:10] <didrocks> (/root)
[09:11] <seb128> so the wrong value is probably my fault
[09:11] <seb128> I used "gsettings.get_value(key).unpack()" in the callback
[09:11] <seb128> I should probably use the wrapper
[09:11] <seb128> that does the sudo/gsettings cmd dance to get from the correct user
[09:11] <didrocks> yeah…
[09:11] <seb128> but that's not going to resolve the fact that /run/...dconf/user is owned by root
[09:12] <seb128> and that makes gsettings unhappy/complaining about the permissions
[09:12] <duflu> Nafallo, in fact you can use your Bluetooth mouse in a VT too (if gpm is installed)
[09:12] <Nafallo> :-)
[09:12] <Laney> on_screen_reader_enabled_changed: False
[09:12] <Laney> on_screen_reader_enabled_changed: True
[09:12] <Laney> it works here
[09:12] <Laney> I don't have that root thing
[09:12] <Laney> let me reboot to a clean environment
[09:13] <seb128> Laney, https://paste.ubuntu.com/p/ZWww3TFdNy/ ... something is probably wrong in my diff
[09:13] <seb128> Laney, do you read the value using the wrapper?
[09:13] <Laney> it's like settings.get_boolean("screen-reader-changed") in the callback
[09:13] <Laney> enabled
[09:14] <Nafallo> duflu: thanks for pointing me in the right direction. I'll subscribe, but you seem able to reproduce this so no further action needed?
[09:15] <duflu> Nafallo, actually I can't reproduce it or the other bug today
[09:15] <duflu> It's not a midweek bug
[09:16] <Nafallo> duflu: okay. just let me know if I should do something then :-)
[09:18] <seb128> Laney, well it's not the callback, because I boot, go to a tty and do a gsettings get and get the dconf permission error, without trying to activate the callback in -dm first
[09:18]  * seb128 doesn't understand
[09:19] <duflu> Nafallo, maybe enable debug in /etc/gdm3/custom.conf, reboot, start watching 'journalctl -f' from an ssh login, then try and login and reproduce it.
[09:19] <duflu> Nafallo, because upstream wants more info: https://gitlab.gnome.org/GNOME/gnome-shell/issues/227
[09:20] <ubot5-ng> GNOME bug 227 in gnome-shell "Login fails when preceded by incorrect password" (comments: 7) [Opened]
[09:20] <ubot5`> Error: Gnome bug 227 could not be found
[09:21] <didrocks> the dconf perm error is on the tty with a simple get?
[09:21] <seb128> yes
[09:21] <seb128> same I've been doing since I started testing
[09:21] <didrocks> weird, I'm pretty sure I didn't see that yesterday
[09:21] <seb128> the file is indeed root owned
[09:21] <didrocks> ok, so no patch at all on ubiquity?
[09:21] <seb128> didrocks, https://paste.ubuntu.com/p/ZWww3TFdNy/
[09:21] <didrocks> just doing a get on a tty
[09:21] <seb128> that patch
[09:22] <seb128> booting in rescue.target, applying the patch
[09:22] <seb128> ctrl-D
[09:22] <seb128> waiting for -dm to be loaded
[09:22]  * didrocks fires up vm
[09:22] <seb128> going to a tty
[09:22] <didrocks> paste.ubuntu.com is annoying for copying raw patch, as requires login :/
[09:23] <seb128> didrocks, Laney, k, I changed back the sudo calls to use -E instead of '--preserve-env=DBUS_SESSION_BUS_ADDRESS' and no root problem anymore
[09:23] <seb128> weird, I tried the patch with '--preserve-env=DBUS_SESSION_BUS_ADDRESS' this morning and it seemed fine
[09:23] <seb128> I'm a bit puzzled now :/
[09:23] <seb128> but I tried 3 boots with the diff from pastebin before and I had the issue 3 times
[09:24] <didrocks> seb128: try to pass HOME
[09:24] <seb128> now I loaded the same diff but changed for -E
[09:24] <seb128> yeah
[09:24] <Laney> -H sets HOME
[09:24] <didrocks> oh right
[09:24] <seb128> k, I don't understand :/
[09:24] <Laney> what exactly are the steps to get this?
[09:24] <Nafallo> duflu: hmm. looks like we may not have confirmed this is actually a wrong login issue, right?
[09:25] <seb128> Laney, mine is
[09:25] <seb128> - pick "install" on the syslinux menu
[09:25] <seb128> - f6
[09:25] <seb128> systemd.unit=rescue.target
[09:25] <seb128> dhclient to have internet
[09:25] <seb128> wget the patch from people page (using the ip, I've no dns)
[09:25] <seb128> patch -p0 in /usr/lib/ubiquity
[09:25] <seb128> ctrl-D
[09:25] <seb128> -> ubiquity-dm loaded
[09:26] <seb128> then ctrl-alt-<fn> and gsettings get or look at at the log
[09:26] <duflu> Nafallo, I'm not going to comment in there further while I can't reproduce it. But when I could reproduce it I did confirm authentication is successful (as other people confirmed too). Only the gnome-shell process is missing
[09:26] <Laney> ok, thx
[09:26] <duflu> Also no crash file
[09:26] <seb128> Laney, didrocks, I need to go pick somebody, back in a bit and I re-do another testing round
[09:26] <Nafallo> duflu: excellent. that was the only part I thought was odd :-)
[09:27] <seb128> Laney, didrocks, what I tried now is http://people.canonical.com/~seb128/new ... that version gives me the root owned error, I did a try where I changed the --preserve-env to -E before applying the patch and that worked
[09:27] <seb128> orca started and read screen
[09:27] <seb128> anyway, bbiab
[09:28]  * didrocks starts a vm
[09:33] <didrocks> ok, confirming what seb128 says
[09:33] <didrocks> it tries to create /run/user/999/user
[09:34] <didrocks> I thought that was dconf-service would would try to create that file
[09:34] <didrocks> which is with the correct perms and id
[09:35] <didrocks> (and the folder 999 as well
[09:35] <didrocks> knowing we already have ~/.config/dconf/user with correct perm and ownership
[09:37] <didrocks> (also, we don't use XDG_RUNTIME_DIR for dconf here…)
[09:37] <didrocks> so something makes dconf fallback to XDG_RUNTIME_DIR maybe?
[09:38] <Nafallo> duflu: it will probably take a while. my other laptop was quite outdated and doing updates now ;-)
[09:38] <didrocks> HOME=/home/ubuntu in spawn dconf-service process, as expected by -H
[09:44] <didrocks> Laney: confirming laney?
[09:44] <Laney> yeah
[09:44] <Laney> it's probably XDG_RUNTIME_DIR
[09:44] <Laney> try adding that
[09:44] <didrocks> it's in the process…
[09:45] <didrocks> if you look at dconf-service
[09:45] <didrocks> but can try
[09:45] <Laney> you can't see what the gsettings calls had though
[09:45] <didrocks> yeah
[09:45] <didrocks> it's weird that setting XDG_RUNTIME_DIR would have it using $HOME instead of XDG_RUNTIME_DIR though
[09:45] <didrocks> but let's see
[09:46] <didrocks> XDG_RUNTIME_DIR is correct in ubiquity, so let's try to pass that to the gsettings call
[09:50] <jbicha> good morning
[09:50] <willcooke> tjaalton, duflu - sooo, PPA is built but before I installed it I wanted to make sure it was still broken, and.. it's not?! i.e. Installed slack and skype and it didnt kill the wayland session
[09:50] <willcooke> so I guess that's good :)
[09:50] <willcooke> hi jbicha
[09:51] <duflu> willcooke, only Mesa changed?
[09:51] <willcooke> I did an apt upgrade first and saw a new xwayland go past, so could be that
[09:51] <didrocks> hey jbicha
[09:51] <jbicha> willcooke: do you know if mpt is out this week. I'm disappointed that I haven't had any response to the 3 issues I filed mentioned at the end of https://github.com/CanonicalLtd/desktop-design/issues/66
[09:51] <ubot5-ng> CanonicalLtd bug 66 in desktop-design "Visual design for first-login window" (comments: 21) [Closed] - Assigned to lyubomir-popov (lyubomir)
[09:51] <ubot5`> Error: Could not gather data from Launchpad for bug #66 (https://launchpad.net/bugs/66). The error has been logged
[09:52] <didrocks> seb128: Laney: so, adding --preserve-env=XDG_RUNTIME_DIR in the gsettings call from ubiquity/gsettings.py works.
[09:53] <duflu> willcooke, the new xwayland doesn't sound related (https://launchpad.net/ubuntu/+source/xorg-server/2:1.19.6-1ubuntu4)
[09:53] <didrocks> seb128: Laney: still weird that setting that variable doesn't activate something which tries to write here instead of HOME, but oh well
[09:53] <didrocks> and confirming as well that the screen reader works in ubiquity-dm
[09:53] <willcooke> jbicha, sorry I don't know.  I haven't been in the office this week yet.  Perhaps Laney might have seen him in the office
[09:53] <didrocks> (well, it's in english…)
[09:53] <didrocks> but not a regression from 16.04 apparently
[09:53] <jbicha> I don't even know how Design works these days, to know if m_pt is responsible for desktop issues or if I should be pinging someone else
[09:54] <Laney> Saw him yesterday I Think
[09:54] <Laney> didrocks: ok, nice (you comma separated it with the session bus, or?)
[09:54] <didrocks> Laney: yes
[09:54] <ads20000> duflu: Ohh I didn't realize that was your IRC nick. Thanks for having a look at my bug and it's unfortunate that you don't have the same issue so that we can get what upstream is asking for. I'll try and get hold of someone's else's computer to SSH in from but my friends are trying to encourage me to study so it might be tricky xD
[09:54] <didrocks> both works, you can comma separate or repeat it
[09:55] <duflu> This is sounding familiar again. didrocks do you have a link to whatever you're discussing?
[09:55] <didrocks> switching to live session give you then orca in french
[09:55] <Laney> I added that to my branch
[09:56] <jbicha> Laney: sorry to interrupt, but could you review bug 1762293 ?
[09:56] <ubot5`> bug 1762293 in appstream-generator (Ubuntu) "FFE: Sync appstream-generator 0.7.1-3 (universe) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/1762293
[09:56] <Laney> looking fwd to the ubiquity mp to launch/track orca then
[09:56] <Laney> jbicha: not really, I'm actually trying to deploy that now so I don't have time for reviews
[09:56] <didrocks> duflu: this is an issue with orca not starting in the installer due to perm/ownership issues
[09:56] <Laney> I think I saw mp_t around
[09:57] <didrocks> Laney: pushed?
[09:57] <Laney> oops I accidentally pushed to trunk
[09:57] <Laney> :D
[09:57] <didrocks> :p
[09:57] <Laney> meant to go to my branch
[09:57] <didrocks> yeah, the typical issue with bzr and tracking branch
[09:57] <didrocks> yeah, I had your branch opened :)
[09:57] <Laney> oh well
[09:57] <didrocks> good enough ;)
[09:57] <Laney> its going to be reviewed again in the queue anyway
[09:58] <jbicha> Laney: asgen is unseeded universe so if we hadn't filed the FFe, maybe we could have just synced?
[09:58] <didrocks> ok, so let me try a live session directly
[09:58] <didrocks> and starts orca from it
[09:59] <Laney> the "new" patch clearly needs further work to track killing orca when you go to False, and that unpack stuff and "is True" needs replacing with get_boolean
[09:59] <Laney> so going to asgen stuff for a bit, ttyl
[10:01] <Laney> jbicha: (it can be backported, it's not a big deal, don't get worked up about it)
[10:02] <Laney> there have been lots of followup commits and fixups, the initial request was hasty
[10:02] <jbicha> the asgen package isn't a big deal to me, it was just on my list
[10:02] <Laney> ok, then I suggest closing this request
[10:03] <didrocks> seb128: Laney: ok, works as well when started from a live session + ubiquity started. However, it's in english and not in french again (compared to being started as part of the session, with ubiquity-dm first, activate a11y, quit to login to live), but not a regression from 16.04
[10:03] <Laney> alright, feel free to investigate that if you want (for .1 probably?)
[10:03] <Laney> thx!
[10:04] <didrocks> pressing Super+Shift+S again close orca
[10:04] <didrocks> (and there was only one running in the session, the one spawned by ubiquity)
[10:04] <Laney> in dm too?
[10:04] <didrocks> didn't try in dm, I'm in the live session case right now
[10:04] <jibel> Laney, can you review/merge this https://code.launchpad.net/~jibel/ubiquity/lp1741690_remove_separate_greetee_a11y_icon/+merge/343906 ?
[10:06] <duflu> seb128, willcooke, I'm heading off. Do you need me on Wed?
[10:06] <willcooke> duflu,  I think we're good.  Have a good one.
[10:07] <willcooke> (tested the PPA still works)
[10:07] <Laney> jibel: ask xnox or infinity please, trying to keep in asgen mode
[10:07] <Laney> looks like it has a conflict?
[10:07] <jibel> okay
[10:09] <sil2100> jibel: I can take a look as well, after the text conflicts get resolved
[10:10] <tseliot> Laney: I suppose you're too busy. jbicha or mvo maybe? https://code.launchpad.net/~albertomilone/software-properties/software-properties/+merge/343882 (LP: #1753333) (my fix works)
[10:10] <ubot5`> Launchpad bug 1753333 in software-properties (Ubuntu) "Using "Software and Updates -> Additional Drivers" to Switch Fails" [High,In progress] https://launchpad.net/bugs/1753333
[10:10] <sil2100> jibel: but I hear xnox already did ;)
[10:11] <Laney> tseliot: sorry, might get some time later
[10:11] <tseliot> Laney: ok, thanks
[10:15] <jibel> sil2100, conflicts in the changelog is fioxed
[10:15] <jibel> -o
[10:26] <tjaalton> willcooke: alright
[10:26] <jbicha> alexarnaud: symlinking library .so names is a very unusual step so no, I don't plan to do that
[10:27] <alexarnaud> jbicha: Are you not afraid of breaking of hardware during migration 16.04 => 18.04?
[10:27] <jbicha> alexarnaud: I suggest complaining upstream about the soname bump if you think it's a problem
[10:30] <alexarnaud> Don't you think it's not a packaging responsibility to maintain user experience during upgrade?
[10:32] <jbicha> I don't think it's Ubuntu place to add symlinks for different soname versions
[10:32] <willcooke> tkamppeter, have their been any changes to the printing stack in 17.10 in the last week or so?  I'm seeing many more "I found a printer" type notifications than usual, but could be my machine/network/printer/wind direction
[10:32] <jbicha> if bumping the soname is so disruptive to third party drivers, then maybe the soname shouldn't be bumped
[10:32] <willcooke> *there
[10:32] <alexarnaud> I understand
[10:33] <jbicha> Ubuntu also can't be the only distro with this issue…
[10:43] <alexarnaud> jbicha: I'll contact Debian maintainer. It's not possible to let broken hardware.
[10:45] <jbicha> mmm, Debian maintainer doesn't like Ubuntu people complaining about his package he left in experimental :|
[10:46] <alexarnaud> I know.
[10:46] <alexarnaud> You do a great job on this package anyway :).
[10:47] <alexarnaud> But I assume we don't target the same user base. My user isn't able to debug hardware after update.
[10:48] <jbicha> maybe talk to upstream (not Debian), sane-backends 1.0.27 was released almost a year ago
[10:51] <willcooke> seb128, you think this is anything to worry about?  https://errors.ubuntu.com/problem/eabb483bd4584c745292dbf0b45214b2f5d75013
[10:51] <willcooke> Looks like it's failing to get a lock, so probably something else going on at the same time
[10:53] <alexarnaud> jbicha: Thanks for you help and patience :).
[11:17] <seb128> back
[11:18] <seb128> Laney, didrocks, k, good that it was the env :) I'm unsure we need to deal with "killing" orca since it exit itself when the gsettings key goes to false from what I saw during testing
[11:19] <Laney> sounds OK then
[11:19] <Laney> a comment to say that would be good so nobody gets worried
[11:19] <seb128> willcooke, the error seems mostly noise to me, that should probably not trigger apport ... it looks like apt is already in use when unattendred-upgrades wakes up, it should probably just bail out and retry later
[11:20] <seb128> where?
[11:20] <seb128> I didn't follow up what's the curent state of the art mp
[11:20] <seb128> did anybody propose one with the orca activation?
[11:20] <seb128> or do you mean code comment?
[11:20] <Laney> not that I saw
[11:20] <Laney> when orca is launched
[11:20] <seb128> k
[11:36] <jbicha> GunnarHj: gnome-initial-setup looks better translated in French now
[11:37] <seb128> :)
[11:47] <GunnarHj> jbicha: Right, and in a few other languages. Quite a few missing, though, such as German and Chinese.
[11:52] <seb128> Laney, didrocks, jibel, https://code.launchpad.net/~seb128/ubiquity/start-screen-reader/+merge/343975
[11:54] <Laney> seb128: thanks, I'll leave two comments
[11:54] <seb128> thx
[11:56] <Laney> ok, three :P
[11:57] <seb128> Laney, I removed the read because it's working fine without it
[11:57] <seb128> but since the documentation mentions it you are probably right it's safer
[11:57] <Laney> ok, but it's correct to start orca anyway if the key is true isn't it?
[11:58] <seb128> yes
[13:08]  * kenvandine upgraded to bionic and lost wifi... 
[13:10] <seb128> didrocks, Laney, thanks for the review, pushed some tweaks (what took me longer is trying to get things indented correctly, yeah python :/)
[13:11] <seb128> and I'm not even sure that's right
[13:11] <seb128> like
[13:11] <seb128>             self.a11y_settings =
[13:11] <seb128>             Gio.Settings.new("org.gnome.desktop.a11y.applications")
[13:11] <seb128> looks weird to me :/
[13:12] <seb128> jibel, ^ sorry, just saw your review, already addresed with the changed I pushed for new review
[13:12] <didrocks> seb128: shouldn't you have self.a11y_settings = \
[13:12] <didrocks> ?
[13:12] <seb128> I hate python
[13:13] <didrocks> I guess also, you will get rejection with that alignement in pep8
[13:13] <jibel> np, maybe break after the opening parenthesis
[13:13] <seb128> didrocks, no, that's the one I had to use to not have rejections
[13:13] <seb128> jibel, you mean?
[13:14] <jibel> https://paste.ubuntu.com/p/s55mR8PYgd/
[13:14] <didrocks> seb128: I guess it pass because it's 2 statements for it
[13:14] <jibel> it's easier to read with the indentation than breaking at the = sign
[13:14] <didrocks> seb128: have you tried running it?
[13:14] <didrocks> I would be surprised it runs
[13:14] <didrocks> and so 2 instructions -> aligned -> ok
[13:15] <seb128> didrocks, you are right it needs the \, but then at what level does next line needs to indent?
[13:15] <seb128> python is so annoying in that regard
[13:15] <didrocks> seb128: ahah, so, there is where I have my issues with pep8 :)
[13:15] <seb128> well 79 lines limitation rather than python
[13:15] <didrocks> I generally do it incrementally :p
[13:15] <didrocks> trying to increment
[13:15] <didrocks> run pep8
[13:15] <didrocks> and so on…
[13:15] <jibel> and line break after the parenthesis is the style used in ubiquity
[13:16] <mgedmin> https://pypi.org/project/black/ is an ambitious new project that aims to format Python code automatically
[13:16] <seb128> right but "org.gnome.desktop.a11y.applications" is too long if I intend on the same level
[13:16] <seb128> or I need to cut the string
[13:16] <seb128> it's ridiculous
[13:16] <seb128> 79 is too low to intend
[13:16] <seb128> intend -> wrap
[13:16] <didrocks> seb128: come to my club!
[13:17]  * didrocks makes first members joining free for a year
[13:17] <seb128>             self.a11y_settings = Gio.Settings.new(
[13:17] <seb128>                                      "org.gnome.desktop.a11y.applications")
[13:17] <seb128> that seems to work
[13:17] <seb128> but it's not nice looking :/
[13:17] <didrocks> syntactically, it's working
[13:17] <didrocks> if pep8 is happy, good
[13:18] <didrocks> seb128: see, go, -> gofmt automatically ran for you, code automatically formatted, no debate :p
[13:19] <seb128> :)
[13:19] <seb128> k, pushed again
[13:19]  * mgedmin would indent 4 spaces more than the line above
[13:19] <jibel> +            self.a11y_settings = Gio.Settings.new(
[13:19] <didrocks> mgedmin: but then, you will be above the 79 chars limit
[13:19] <jibel> +                "org.gnome.desktop.a11y.applications")
[13:19] <seb128> jibel, you might need to pull --force, I didn't want to do 2 "white space commits" so changed the previous one and repushed --force :p
[13:19] <jibel> looks nicer
[13:20] <seb128> thx for the hint
[13:20]  * mgedmin meant what jibel pasted
[13:20] <jibel> seb128, it's fine
[13:20] <seb128> k, let's redo a test on the iso now
[13:20] <seb128> to see if I screwed anything
[13:20] <didrocks> ah "less" not more then
[13:22] <seb128> bah, and it's almost meeting-o-clock and I didn't start writting my summary
[13:26] <seb128> kenvandine, hey, sorry I just remember that I think you pinged me (was that yesterday?) for some snap testing?
[13:26] <seb128> I read that I think after been away but then forgot about it
[13:26] <kenvandine> seb128, no worries, osomon tested :)
[13:26] <kenvandine> gedit in stable now has translated dialogs :)
[13:26] <seb128> k; good
[13:26] <seb128> nice
[13:26] <Nafallo> heh. the days starting to blend together in release times, seb128 ? ;-)
[13:27]  * kenvandine now has a dedicated VM for french testing :)
[13:27] <Nafallo> haha
[13:27] <didrocks> seeing the amount of frenchies on this team, this isn't surprising :p
[13:27] <didrocks> huge progress made since 2010 (and even more since 2004 :p)! :)
[13:28] <Nafallo> hmm
[13:28] <Nafallo> I wonder what year I took evening French classes because of the Desktop team ;-)
[13:28] <Nafallo> 2005 perhaps?
[13:28] <didrocks> ahah
[13:28] <didrocks> tricked into it!
[13:29] <Nafallo> nah. didn't need much motivation to choose french to be honest :-)
[13:29] <seb128> didrocks, Laney, jibel, of course I screwed something, a11y_settings needs to be self.a11y_settings, I repushed over :p
[13:30] <Nafallo> meeting! :-D
[13:30] <didrocks> seb128: and you have to refix the identation to make it under 79 char… and… and… :)
[13:30] <kenvandine> meeting time!
[13:30] <kenvandine> #startmeeting Desktop Team Weekly Meeting - 2018-03-13
[13:30] <meetingology> Meeting started Tue Apr 24 13:30:57 2018 UTC.  The chair is kenvandine. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:30] <meetingology> Available commands: action commands idea info link nick
[13:31] <jbicha> o/
[13:31] <kenvandine> Roll call:  andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN (out), seb128, tkamppeter, trevinho, robert_ancell (out)
[13:31] <andyrock> o/
[13:31] <seb128> hey!
[13:31] <didrocks> hey!
[13:31] <jibel> o/
[13:32] <kenvandine> let's get started
[13:32] <kenvandine> Happy release week!
[13:32] <kenvandine> #topic andyrock
[13:32] <andyrock> hey
[13:32] <andyrock> Not a productive week, PTO Friday and sick yesterday.
[13:32] <andyrock> Completed:
[13:32] <andyrock> - Fixed LP: #1761841
[13:32] <andyrock> - Fixed LP: #1764989
[13:32] <andyrock> In progress:
[13:32] <andyrock> - Update upstream patch to add ubuntu-sso provider in gnome-online-accounts
[13:32] <andyrock> - Adding close buttons to ubuntu-welcome
[13:33] <andyrock> - LP: #1764723
[13:33] <andyrock> No RLS bug for me.
[13:33] <ubot5`> Launchpad bug 1761841 in update-notifier (Ubuntu) "Notification for livepatch are not shown." [Medium,Fix released] https://launchpad.net/bugs/1761841
[13:33] <ubot5`> Launchpad bug 1764989 in gnome-online-accounts (Ubuntu) "[ubuntusso] Cancelling polkit authentication shows a generic error" [Low,Fix released] https://launchpad.net/bugs/1764989
[13:33] <ubot5`> Launchpad bug 1764723 in gnome-initial-setup (Ubuntu) "gnome-initial-setup says that Livepatch is "all set" even if enabling is still in progress." [Medium,In progress] https://launchpad.net/bugs/1764723
[13:33] <andyrock> eow
[13:33] <kenvandine> andyrock, thx!
[13:33] <kenvandine> #topic dgadomski
[13:33] <dgadomski> hey
[13:33] <dgadomski> * verified latest patch for bug #1764668
[13:33] <dgadomski> * debugging a problem with WPA2 enterprise (EAP-TLS) with NM and wpasupplicant directly. I'm going to gather all info and report a lp bug.
[13:34] <ubot5`> bug 1764668 in libvirt (Ubuntu Bionic) "guest cleanup script fails to iterate" [Undecided,In progress] https://launchpad.net/bugs/1764668
[13:34] <dgadomski> eof
[13:34] <kenvandine> dgadomski, thx
[13:34] <kenvandine> #topic didrocks
[13:34] <didrocks> Telemetry:
[13:34] <didrocks>   * Multiple ubuntu-report fixes/enhancements (https://launchpad.net/ubuntu/+source/ubuntu-report/1.0.8):
[13:34] <didrocks>     - complex screen configs with multiple frequencies
[13:34] <didrocks>     - add timeout config for hanging servers
[13:34] <didrocks>     - list architecture as part of POST data
[13:34] <didrocks>   * After discussions, switch to vendor dependencies for support in ubuntu-report:
[13:34] <didrocks>     - change autopkgtests and ship now upstream vendor dependencies (1.0.9 + 1.0.10)
[13:34] <didrocks>   * Switch to reading from chassis_vendor to sys_vendor after talking to Entroware (https://launchpad.net/ubuntu/+source/ubuntu-report/1.0.11)
[13:34] <didrocks>   * Seed gnome-initial-setup and ubuntu-report CLI tool (https://launchpad.net/ubuntu/+source/ubuntu-meta/1.417)
[13:34] <didrocks> Communitheme:
[13:34] <didrocks>   * Investigate only second login working on Wayland for communitheme. After investigation, this results in 2 bugs:
[13:34] <didrocks>     - one communitheme specific one, which under Wayland, doesn't set default paths (the scripts are running after wrapper on Wayland, contrary to Xorg): https://github.com/ubuntu/communitheme-snap-helpers/commit/46413618dcd52555d844262bbd69dfd4700568e2
[13:34] <didrocks>     - another one where old sessions aren't properly closed, and we were blindly appending the same values multiple times. Fixed in xorg https://salsa.debian.org/xorg-team/xorg/merge_requests/3, https://salsa.debian.org/xorg-team/xorg/merge_requests/4. Fix in gnome-session https://launchpad.net/ubuntu/+source/gnome-session/3.28.1-0ubuntu2. Proposed fix in snapd (waiting for it to be reviewed):
[13:34] <ubot5-ng> X Strike Force bug (Merge request) 3 in xorg "Protect against multipleadditions of the same paths to XDG_CONFIG_DIRS" (comments: 0) [Merged]
[13:34] <didrocks> https://github.com/snapcore/snapd/pull/5075.
[13:34] <ubot5-ng> X Strike Force bug (Merge request) 4 in xorg "Protect duplication in XDG_DATA_DIRS" (comments: 0) [Merged]
[13:34] <ubot5-ng> snapcore bug (Pull request) 5075 in snapd "snap/env: fix env duplication logic" (comments: 1) [Open]
[13:34] <didrocks>     - This incindently fixes Visual Studio Code, slack and other electrons apps crashing after multiple logout/login: https://launchpad.net/bugs/1764355
[13:34] <ubot5`> Ubuntu bug 1764355 in xorg (Ubuntu) "Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login" [Undecided,Fix released]
[13:34] <didrocks>   * ubuntu-settings communitheme's change default font (https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1764974)
[13:34] <ubot5`> Ubuntu bug 1764974 in ubuntu-settings (Ubuntu) "Change default interface font size in Community theme" [Undecided,Fix released]
[13:34] <didrocks>   * Restore edge -> master snap autopublication (https://github.com/ubuntu/communitheme-snap-helpers/commit/c39b212dfaa695fed7a2682e55f2d9301bac459f)
[13:34] <didrocks>   * Continue publishing inteviews on my blog (will be done on Wednesday)
[13:34] <didrocks>   * Discussing, bug triaging and answers
[13:35] <didrocks> Misc:
[13:35] <didrocks>   * Review lightdm-settings NEW package for double checking confirmation for sil_2100
[13:35] <didrocks>   * Debug and inspect ubiquity "no callback" with a proposed fallback fix (http://pastebin.com/raw/Wjh0K2Pg)
[13:35] <didrocks> No rls bug assigned remaining.
[13:35] <didrocks> .
[13:35] <kenvandine> didrocks, thx
[13:35] <didrocks> yw!
[13:35] <kenvandine> #topic duflu
[13:35] <kenvandine> * GJS:
[13:35] <kenvandine>   - Fix released for that massive crash regression that started last week (https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1763878). Although we continue to collect duplicates from machines not yet updated...
[13:35] <kenvandine>   - Gnome Shell memory leaks are also much reduced by the same gjs update (https://launchpad.net/bugs/1672297)
[13:35] <kenvandine> * Gnome Shell performance improvements improve!
[13:35] <kenvandine>   - [20% drop in render time/GPU/CPU usage] Disabled mipmapping on window previews: https://gitlab.gnome.org/GNOME/mutter/merge_requests/89
[13:35] <ubot5`> Ubuntu bug 1763878 in gjs (Ubuntu) "[regression] Many programs crashing at exit with assert failure: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed. Called from cairo_debug_reset_static_data()" [High,Fix released]
[13:35] <ubot5-ng> GNOME bug (Merge request) 89 in mutter "MetaShapedTexture: Disable mipmapping (emulation)" (comments: 1) [Opened]
[13:35] <ubot5`> Ubuntu bug 1672297 in gjs (Ubuntu Bionic) "gnome-shell uses lots of memory, and grows over time" [Critical,In progress]
[13:35] <kenvandine>   - [50% drop in CPU/GPU usage] Iterated on my previous offscreening optimization: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/73
[13:35] <ubot5-ng> GNOME bug (Merge request) 73 in gnome-shell "js/ui: Choose some actors to cache on the GPU" (comments: 5) [Opened]
[13:35] <kenvandine>   - [20% drop in CPU usage] Revived another great little fix that upstream forgot: https://gitlab.gnome.org/GNOME/mutter/merge_requests/87
[13:35] <ubot5-ng> GNOME bug (Merge request) 87 in mutter "ClutterActor: Preserve valid paint volumes till the next relayout/repaint" (comments: 2) [Opened]
[13:35] <kenvandine>   - Happy news: A couple of my older performance fixes finally made it into bionic (mutter 3.28.1-1):
[13:35] <kenvandine>     . https://gitlab.gnome.org/GNOME/mutter/commit/b2f9de98
[13:35] <kenvandine>     . https://salsa.debian.org/gnome-team/mutter/blob/debian/master/debian/patches/clutter-Smooth-out-master-clock-to-smooth-visuals.patch
[13:36] <kenvandine>   - Reorganized the performance issues into two lists (many list items are in progress but you can't tell):
[13:36] <kenvandine>     . https://trello.com/c/Q6JYXPPs
[13:36] <kenvandine>     . https://trello.com/c/pe5mRmx7
[13:36] <kenvandine> * Totem performance, back under investigation, tried and failed (https://trello.com/c/7zeMdP0S)
[13:36] <kenvandine>   - Implemented multi-buffering in clutter-gst to try and fix stuttering. Unfortunately it didn't help. Turns out the bottleneck is in the GL(X) rendering, which never catches up to decoding so can't benefit from buffering.
[13:36] <kenvandine>   - Implemented direct pixmap-texture rendering to reduce the GPU load in gstreamer-vaapi. Unfortunately it didn't help by an adequate amount. And is not quite polished enough to propose upstream yet. Now with less reason to finish it.
[13:36] <kenvandine>   - Given up for now. See https://trello.com/c/7zeMdP0S
[13:36] <kenvandine> * Trying to figure out login failures (only started last week):
[13:36] <kenvandine>   - https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1765261
[13:36] <ubot5`> Ubuntu bug 1765261 in gdm3 (Ubuntu) "[regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt" [High,Incomplete]
[13:36] <kenvandine>   - https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137
[13:36] <ubot5`> Ubuntu bug 1766137 in gnome-shell (Ubuntu) "[regression] Password accepted but login fails (blank purple screen and mouse pointer only)" [High,Confirmed]
[13:36] <kenvandine> * Daily bug management across gnome-shell, mutter, gdm3, ubuntu-themes, bluez, pulseaudio, dkms, wayland, totem, mpv, libinput.
[13:36] <kenvandine>   - Not a great week this week: https://docs.google.com/spreadsheets/d/e/2PACX-1vRDHPxGBHqM6XkT_S8ggtYfD0xchKSUD_z9PopNVE3G1rU05fVSnxDGcDsEstl7gu7N-tzCU6mLUp2V/pubchart?oid=254968654&format=interactive
[13:36] <kenvandine>   - So I'm about to put out a public call for people to adopt some neglected packages: gnome-terminal, gedit and gnome-control-center...
[13:36] <kenvandine> #topic jbicha
[13:36] <jbicha> • Removed gksu from Ubuntu
[13:36] <jbicha> • Haven't removed old webkitgtk yet. Blocker is gnucash. gnucash 3.0 was ported to gtk3 but its build tests fail in Ubuntu (but not in Debian!) bug 1758740
[13:36] <ubot5`> bug 1758740 in gnucash (Ubuntu) "FFe: Sync gnucash 1:3.0-1 (universe) from Debian experimental (main)" [Wishlist,Incomplete] https://launchpad.net/bugs/1758740
[13:36] <jbicha> • Applied gegl security fix for bionic bug 1765563
[13:36] <ubot5`> bug 1765563 in gegl (Ubuntu Artful) "gegl: CVE-2018-10114 (ppm)" [Undecided,New] https://launchpad.net/bugs/1765563
[13:37] <jbicha> • Sponsored late mutter & gnome-shell updates yesterday
[13:37] <jbicha> • No progress on my bionic tracking bug 1761554, sorry
[13:37] <ubot5`> bug 1761554 in gnome-shell (Ubuntu Bionic) "[bionic] Extended characters in GNOME screen keyboard don't get entered" [Medium,Triaged] https://launchpad.net/bugs/1761554
[13:37] <jbicha> 🎳
[13:37] <kenvandine> jbicha, thx
[13:37] <kenvandine> #topic jamesh
[13:37] <kenvandine> snapd:
[13:37] <kenvandine> * The user-mounts branch is hopefully ready to merge: all the spread
[13:37] <kenvandine> tests pass, code review, and security review.  However Gustavo wanted
[13:37] <kenvandine> to do one last review prior to merging:
[13:37] <kenvandine> https://github.com/snapcore/snapd/pull/3963
[13:37] <kenvandine> * I put together a requested followup to expand the bind mount code to
[13:37] <ubot5-ng> snapcore bug (Pull request) 3963 in snapd "cmd/snap-confine: add support for per-user mounts" (comments: 21) [Open]
[13:37] <kenvandine> handle file bind mounts: https://github.com/snapcore/snapd/pull/5082
[13:37] <ubot5-ng> snapcore bug (Pull request) 5082 in snapd "cmd/snap-update-ns: use Secure.BindMount to bind mount files" (comments: 1) [Open]
[13:37] <kenvandine> * I'm currently testing a third branch to plumb xdg-document-portal
[13:37] <kenvandine> into the sandbox using user-mounts, which will allow testing out the
[13:37] <kenvandine> file open/file save features of the desktop portal.
[13:38] <kenvandine> #topic jibel/heber
[13:38] <jibel> Release week and release testing, still need a fix in the installation for the screen reader which should be really soon.
[13:38] <jibel> and that's all
[13:38] <kenvandine> jibel, thx
[13:38] <kenvandine> #topic kenvandine
[13:38] <kenvandine> * Merged LD_PRELOAD of bindtextdomain PR and rebuild the gedit snap in the store. https://github.com/ubuntu/snapcraft-desktop-helpers/pull/106
[13:38] <kenvandine> * Created new gnome-3-28-1804 based on bionic and published it in the store.
[13:38] <kenvandine>   - requested auto-connect of the content interface as well https://forum.snapcraft.io/t/auto-connection-for-gnome-3-28-1804-content-interface/5043/3
[13:38] <kenvandine>   - Note this requires base:core18 which is currently only available in the edge channel but destined to stable any day
[13:38] <ubot5-ng> ubuntu bug (Pull request) 106 in snapcraft-desktop-helpers "LD_PRELOAD bindtextdomain to load translations from multiple paths" (comments: 1) [Closed]
[13:38] <kenvandine> * Created branches of snaps to use gnome-3-28-1804 and core18
[13:38] <kenvandine>   - gnome-calculator and gnome-characters are in the beta channel
[13:38] <kenvandine>   - gnome-logs is in the works
[13:39] <kenvandine> * Working on generating desktop-preinstalled images
[13:39] <kenvandine> * No assigned rls bugs
[13:39] <kenvandine> ⚾
[13:39] <kenvandine> #topic laney
[13:39] <Laney> sry
[13:39] <Laney> it's a bit lame, room is busy
[13:39] <Laney> queue reviews
[13:39] <Laney> • more asgen work, the new version is deployed and generating now
[13:39] <Laney> • some debugging / help(?) with ubiquity & orca & permissions
[13:39] <Laney> • couple of FTBFS fixed
[13:40] <Laney> • pkgbinarymangler broke the archive, fixed that
[13:40] <Laney> • ported udisks2 delta back to debian, fwded remaining patch upstream, re-enabled libblockdev-crypto2, uploaded & synced
[13:40] <Laney> 𝌚 ("tetragram for release")
[13:40] <kenvandine> Laney, is the release sprint going well?
[13:41] <Laney> yeah it's fine
[13:41] <Laney> needs moar ubiquity
[13:41] <kenvandine> cool, no hair on fire i guess :)
[13:41] <kenvandine> Laney, thx
[13:41] <seb128> Laney, I've updated the mp, I think it addressed your review comments
[13:41] <kenvandine> #topic oSoMoN(out)
[13:41] <Laney> seb128: yeh, will look
[13:42] <seb128> thx
[13:42] <kenvandine> out the rest of the week and didn't send a status report
[13:42] <kenvandine> #topic seb128
[13:42] <seb128> • daily launchpad bugs & e.u.c reviews
[13:42] <seb128> • iso testing
[13:42] <seb128> • ubiquity debugging, wasted some days to understand what was going on. Thanks Laney, didrocks and jibel for helping debugging and for the code reviews, we got a working set of changes now
[13:42] <seb128> • helped with some translations issues
[13:42] <seb128> • discussed/reviewed gnome-initial-setup bugs/proposed changes
[13:42] <seb128> • sponsored some nautilus fixes from Trevinho
[13:42] <seb128> • milestoned bugs
[13:42] <seb128> ∘ bug #1726143, no update, the "milestoned" part is fixed the remaining is for SRU or later
[13:42] <ubot5`> bug 1726143 in nautilus-share (Ubuntu Bionic) "Automatic installation of samba fails with "could not find package libpam-smbpass"" [High,Confirmed] https://launchpad.net/bugs/1726143
[13:43] <seb128> (probably other bugs poking I forgot to list, I've been busy with ubiquity all day and forget to properly wrote the summary, just did in a rush)

[13:43] <kenvandine> seb128, thx
[13:43] <kenvandine> #topic tkamppeter
[13:43] <tkamppeter> - cups-filters: Made cups-browsed able to re-generate queues correctly when queues it had created got remove or overwritten. Required major changes in printer discovery and queue creation process.
[13:43] <tkamppeter> - Google Summer of Code 2018: Student projects are officially announced by Google. Started/continued mentoring.
[13:43] <tkamppeter> - Bugs.
[13:43] <kenvandine> tkamppeter, thx
[13:43] <kenvandine> #topic trevinho
[13:44] <kenvandine> · gnome-shell and mutter (downstream):
[13:44] <kenvandine>   - Some fixes on the proposed patches, and added new one:
[13:44] <kenvandine> https://code.launchpad.net/~3v1n0/gnome-shell/bionic-patches-add-gpu-cached-texture/+merge/343565
[13:44] <kenvandine> https://code.launchpad.net/~3v1n0/gnome-shell/bionic-patches-picks-reorder/+merge/343564
[13:44] <kenvandine>     https://salsa.debian.org/gnome-team/mutter/merge_requests/2
[13:44] <ubot5-ng> GNOME bug (Merge request) 2 in mutter "debian/patches: handle xwayland crashes better" (comments: 2) [Merged]
[13:44] <kenvandine> · gnome-shell and mutter (upstream):
[13:44] <kenvandine>   - https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/79
[13:44] <ubot5-ng> GNOME bug (Merge request) 79 in gnome-shell "St cache texture destroy fixes" (comments: 0) [Opened]
[13:44] <kenvandine>   - https://gitlab.gnome.org/GNOME/mutter/merge_requests/84
[13:44] <ubot5-ng> GNOME bug (Merge request) 84 in mutter "window: Return -1 if meta_window_get_monitor is called on an unmanaged window" (comments: 0) [Opened]
[13:44] <kenvandine>   - https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/82
[13:44] <ubot5-ng> GNOME bug (Merge request) 82 in gnome-shell "Support unmanaged windows monitor index (negative)" (comments: 0) [Opened]
[13:44] <kenvandine>   - https://gitlab.gnome.org/GNOME/mutter/merge_requests/63 (rework)
[13:44] <ubot5-ng> GNOME bug (Merge request) 63 in mutter "theme: Override theme using GTK_THEME env variable" (comments: 20) [Opened]
[13:44] <kenvandine>   - https://gitlab.gnome.org/GNOME/mutter/merge_requests/85
[13:44] <ubot5-ng> GNOME bug (Merge request) 85 in mutter "cogl: Do not unref a NULL object" (comments: 0) [Opened]
[13:44] <kenvandine>   - Upstream reviews, cherry-picks and merges
[13:44] <kenvandine> · gtk (affects nautilus):
[13:44] <kenvandine>   - https://gitlab.gnome.org/GNOME/gtk/merge_requests/117
[13:44] <ubot5-ng> GNOME bug (Merge request) 117 in gtk "stack: protect set_visible_child_name from NULL stack" (comments: 1) [Merged]
[13:44] <kenvandine>   - https://gitlab.gnome.org/GNOME/gtk/merge_requests/118
[13:44] <ubot5-ng> GNOME bug (Merge request) 118 in gtk "Gtkplacesview finalization fixes" (comments: 0) [Closed]
[13:44] <kenvandine> · nautilus (upsteram):
[13:44] <kenvandine>   - https://gitlab.gnome.org/GNOME/nautilus/merge_requests/195
[13:44] <ubot5-ng> GNOME bug (Merge request) 195 in nautilus "window-slot: Clear pending selection after freeing it" (comments: 3) [Merged]
[13:44] <kenvandine>   - https://gitlab.gnome.org/GNOME/nautilus/merge_requests/98 (updated)
[13:44] <kenvandine>   - https://gitlab.gnome.org/GNOME/nautilus/merge_requests/112 (updated)
[13:44] <ubot5-ng> GNOME bug (Merge request) 98 in nautilus "Recent Files search provider" (comments: 26) [1. Feature, 5. Search, Opened]
[13:44] <kenvandine> · Theme fixes and rework (all landed):
[13:44] <ubot5-ng> GNOME bug (Merge request) 112 in nautilus "directory: update recent files manager on rename or file move" (comments: 30) [1. Feature, 5. Operations, Opened]
[13:44] <kenvandine>   - https://code.launchpad.net/~3v1n0/ubuntu-themes/infobar-default-color/+merge/343749
[13:44] <kenvandine>   - https://code.launchpad.net/~3v1n0/ubuntu-themes/placessidebar-improvements/+merge/343748
[13:44] <kenvandine>   - https://code.launchpad.net/~3v1n0/ubuntu-themes/menubar-colors-fixes/+merge/343663
[13:45] <kenvandine> · Fixed the indicator-sound FTBFS (and landed):
[13:45] <kenvandine> https://code.launchpad.net/~3v1n0/indicator-sound/tests-environment-fixes/+merge/343741
[13:45] <kenvandine> · Fixed a build issue in the telegram-snap:
[13:45] <kenvandine> https://github.com/3v1n0/telegram-snap/commits?author=3v1n0&since=2018-04-18T06:00:00Z&until=2018-04-25T05:00:00Z
[13:45] <kenvandine> · Working on ther JS fixes and nautilus crashes / issues
[13:45] <kenvandine> #topic robert_ancell(out)
[13:45] <kenvandine> Holiday this week
[13:45] <kenvandine> #topic http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:46] <kenvandine> desktop only has one bug?
[13:46] <seb128> which is fixed
[13:47] <seb128> well, fix is in proposed
[13:47] <kenvandine> great!
[13:47] <seb128> I guess people have been too busy to tag things :p
[13:47] <seb128> there is lot we need to fix in SRUs but not for release at this point
[13:47] <kenvandine> cool
[13:47] <kenvandine> #topic aob
[13:49] <didrocks> kenvandine: do you think that if we don't get GNOME 3.28 snaps that we can get the slot autoconnecting and such for gtk-common-theme?
[13:49] <didrocks> kenvandine: as you saw, I have daily pings (even multiple today :p)
[13:49] <didrocks> so the community is eager it seems to have theme snaps (especially in communitheme where they are transparent)
[13:50] <kenvandine> didrocks, we need to request the auto-connect on the forum
[13:50] <didrocks> kenvandine: mind doing that? Happy to help, but you already have done it for the platform, correct?
[13:50] <kenvandine> didrocks, updating all the snaps wasn't at the top of my todo list, i really want to get back to the hyper-v image
[13:51] <didrocks> kenvandine: ok, willcooke told me to mention it to you and check, so I guess done :p
[13:51] <kenvandine> i'll file the auto-connect request
[13:51] <didrocks> thanks!
[13:51] <kenvandine> it'll be later this week before i can update all the snaps
[13:51] <seb128> kenvandine, we don't care about 'all the snaps" for the release but we might about those on the iso?
[13:52] <seb128> or what core is going to be seeded on the iso?
[13:52] <kenvandine> seb128, true, i can quickly update the seeded snaps
[13:52] <kenvandine> core 16
[13:52] <kenvandine> too late to change that
[13:52] <seb128> k, so we probably want to stay on that for our snaps for the release
[13:52] <kenvandine> i really wanted to switch to core18
[13:52] <seb128> we can update in the store after release
[13:52] <kenvandine> but it hasn't made it to stable yet
[13:52] <kenvandine> right
[13:52] <didrocks> is autodownload of default content-provider will work on snap refresh?
[13:53] <kenvandine> i can add the theme support to the seeded snaps though
[13:53] <jibel> seb128, pep8 tests are still failing, line 727 is over indented
[13:53] <kenvandine> oh... install yes but not sure about refresh
[13:53] <kenvandine> i'd assume
[13:53] <didrocks> worth a test :)
[13:53] <didrocks> thanks kenvandine!
[13:53] <Laney> jibel: I fixed it when merging
[13:53] <jibel> thx
[13:53] <kenvandine> mvo, ^^ will autodownload of default provider happen on refresh?
[13:54] <Laney> not that push is finishing
[13:54] <seb128> jibel, Laney, thx, I don't understand why it doesn't tell me about it here :/
[13:54] <seb128> $ pep8 ubiquity/frontend/gtk_ui.py | grep -v E402
[13:54] <seb128> $
[13:54] <seb128> oh well
[13:54] <seb128> thanks Laney!
[13:55] <Laney> I ran tests/run-pep8
[13:55] <Laney> or whatever it is
[13:55] <kenvandine> didrocks, actually i'd rather not add the theme bits to the seeded snaps right now, because that would mean we should really seed the common themes snap
[13:55] <kenvandine> seems too late to update the seed
[13:55] <jibel> i built the package to install it on the iso
[13:56] <seb128> funny
[13:56] <didrocks> kenvandine: so, maybe on release day?
[13:56] <kenvandine> yeah
[13:56] <didrocks> as long as snap refresh install the default provider, sounds good :)
[13:56] <kenvandine> at least in the candidate channel by release day :)
[13:57] <kenvandine> so we can get some testing in
[13:57] <didrocks> yeah ;)
[13:57] <didrocks> then pushing the trigger!
[13:57] <kenvandine> didrocks, i'll make sure to get an answer on the downloading of the default provider
[13:57] <seb128> we can probably wrap the meeting
[13:57] <kenvandine> yeah...
[13:57] <seb128> seems like discussion drifted to non meeting specific chatting
[13:57] <kenvandine> seems done with AOB
[13:57] <kenvandine> #endmeeting
[13:57] <meetingology> Meeting ended Tue Apr 24 13:57:40 2018 UTC.
[13:57] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-04-24-13.30.moin.txt
[13:57] <didrocks> kenvandine: perfect, keep me posted!
[13:57] <kenvandine> thanks all!
[13:57] <didrocks> thx
[13:57] <seb128> thanks!
[13:57] <seb128> $ pep8 ubiquity/frontend/gtk_ui.py | grep E126
[13:57] <seb128> $
[13:58] <seb128>  pep8 --ignore=E402 ubiquity/frontend/gtk_ui.py
[13:58] <Nafallo> 2018-03-13 :-D
[13:58] <seb128> ubiquity/frontend/gtk_ui.py:727:38: E126 continuation line over-indented for hanging indent
[13:58] <seb128> go figure
[13:59] <jbicha> andyrock: people don't like that gnome-initial-setup doesn't have window buttons?
[13:59] <andyrock> jbicha: seb128 asked me to add them
[14:00] <jbicha> andyrock: do you know about new user mode for gnome-initial-setup?
[14:00] <seb128> jbicha, some don't want to be bothered with a welcome wizard and want to be able to close it without having to go through the steps
[14:00] <andyrock> jbicha: we use the existing user mode
[14:01] <seb128> jbicha, we are just investigating that change atm, not going with it
[14:01] <andyrock> jbicha: we'll show the button if it's "existing-user-mode" and the current desktop is "ubuntu"
[14:02] <jbicha> seb128: there is a Quit button in the app menu that works; however it is designed so that the wizard will come back on next login until your complete it
[14:02] <jbicha> the current version is only 3 screens
[14:03] <jbicha> andyrock: ok
[14:05] <seb128> jbicha, maybe we should just change it to not come back in ubuntu session if that item is used
[14:05] <seb128> the decoration buttons look a bit weird
[14:11] <mvo> kenvandine: auto-download of new/changes default providers is not implemented at this point. its very high on the todo list and we expect it for the next release. do you need it more urgently?
[14:12] <andyrock> seb128: I can do that as well
[14:12] <andyrock> your call
[14:12] <seb128> andyrock, I think that would make sense
[14:13] <andyrock> ok so I just need to create the stamp file if that action is triggered (and if it's an ubuntu session)
[14:13] <seb128> yeah
[14:13] <seb128> thx andyrock
[14:14] <seb128> sorry for not thinking about that first, I think it's good enough for us
[14:14] <andyrock> I'll open a bug too, to track the status
[14:15] <seb128> thx
[14:16] <didrocks> mvo: do you mind mentionning this on https://forum.snapcraft.io/t/snap-application-and-snap-themes/4946? Telling that communitheme snap won't work with other snaps until this is implemented? I have daily pings about it right now…
[14:16] <didrocks> and having a reference point would be great!
[14:21] <kenvandine> mvo, well yeah, as our default snaps update to use core18 and gnome-3-28-1804 content interface
[14:21] <kenvandine> we need to ensure those are downloaded automatically
[14:21] <kenvandine> mvo, same for the content interfaces being added for the themes
[14:22] <mvo> kenvandine, didrocks I push that even higher now
[14:23] <kenvandine> mvo, how about autoconnect on refresh?
[14:24] <kenvandine> if we change the snap to use gnome-3-28-1804 instead of gnome-3-26-1604
[14:24] <kenvandine> it should connect on refresh right?
[14:33] <jibel> didrocks, your change to add the oem key to telemetry makes the installer crash
[14:34] <didrocks> jibel: oh! :( I did a quick try by maybe mistype after this?
[14:34] <didrocks> jibel: do you have the stacktrace?
[14:34] <jibel> didrocks, http://paste.ubuntu.com/p/CCpDKV9jq2/
[14:35] <didrocks> jibel: was it running in oem mode?
[14:35] <jibel> didrocks, no
[14:35] <jibel> normal installation
[14:36] <jibel> Laney, ^^ do not release ubiquity 18.04.11 pls
[14:36] <didrocks> Laney: jibel: let's get it this MR out to not delay it more
[14:36] <jibel> agreed
[14:37] <Laney> unlucky
[14:37] <didrocks> jibel: not sure I understand the stacktrace though, it's the same key than you mentioned as well oem-config/enable
[14:37] <Laney> jibel: push a revert?
[14:37] <jibel> yes revert it, it's a minor change
[14:37] <Laney> sorry, I meant can *you* push it please :P
[14:38] <jibel> :)
[14:40] <didrocks> if self.db.get('oem-config/enable') == 'true'…
[14:41]  * didrocks puzzled, the rest of ubiquity code is using it
[14:46] <jibel> reverted
[14:46] <didrocks> thx jibel
[14:47] <jibel> ubiquity's full of mysteries ...
[14:47] <didrocks> yeah, I'm really puzzled on that one
[14:47] <didrocks> maybe only oem_user_config is working
[14:47] <didrocks> which is the OEM mode set and ignoring getting the oem-config key
[14:48]  * didrocks doesn't know the different between the 2 and it's not documented
[14:50] <xclaesse> wow, alt-F4 switch to TTY instead of ctr-alt-F4
[14:50] <jibel> the good news is that the screen reader is now working \o/
[14:50] <xclaesse> that must be a really recent regression in 18.04, haven't noticed that behaviour previously
[14:51] <jibel> xclaesse, are you using wayland?
[14:51] <mvo> kenvandine yeah, auto-connect on refresh should be fine
[14:51] <jbicha> xclaesse: are you in a virtual machine?
[14:51] <kenvandine> mvo, cool
[14:52] <mvo> kenvandine (sorry for the delay, I had a meeting)
[14:52] <kenvandine> mvo, so we really need autodownload
[14:52] <xclaesse> don't think so
[14:52] <xclaesse> not a VM, no
[14:53] <seb128> xclaesse, did you recently update? those are usually weird console-setup cases
[14:53] <mvo> kenvandine: I look into it today/tomorrow
[14:54] <xclaesse> seb128: I updated this morning but didn't restart the session
[14:54] <xclaesse> maybe I should reboot
[14:54] <kenvandine> mvo, thx
[14:54] <seb128> xclaesse, yeah, you should, I think the system is in a weird state maybe
[14:56] <didrocks> the console-setup issue back again maybe :(
[15:00] <xclaesse> seb128: ok, reboot fixed it... thanks
[15:03] <seb128> xclaesse, nice, yw
[15:03] <seb128> didrocks, yeah, in some upgrades cases :/
[15:05] <jbicha> seb128: what do you think about LP: #1766575 ? I think it's safe for 18.04 (but arguably not very important either)
[15:05] <ubot5`> Launchpad bug 1766575 in gnome-control-center (Ubuntu) "Drop libnss-myhostname recommends" [Low,New] https://launchpad.net/bugs/1766575
[15:07] <seb128> jbicha, I don't have a strong opinion, ask #ubuntu-release if they consider it worth taking for a respin?
[15:07] <seb128> otherwise I think it's fine as a SRU
[15:08] <Laney> probably rather people stopped uploading already
[15:09] <seb128> jbicha, you have your reply :)
[15:09] <seb128> though uploading as a SRU is probably fine
[15:09] <seb128> but we might want to see if there are other g-c-c changes/fixes we want to bundle if we SRU it
[15:10] <jbicha> sure, thanks
[15:11] <seb128> np!
[15:14] <jbicha> I believe uploading that will allow libnss-myhostname to drop to universe
[15:25] <didrocks> Trevinho: there is quite some conflicts on the volume-slider bar if I want to rebase. Are you sure there will be a review if I rebase? I did rebase and fix conficts taking some days this cycle already for nothing, that's why I'm powndering
[15:45] <Laney> 24/04 16:43:43 -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [18.04.11]
[15:45] <Laney> :V V:
[15:49] <didrocks> !
[15:53] <willcooke> andyrock, where should I put bugs for the g-o-a u1 plugin?  (At least I think that's where it should go)
[15:53] <andyrock> willcooke: gnome-online-accounts (ubuntu)
[15:54] <willcooke> thx andyrock
[15:54] <andyrock> what bug?
[15:56] <kenvandine> didrocks, https://forum.snapcraft.io/t/auto-connection-of-gtk3-themes-icon-themes-and-sound-themes-interfaces/5118
[15:57] <willcooke> Laney, xnox - re: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939  if that can't be fixed, can we add a message to the screen to say "You need to reboot your machine" or something like that?
[15:57] <ubot5`> Ubuntu bug 1706939 in systemd (Ubuntu Bionic) "A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (22s / no limit)"" [Medium,Confirmed]
[15:57] <willcooke> I can reproduce that here easily
[15:58] <willcooke> so I can do debugging if that helps
[16:00] <Laney> willcooke: in a VM or on hardware?
[16:00] <didrocks> kenvandine: excellent, thanks!
[16:01] <willcooke> Laney, certainly hardware, will double check on a VM now
[16:04] <xnox> willcooke, if you can reproduce, that's good.
[16:04] <Trevinho> didrocks: I can review.... But you know I don't feel confident in pushing. Yesterday we were discussing this a bit on gnome hackers... They said to ping more. But I think we did. Didn't we?
[16:05] <xnox> willcooke, first after booting, what is actually "waiting/hanging", is that NetworkManager-wait-online?
[16:06] <xnox> imho that should not be enabled on the live-session.... as well, we cannot assume we will get networking up.
[16:06]  * xnox checks that
[16:06] <didrocks> Trevinho: we pinged at first every 3 days, and then weekly
[16:06] <didrocks> Trevinho: for a couple of months
[16:06] <didrocks> so, yeah, we did. Telling to ping more is hemf…
[16:07] <didrocks> Trevinho: ok, I'll rebase, probably going to take a day seeing the number of changes… (AGAIN)
[16:09] <willcooke> xnox, got some real hardware and a vm just about installed.  Should I do anything before I tell it to reboot?
[16:09] <willcooke> (of course, this time it will just work)
[16:11] <willcooke> andyrock, oh, sorry, missed your reply - it seems that if you have a g-o-a u1 account *already set up* then on the g-i-s livepatch setup screen the u1 plugin just craps out when you click go
[16:11] <willcooke> and takes you back to g-i-s
[16:11] <willcooke> but nothing happens
[16:12] <andyrock> we should show an error
[16:12] <andyrock> it's not a bug in gnome-online-accounts
[16:12] <willcooke> I need to do some tests to reproduce, but before I finish the install I want to see if I can help debug this non-rebooting problem
[16:12] <andyrock> but in gnome-initial-setup
[16:13] <xnox> willcooke, well, did you configure networking at all?
[16:13] <andyrock> willcooke: not sure how we should handle this
[16:13] <xnox> willcooke, e.g. i guess it's wifi only, and you didn't setup wifi on this thing? thus your system is offline.
[16:17] <Trevinho> didrocks: reversing the volume patches make them to apply properly, so you can just reuses this trick. At least so it was when I was cherry picked the change
[16:17] <willcooke> xnox, the real machine is wifi, and I did select the wifi network, did download updates etc etc.  The vm (think's that it) is on wired
[16:17] <willcooke> the wifi one is connected and online
[16:21] <didrocks> Trevinho: well, as there is some refactoring, I need to move the volume patches as well around
[16:22] <didrocks> but yeah, I was going for a git log on the file, and moving things around
[16:23] <Trevinho> didrocks: good... I'll bring this up in Cambridge again. And Jonas will also be at the sun sprint.
[16:23] <didrocks> Trevinho: great! Thanks :)
[16:24] <willcooke> and as expected, this time the real machine rebooted just fine
[16:24] <willcooke> bloody thing
[16:25] <xnox> willcooke, so. it depends how quick or slow you are.
[16:25] <willcooke> xnox, does rather smell like that
[16:26] <willcooke> xnox, I'll try again and do it as fast as I can
[16:26] <xnox> willcooke, depends if wifi configured within 30s or not, of starting NM-wait-online unit.
[16:26] <xnox> willcooke, can you try booting and waiting 45s before configure wifi; do install, reboot, see if it reboots (case A)
[16:26] <willcooke> xnox, ack will do
[16:27] <xnox> willcooke, boot wait 45s, configure wifi, change to tty3 do $ systemctl stop NetworkManager-wait-online.service; $ systemctl start NetworkManager-wait-online.service; $ systemctl is-system-running => ensure it is "running"; logout; complete install; reboot see if it reboots (case B)
[16:39] <tseliot> mvo: hey, are you done with the meeting?
[16:50] <willcooke> xnox, Case A: hangs.
[16:50] <willcooke> testing case B now
[16:51] <xnox> willcooke, did you use "install ubuntu / ubiquity-dm" or "try ubuntu / live session"?
[16:51] <xnox> willcooke, also was it EFI boot, or bios boot?
[16:51] <willcooke> EFI
[16:51] <willcooke> and erm, can't remember which option I selected, I can test again
[16:52] <willcooke> Pretty sure it was Try Ubuntu
[16:52] <willcooke> since that's the one at the top
[16:52] <xnox> ack, cause you did not see try-ubuntu, you had the EFI boot for it.
[16:53] <willcooke> Case B I'm doing with Try Ubuntu
[16:56] <xnox> ack
[17:02] <willcooke> grr. n-m thinks I'm offline but I'm not
[17:03] <willcooke> k, now its woken up
[17:14] <willcooke> xnox, Case B - also hangs.  But this time there is no text on the screen at all
[17:19] <xnox> willcooke, press enter?
[17:20] <xnox> willcooke, it should be displaying message "Please remove installation media and press enter" no?
[17:20] <xnox> willcooke, is it nvdia graphics? intel graphics?
[17:20] <xnox> willcooke, bring that thing to the office tommorow?
[17:24] <willcooke> xnox, intel.  If you think it can get fixed for release, I can come down tomorrow I think.  Lemme try it again, because n-m faffed about for a while before it knew I was really online
[17:25] <willcooke> and yes, press enter
[17:25] <willcooke> no ttys were alive
[17:25] <xnox> hm
[17:26] <willcooke> hrm. wtf. This time I booted off the USB stick, I've got the "Live session user" login at the greeter
[17:26] <willcooke> on the plus side, when I told it to shut down it asked me to remove the drive and hit enter, and that all worked.
[17:28] <willcooke> xnox, should it make a difference if I connect to the wifi via the n-m applet or via the installer itself?
[17:35] <xnox> willcooke, should not.
[18:09] <willcooke> Tried Case B again, still hanfs
[18:09] <willcooke> hangs
[18:22] <willcooke> xnox, bah, everything I try hangs.  I'm in the office on Thursday, but is it worth me coming down tomorrow as well?  I can do if you think it might be possible to get a fix in to the release
[18:25] <xnox> willcooke, tomorrow is better than thursday for hangs.
[18:25] <willcooke> :)
[18:25] <xnox> willcooke, thursday is better for bubbly and whiskey
[18:25] <willcooke> right, see you tomrrow then. and Thursday
[18:25] <willcooke> :)
[18:27] <xnox> willcooke, there is hotel, if you want to stay overnight?
[18:30] <willcooke> I'll need to clear it with the work boss and the home boss
[19:13] <willcooke> jbicha, how do I mark that I've added a bug to the release notes in LP?
[19:15] <willcooke> jbicha, ignore, worked it out
[19:19] <willcooke> andyrock, sorry for the delay on this: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1766694
[19:19] <ubot5`> Ubuntu bug 1766694 in gnome-online-accounts (Ubuntu) "If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install" [Medium,Confirmed]
[19:23] <andyrock> willcooke: I'll try a way to fix it, but I guess the priority is not high because why a u1 should be already configured at this point?
[19:24] <willcooke> yeah, it's an edge case I think
[19:24] <willcooke> and there's a work aroud
[19:24] <willcooke> if we can do the same thing as we do in Software & Updates, where it shows you the list of accounts and lets you choose one, that would be nice I think
[19:24] <willcooke> but yeah, I dont think people should have a u1 account set up already, even upgraders from 17.10 right?
[19:34] <jbicha> once livepatch is set up, g-i-s won't show the livepatch page
[19:36] <andyrock> willcooke: we could use this: https://github.com/CanonicalLtd/desktop-design/issues/62
[19:36] <ubot5-ng> CanonicalLtd bug 62 in desktop-design "Authentication in gnome-software using gnome-online-accounts" (comments: 14) [Priority: High, Open] - Assigned to matthewpaulthomas (Matthew Thomas)
[19:36] <ubot5`> bug 62 in Launchpad itself "Maintainers can add themselves to the CC: list too" [Medium,Invalid] https://launchpad.net/bugs/62
[19:37] <andyrock> https://github.com/CanonicalLtd/desktop-design/issues/62#issuecomment-382689517
[19:37] <andyrock> or....
[19:37] <andyrock> let me check if what I've in mind is possible
[19:38] <andyrock> willcooke: so we could do like that
[19:38] <andyrock> if an account is already setup and you try to add the same account
[19:38] <andyrock> we get the error GOA_ERROR_ACCOUNT_EXISTS
[19:39] <andyrock> in this case we ignore the error and we get the account manually
[19:40] <andyrock> or I can implement that design
[19:40] <andyrock> as you prefer
[19:43] <willcooke> andyrock, I think that since this is a fairly small edge case, we don't need to rush it.  If doing it properly per the designs on that github issue will solve this problem, we should spend the time working on that rather than a quick fix up.  wdyt?
[19:43] <andyrock> willcooke: I prefer to implement that design too
[19:44] <andyrock> let's wait for the design to be completed before we implement something that needs to be changed
[19:44] <andyrock> *to be changed later on
[19:44] <andyrock> the only thing that needs to be completed in that design is the "logout" option
[19:44] <willcooke> andyrock, coolio, thanks
[19:44] <andyrock> we don't need that in g-i-s
[19:45] <andyrock> but let's see what's the final design
[19:45] <willcooke> yeah sounds good
[20:13] <willcooke> ok, calling it a night
[20:13] <willcooke> laters d00dz
[20:14] <gQuigs> the new "welcome to ubuntu" is pretty neat :)
[20:17] <juliank> I updated my bionic a few minutes ago. Login takes a long time, like 10-20 seconds for shell UI to appear. There stuff from proposed is in there (shell, kernel, samba, perftools, base-files. modemmanger), not sure if that's the issue.
[20:17] <juliank> in a gnome session
[20:19] <juliank> anyone else seeing that?
[20:19] <juliank> login screen -> black/grey/depends - 10-20 seconds _> shell ui
[20:20] <juliank>      1min 1.401s gvfs-udisks2-volume-monitor.service
[20:20] <juliank> blame
[20:20] <juliank> hmm, could that be because I have a davfs2 mountpoint and am not connected to the network?
[20:21] <seb128> could be
[20:21] <juliank> though it's autofs
[20:22] <juliank> but apparently the autofs is mounting once that monitor starts
[20:22] <juliank> :(
[20:22] <seb128> it's a new issue since today? would be useful to know still if it you get it without those mounts
[20:23] <juliank> no, I think it just starts with a different hotspot
[20:23] <juliank> it's on Telekom_FON, and that requires one of those portla pages to login
[20:26] <juliank> should probably patch gvfs to ignore autofs mount points in monitoring
[20:26] <juliank> I had issues with that combination a lot
[20:26] <seb128> that seems worth an upstream report
[20:26] <seb128> on that note I reboot to test something and call it a day
[20:26] <seb128> night
[20:30] <juliank> JFTR: that's https://bugzilla.gnome.org/show_bug.cgi?id=771740
[20:30] <ubot5`> Gnome bug 771740 in udisks2 volume monitor "gvfs-udisks2-volume-monitor activates autofs mountpoints" [Normal,Reopened]
[20:30] <ubot5-ng> bugzilla.gnome.org bug 771740 in udisks2 volume monitor "gvfs-udisks2-volume-monitor activates autofs mountpoints" [Normal, Reopened] - Assigned to gvfs-maint
[20:30] <ubot5`> bug 771740 in webtrees "svn11392: Missing </div>" [High,Fix released] https://launchpad.net/bugs/771740
[20:30] <juliank> did the ubots just talk to each other?
[21:17] <sarnold> that's what that looks like :)