[06:31] <Trevinho> morning...
[06:32] <Trevinho> Laney: I've been using latest version, but I agree it wasn't the case here to look at. But I tried that branch in kms and simply it will stop ubuntu running forever in kms, as  CanGraphical never goes to 'yes'.
[06:33] <Trevinho> so indeed I think is a lower level thing, just speaking of the effect here
[06:59] <duflu> Morning Trevinho
[07:02] <duflu> Wait. Trevinho is first online.
[07:02]  * duflu suspects he hasn't gone to bed yet
[07:02] <Trevinho> xD
[07:03] <Trevinho> ahaha, I did, but I had to drive a friend to the airport, so I had an early alarm :(
[07:18] <didrocks> good morning
[07:18] <Trevinho> hi didrocks
[07:18] <didrocks> hey Trevinho
[07:29] <duflu> Hello didrocks
[07:32] <didrocks> morning duflu
[07:36] <seb128> k, back!
[07:36] <seb128> hey didrocks Trevinho duflu
[07:36] <seb128> good morning desktopers
[07:37] <duflu> Hi seb128
[07:38] <seb128> how is everyone today?
[07:42] <oSoMoN> good morning desktoppers
[07:44] <didrocks> salut seb128, hey oSoMoN
[07:44] <acheronuk> LP: #1798005
[07:44] <acheronuk> can anyone check ubuntu main for that bug?
[07:44] <acheronuk> I have to walk out the door in a few mins
[07:45] <oSoMoN> salut didrocks, seb128
[07:45] <acheronuk> log: https://paste.ubuntu.com/p/kbzDFYpCBT/
[07:46] <seb128> lut oSoMoN; en forme ?
[07:46] <didrocks> seb128: on the "how is everyone" -> doing another yack shaving it seems :p
[07:46] <didrocks> and you?
[07:47] <oSoMoN> seb128, ça va, et toi?
[07:50] <duflu> Morning oSoMoN
[07:50] <seb128> oSoMoN, ça va bien!
[07:50] <seb128> didrocks, poor yack, winter is coming they need to keep warm :p the installer/screen reader one?
[07:50]  * duflu was briefly distracted by spider killing... Happy spring
[07:51] <didrocks> seb128: yeah, the whole a11y stack basically
[07:51] <seb128> :(
[07:51] <seb128> do you have a clue what's the issue is?
[07:51] <didrocks> yep
[07:51] <seb128> how do you ubiquity carry over the config to the installed system?
[07:51] <didrocks> it's using… a11y-profile-manager
[07:52] <seb128> lol
[07:52] <didrocks> which isn't seeded anymore
[07:52] <seb128> that explains :)
[07:52] <didrocks> same, isolinux is using a11y-profile-manager
[07:52] <seb128> shrug, I did revert some of that when I fixed other a11y problems in previous cycle
[07:52] <didrocks> which has a lot of vulneravities
[07:52] <seb128> I should have done a full revert to the codebase before that component was added :/
[07:52] <didrocks> like well-known names owned by root in /tmp
[07:52] <seb128> but a11y-profile-manager isn't used/on the iso anymore, is it?
[07:53] <didrocks> also, this thingy doesn't really know about GNOME
[07:53] <didrocks> it's not on the iso
[07:53] <didrocks> but isolinux set the profile you select based on it
[07:53] <seb128> ah :/
[07:53] <seb128> shrug, we should have reverted those changes
[07:53] <didrocks> and ubiquity, at install time, runs a hook which triggers it
[07:53] <seb128> that component was added not so long ago
[07:53] <didrocks> I like as well the usage of:
[07:53] <didrocks> function_witout_parameter() {
[07:54] <didrocks>   … read global variables …
[07:54] <didrocks> }
[07:54] <didrocks> …set global variables… with "if profile"
[07:54] <didrocks> function_witout_parameter()
[07:54] <didrocks> the whole code is like that :/
[08:05] <willcooke> morning
[08:06] <seb128> hey willcooke
[08:06] <didrocks> hey willcooke
[08:07] <seb128> at the office again today?
[08:13] <duflu> Morning willcooke
[08:15] <Laney> yo
[08:16] <seb128> hey Laney, how are you? enjoy the great London?
[08:16] <didrocks> morning Laney
[08:17] <seb128> and the citizenM?
[08:17] <willcooke> seb128, not yet, but might go in a little later on.  Got some meetings this mirning
[08:17] <seb128> willcooke, you didn't send the traditional "who is where this week" and "meeting reminder" btw :p
[08:17] <willcooke> darn
[08:18] <willcooke> I'll do it no
[08:18] <willcooke> now
[08:20] <Laney> seb128: it's good! nice cappuccino this morning :>
[08:20] <Laney> & hey didrocks willcooke
[08:20] <Laney> I forgot to do a status update
[08:24] <seb128> bad Laney :p
[08:33] <Laney> probably do it after we fix the installer that we broke :-)
[08:34] <seb128> haha
[08:34] <Laney> release traditions
[08:34] <seb128> with Didier we decided to stay away from doing late changes to fix a11y this cycle
[08:35] <seb128> the "onscreen reader is not enabled after installation if selected during install" is there since 17.10 :/ (casper still uses a11y-profile-manager than we killed from the iso/main when we switched to GNOME)
[08:35] <Trevinho> hi guyz
[08:35] <Laney> whoops!
[08:35] <Laney> good that it's not new though
[08:36] <didrocks> yeah, and we know what happens when we fix a11y in the installer, right?
[08:36] <didrocks> we can create a new tradition, but I'm not in :p
[08:38] <Laney> you could try elif finished_step == 'ubiquity.components.partman_commit':
[08:38] <Laney> WHAT
[08:38] <Laney> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1797861
[08:38] <Laney> that
[08:38] <Laney> guessing that's not covered by previous statements about a11y-thingy
[08:39] <didrocks> No, it's not related on that one
[08:39] <didrocks> (we are only talking about getting options from isolinux and setting them on the final installed system)
[08:41] <seb128> right, I'm going to give a try to that one
[08:43] <Laney> thanks!
[08:48] <didrocks> Laney: stupid question, but how do you trigger maybe-ubiquity using Boxes/kvm?
[08:48] <didrocks> Laney: I always have isolinux popping up
[08:49] <didrocks> and so, no way to have maybe-ubiquity
[08:51] <Laney> you can add it to the kernel cmdline
[08:51] <didrocks> do you have the exact syntax handy?
[08:51] <didrocks> otherwise, I can look
[08:52] <Laney> just add maybe-ubiquity somewhere in there
[08:52] <didrocks> I guess replacing only-ubiquity by maybe-ubiquity
[08:52] <didrocks> k! thanks Laney
[08:52] <didrocks> trying to reproduce the issue as well (can't when booting directly to a live session or install session)
[08:53] <didrocks> confirmed with maybe-ubiquity -> try ubuntu -> enable a11y -> start ubiquity
[08:54] <didrocks> indeed, no root apps are read by the screen reader under that config
[08:54] <seb128> so only when going through maybe ubiquity?
[08:54] <seb128> or "luck" on that boot?
[08:54] <didrocks> 100% on one try for both right now ;)
[08:54] <didrocks> doing more run to confirm or deny
[08:57] <didrocks> ah, have reproduced in only-ubiquity
[08:57] <seb128> I wonder if orca gets confused by having the same apps register 2 times or something
[08:57] <seb128> k, guess not then
[08:59] <didrocks> hum
[08:59] <didrocks> it's weird
[09:00] <didrocks> in that session, it "sometimes work"
[09:00] <didrocks> like selecting the language list, I get one on fourth selection read
[09:00] <didrocks> (even if I go very slowly)
[09:01] <seb128> I'm on the maybe-ubiquity screen and I've activated it but it fails to read anything e.g when I change language
[09:01] <didrocks> try keyboard
[09:02] <seb128> oh, yes, I was just doing that
[09:02] <didrocks> (I didn't try activating a11y on maybe-ubiquity itself)
[09:02] <didrocks> ah ok
[09:02] <didrocks> because on the fuzzy results before, I got 100% working with keyboard, but not mouse…
[09:02] <seb128> so yeah, I picked "try ubuntu"
[09:02] <seb128> right, same here
[09:02] <didrocks> something is fishy
[09:02] <seb128> I was trying the mouse
[09:03] <seb128> well, keyboard is what makes sense
[09:03] <didrocks> indeed
[09:03] <seb128> blind users can probably not use the mouse
[09:03] <didrocks> but still, don't really like that :)
[09:03] <seb128> yeah
[09:03] <didrocks> it's going to hit us back because we don't understand it fully
[09:04] <seb128> so the reader is working on the live session for me on first try going through maybe-ubiquity
[09:04] <didrocks> doesn't for me on this second try
[09:05] <didrocks> maybe-ubiquity -> enabled a11y -> live session -> (a11y enabled already) ubiquity -> nothing (nor mouse or keyboard)
[09:05] <seb128> k, try 2
[09:06] <seb128> my first one was
[09:06] <seb128> "wait to boot to maybe-ubiquity -> alt-super-S, it reads something -> click "try" -> start ubiquity from the launcher -> it reads the ubiquity dialog buttons ("continuer")
[09:07] <didrocks> I started it from the desktop icon
[09:07] <didrocks> but apart from that, same…
[09:07] <didrocks> you selected french on maybe-ubiquity?
[09:07] <seb128> yes
[09:07] <didrocks> let's try
[09:08] <didrocks> waow
[09:08] <didrocks> it reads the list in maybe-ubiquity
[09:08] <didrocks> but with an initial lag of at least 5s
[09:09] <didrocks> but then, nothing in live session…
[09:10] <didrocks> we should call release week "look at a11y installer issue week"
[09:12] <seb128> second try, working as well in live
[09:12] <seb128> "continuer button" is spoken when I start ubiquity once in live
[09:12] <didrocks> could be racy, but how come…
[09:12] <didrocks> and if you sudo gedit?
[09:12] <seb128> does it work for you if you stop/start the screenreader?
[09:12] <seb128> any error in the journal?
[09:13] <seb128> sudo gedit speaks "document sans titre...3
[09:13] <didrocks> nothing failing looking for a11y in the journal
[09:13] <didrocks> I tried to stop/start it again
[09:13] <didrocks> not better
[09:13] <seb128> you have sound if you use aplay or something?
[09:13] <seb128> or the test audio from g-c-c?
[09:13] <didrocks> oh a11y is working
[09:13] <didrocks> for everything which !root
[09:13] <seb128> :(
[09:14] <didrocks> orca has a stacktrace
[09:14] <didrocks> on shutdown
[09:14] <didrocks> but nothing when starting…
[09:14] <didrocks> yeah, all windows which aren't root are working
[09:15] <didrocks> let me confirm again (I'm sure I've done that) that booting a live session right away works
[09:16] <didrocks> yeah
[09:16] <didrocks> apps as root works in that case
[09:16] <didrocks> nice sudo apt install pastebinit -> plymouth screen -> exit
[09:17] <didrocks> it switched vt!
[09:17] <didrocks> but the session is still running
[09:17] <didrocks> http://paste.ubuntu.com/p/g97MHJdCYr/ <- working env
[09:17] <didrocks> let's reboot in maybe-ubiquity + session switch and see
[09:18] <seb128> wfm on another try :/
[09:19] <didrocks> virtualbox, not kvm?
[09:19] <Trevinho> sooooooo (Laney), for what I think is also willcooke's issue I think that more than gdm itself, is the way gdm is started. So right now we start it once we've a tty. and for the daemon is probably fine. Problem is that that point there might be no drm card (yet).
[09:19] <Trevinho> A way to fix this is changing gdm3.service so that it wants a drm card / fb to be there
[09:20] <didrocks> seb128: ah, even better, in that session, no a11y working at all…
[09:20] <seb128> :(
[09:20] <seb128> didrocks, right, virtualbox here
[09:21] <didrocks> http://paste.ubuntu.com/p/X46nG3RPFj/ -> failing session (after maybe-ubiquity, enable a11y, try ubuntu)
[09:21] <Trevinho> but not sure if this is a general rule... As in pure fb scenarios I guess X would start without any FB device in... So maybe gdm should wait for a drm device if trying with wayland, while on X could go without.. .But again even X should wait if there's a fb but there's no X driver for it... So quite a mess :)
[09:22] <didrocks> nothing fancy diffing the logs, apart from IDs changing…
[09:22] <seb128> :/
[09:22] <didrocks> ah!
[09:22] <didrocks> oct. 16 09:22:28 ubuntu orca-autostart.desktop[8065]: Une autre instance du lecteur d’écran est déjà lancée pour cette session.
[09:22] <didrocks> oct. 16 09:22:28 ubuntu orca-autostart.desktop[8065]: Lancez « orca --replace » pour remplacer ce processus par un nouveau.
[09:22] <didrocks> in that session
[09:22] <seb128> ah!
[09:22] <didrocks> if I disable/reenable screen reader
[09:23] <didrocks> maybe there is a race + something else with sudo?
[09:23] <seb128> another bug I guess
[09:23] <seb128> the desactivate not working
[09:23] <didrocks> yeah
[09:23] <didrocks> orca is 4 minutes old
[09:23] <didrocks> under ubuntu user
[09:23] <didrocks> no log on shutdown request though :/
[09:23] <seb128> works everytime here/on virtualbox
[09:24] <Trevinho> willcooke: your laptop is still with Andrea?
[09:24] <seb128> I need to step out for early lunch but I try with kvm once I'm back
[09:24] <seb128> bbl
[09:24] <didrocks> seb128: enjoy!
[09:24] <seb128> thx
[09:28] <willcooke> Trevinho, hey, yes
[09:28] <willcooke> unless he sold it
[09:28] <Trevinho> ahaha
[09:28] <Trevinho> you know... you trusted an Italian..
[09:29] <willcooke> :)
[09:29] <willcooke> With the money he got, he could have bought a milkshake
[09:29] <willcooke> Trevinho, reading backscroll
[09:32] <didrocks> seb128: second time I'm reproducing the "no a11y working at all", I have to kill orca, then I'm in the "orca works with all but root apps"
[09:32] <Trevinho> in general I think for making things working in any normal scenario, I think there are multiple options... 1) udev rules + systemd service updates for gdm waiting drm cards (what I've done locally, seems to work properly) | 2) making gdm daemon to monitor udev so that if a main drm card is added it tries to create again a display. As right now it fires once, then if it fails, it just doesn't try again.
[09:32] <willcooke> Trevinho, yeah, so the problem with waiting for a drm device is, as you said, there might not be one in headless mode
[09:33] <willcooke> Trevinho, from ISO testing some of the flavours I think that some of them do retry the greeter later on
[09:33] <willcooke> If we could make the systemd service retry, say, three times before giving up, would that do it?
[09:34] <Trevinho> willcooke: the daemon itself starts properly. it's more a gnome-session thing of not retrying again I think.
[09:34] <willcooke> ah, kk
[09:34] <willcooke> so let's just put the sleep statement back in again then
[09:34] <Trevinho> willcooke: as gdm starts the daemon, then it launches various subdaemons
[09:35] <willcooke> got ya
[09:35] <Trevinho> well it's better to use udev anyway...
[09:35] <Trevinho> like wait for a drm for time, if it doesn't work, then just try.
[09:35] <willcooke> I was joking about the sleep statement btw :)  Just in case...
[09:35] <Trevinho> this is the faster and easier fix
[09:35] <willcooke> sounds good
[09:36] <Trevinho> well, like having a "max timeout" for headless versions where there might be weird setups with no dri cards, but... well for 99% of ubuntu targets things should actually work
[09:36] <willcooke> we should get jibel to confirm that it will work for his automated testing. He'll be in London in a few hours
[10:13] <Trevinho> sooo... eventually I think our main issue is this one: loginctl starts as soon as we've a fb... but having a fb doesn't always mean we've a gfx (dri) card ready to go. So it starts and then fails... CanGraphical doesn't seem to reflect this properly even (as because CanGraphical if is connected to `master-of-seat`, that one is also not safe to use since might be there when fb is set, not when also dri card is there). So for a proper fix
[10:13] <Trevinho> we've multiple possibilities, for a fix for release I'd go with udev + systemd checks.
[10:33] <willcooke> Trevinho, +1
[10:33]  * willcooke -> train
[10:51] <popey> Just did an install of cosmic daily 20181016 in virtualbox with 3d acceleration on and ubiquity died bug 1798065
[10:52] <popey> I suspect this may be a dupe of bug 1798050
[10:52] <popey> I switched off 3d acceleration in virtualbox and the install seems to be progressing further.
[11:11] <willcooke> popey, can you tell me the specs of the VM?  Especially RAM and VRAM
[11:11] <willcooke> Doing a quick test from the train of some old ISOs I have
[11:11] <willcooke> see if I can easily find when it broke
[11:11] <popey> willcooke: 4GB RAM, 128MB VRAM
[11:11] <willcooke> thx
[11:12] <willcooke> and did you do a "try" or go direct to install?
[11:12] <popey> just install
[11:12] <willcooke> ack
[11:12] <popey> i just left it till i got the gui with two buttons
[11:14] <willcooke> popey, and was it on a cosmic host?
[11:15] <willcooke> i.e. cosmic on cosmic
[11:15] <willcooke> yes, looks like it was
[11:15] <willcooke> RTFB
[11:15] <popey> no
[11:15] <willcooke> oh
[11:15] <popey> cosmic vm on bionic host
[11:16] <willcooke> ah, ok, that data was from inside the VM
[11:16] <popey> yeah, i filed the bug in the vm using the popup from ubiquity
[11:16] <seb128> popey, was it a one time thing? or can you reproduce with the same setup?
[11:17] <seb128> also ubiquity issues at this point of the cycle might be worth raising in #ubuntu-release
[11:17] <popey> i will attempt to reproduce it now
[11:17] <seb128> thx
[11:18] <willcooke> my ISO from Friday worked here
[11:18] <seb128> Oct 16 10:38:06 ubuntu ubiquity: AssertionError: Failed to mount the target: /target
[11:19] <seb128> it's similar to bug #1798050 reported earlier
[11:19] <willcooke> I'll retry using the existing diks
[11:19] <seb128> or bug #1798005
[11:19] <seb128> ah
[11:19] <seb128> ^
[11:19] <willcooke> yeah
[11:19] <seb128> willcooke, popey, ^ that's the regression L_aney was mention earlier this morning
[11:19] <seb128> so "known issue/being worked on" it seems
[11:20] <willcooke> woot
[11:20] <willcooke> thanks seb128 popey
[11:20] <willcooke> I'll be in the office in 30 mins, so will report back to the channel
[11:20] <popey> didnt do it on this run
[11:20] <popey> thanks seb128
[11:21] <seb128> popey, it's racy so pretty sure it's that issue, looks like L_aney as a candidate fix in https://git.launchpad.net/ubiquity/commit/?id=d784958
[11:21] <popey> \o/
[11:21] <popey> great success
[11:25] <Laney> yeah feel free to try it if you want
[11:25] <Laney> you can patch that from the live session
[12:07] <Trevinho> so... I'm going with the conditional-wait workaround for gdm now, I think is saner (wait drm a bit, otherwise continue how it is). For upstream i've various other ideas. Might be both systemd that would need to do a similar thing or gdm instead to be more robust. As Systemd right now advertize a CanGraphical as soon a there's a /dev/fb0 around, but this is not true if the drm device takes some time to initialize after the fb. And so when
[12:07] <Trevinho> the drmdevice has been finally added it can't advertize again a CanGraphical change. That's why the fix propsed upstream might help but doesn't fix the problem in all the cases.
[12:07] <Trevinho> probably lunch first though :P
[12:21] <dgadomski> hi
[12:21] <willcooke> hi dgadomski
[12:21] <jbicha> Trevinho: btw did you see my comment in LP: #1796822 that I get the corrupted screen when I enable autologin
[12:21] <dgadomski> could anybody please take a look at the merge request for bug #1755490?
[12:22] <Trevinho> jbicha: mh didn't see no, but I think it all might be related to the same issue
[12:22] <willcooke> dgadomski, is that especially urgent?
[12:23] <jbicha> yes, I'm commenting because I think there were some indications we fixed the problem but that one still is easily reproducible for me
[12:23] <Trevinho> jbicha: run with this systemd unity (add a .service and enable it):
[12:23] <Trevinho> https://www.irccloud.com/pastebin/6gNvcnai/
[12:23] <Trevinho> attach the log after that please
[12:23] <dgadomski> willcooke: nope, not super urgent, it's just there for some time
[12:24] <willcooke> dgadomski, oki, I propose that we look at it after release then, if that's good for you
[12:24] <dgadomski> willcooke: yep, completely, thanks
[12:24] <willcooke> cool
[12:24] <willcooke> I'll add a trello card
[12:26] <Trevinho> I mean all these bugs are speed dependent, and because gdm starts too early basically :)
[12:29] <jbicha> Trevinho: log attached to the bug
[12:39] <Trevinho> thanks
[12:40] <Trevinho> jbicha: was udevadm service running?
[12:40] <Trevinho> jbicha: did you systemctl enable it?
[12:45] <jbicha> Trevinho: ok, new attachment, thanks!
[12:59] <Trevinho> ta
[13:00] <Trevinho> seems to be the same issue
[13:29] <Nafallo> hmm. remind me what URL the meeting updates lives on again? :-)
[13:29] <Nafallo> never mind. found it :-)
[13:30] <willcooke> sorry folks
[13:30] <willcooke> bear with me
[13:30] <willcooke> unprepared
[13:31] <willcooke> #startmeeting Desktop Team Weekly Meeting 16 October 2018
[13:31] <meetingology> Meeting started Tue Oct 16 13:31:07 2018 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:31] <meetingology> Available commands: action commands idea info link nick
[13:31] <willcooke> Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out)
[13:31] <didrocks> hey!
[13:31] <Trevinho> o/
[13:31] <heber> o/
[13:31] <seb128> hey
[13:31] <jibel> hi o/
[13:31] <oSoMoN> hey
[13:31] <Nafallo> hi there
[13:31] <willcooke> Laney, andyrock and jibel are here in London
[13:32] <willcooke> Everyone is very busy with release work, so let's keep this short
[13:32] <willcooke> We haven't had chance to review the rls bugs, so we will have to do it live
[13:33] <willcooke> Tracking first:  http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html
[13:33] <willcooke> http://launchpad.net/bugs/1794280
[13:33] <willcooke> We're working on that one, happy its in hand.  Could have a fix/work around soon
[13:33] <willcooke> http://launchpad.net/bugs/1796822
[13:34] <willcooke> Initial indications are that this is the same bug
[13:34] <willcooke> Should know for sure soon
[13:34] <willcooke> http://launchpad.net/bugs/1794951
[13:34] <willcooke> Ken will look at that tomorrow.  Can be fixed with out affecting release
[13:34] <willcooke> http://launchpad.net/bugs/1797543
[13:34] <willcooke> fixed
[13:34] <willcooke> http://launchpad.net/bugs/1796056
[13:35] <willcooke> I think we've worked around that mostly.  tjaalton anything more needed there ^ ?
[13:36] <willcooke> EOL
[13:36] <tjaalton> willcooke: nope
[13:36] <seb128> there is an upstream patch that has been merged to error out "properly", unsure if that's good enough though if the erroring out still means screwed systems?
[13:37] <tjaalton> upstream released 1.20.2 with that, too late for cosmic anyway
[13:37] <willcooke> tjaalton, will it get an SRU?
[13:37] <tjaalton> willcooke: maybe
[13:37] <willcooke> FWIW I havent seen that specific bug in recent testing, so I think all the other fixes we've done are masking it
[13:38] <seb128> yeah, probably not worth targetting at this point
[13:38] <willcooke> ok, lets untarget
[13:38] <willcooke> tjaalton ok with you?
[13:38] <tjaalton> sure
[13:38] <willcooke> oki, I will do that in a mo
[13:38] <willcooke> Incoming:
[13:38] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html
[13:39] <willcooke> http://launchpad.net/bugs/1797543
[13:39] <willcooke> fixed
[13:39] <willcooke> http://launchpad.net/bugs/1796548
[13:39] <willcooke> Feature not a bug
[13:39] <willcooke> +1s to reject?
[13:39] <Trevinho> yep
[13:39] <didrocks> yep, changed on purpose
[13:40] <willcooke> https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1796550
[13:41] <willcooke> not a release blocker IMO.  There is a simple fix, but in the spirit of this meeting, notfixing?
[13:41] <seb128> that sounds like a good SRU
[13:41] <seb128> right
[13:41] <didrocks> +1
[13:41] <seb128> I'm going to add it to my SRU list
[13:41] <didrocks> (and don't impact everyone btw, just tried)
[13:42] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791574
[13:42] <Trevinho> sru too
[13:42] <willcooke> ack
[13:42] <Trevinho> seb128: list that too plz
[13:42] <seb128> ?
[13:42] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791574
[13:42] <didrocks> (on the SRU list, I guess)
[13:42] <Trevinho> [not if it's "yours"]
[13:43] <willcooke> not a release blocker for 1791574
[13:43] <seb128> ah, SRU seems fine
[13:43] <seb128> if that's the question
[13:43] <seb128> dunno what you mean by "list that too"
[13:44] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1770725
[13:44] <willcooke> Since wayland is not the default, I say -1 for rls
[13:44] <seb128> rls-notfix since it's waylabd
[13:44] <willcooke> done
[13:45] <willcooke> ok, that was more like it
[13:45] <willcooke> :)
[13:45] <seb128> did we skip over mais il était pas trop ouvert, sa réponse ?
[13:45] <seb128> wth?
[13:45] <Trevinho> seb128: add that to the list (if it's a team sru list) I meant
[13:45] <seb128> https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1789356
[13:45] <didrocks> doesn't seem a release blocker, I can have a look for SRU though for bionic-cosmic-eye-users ;)
[13:45] <willcooke> ok, I already notfixing that one
[13:45] <seb128> thx
[13:45] <willcooke> might have been a copy & paste error
[13:46] <willcooke> any more on the rls bugs?
[13:46] <didrocks> we had enough of them :p
[13:46] <willcooke> #topic AOB
[13:46] <willcooke> Bon chance for release all
[13:46] <jbicha> please update https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes
[13:46] <willcooke> Oh, good call jbicha
[13:46] <willcooke> I'll take a look at that this afternoon
[13:47] <willcooke> any more?
[13:47] <jbicha> if you worked on cool features this cycle, please do add it to the Release Notes so people know about it :)
[13:48] <willcooke> I have some stuff semi prepared, I can add it
[13:48] <willcooke> which should call out most of it
[13:48] <willcooke> ok, ending meeting then
[13:48] <willcooke> thanks
[13:48] <didrocks> thx!
[13:49] <seb128> thx!
[13:49] <willcooke> #endmeeting
[13:49] <meetingology> Meeting ended Tue Oct 16 13:49:33 2018 UTC.
[13:49] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-10-16-13.31.moin.txt
[13:49] <willcooke> 19 mins
[13:50] <oSoMoN> thanks
[13:51] <tkamppeter> Sorry I am late, have posted my week (Mentor Summit) now.
[13:52] <jbicha> tkamppeter: hi, I blogged about https://jeremy.bicha.net/2018/10/14/google-cloud-print-in-ubuntu/
[13:54] <seb128> jbicha, that only works in libreoffice no?
[13:54] <jbicha> seb128: it works in other apps
[13:54] <seb128> or how does it integrate to the gtk print dialog?
[13:54] <jbicha> yes
[13:55] <seb128> "how"
[13:55] <jbicha> dunno :)
[13:55] <seb128> I mean gtk doesn't use the lib
[13:55] <jbicha> magic?
[13:55] <tkamppeter> Jbicha, this is really strange, as the part for the GTK print dialog to support the Common Print Dialog Backends (cpdb-...) is not finished yet.
[13:55] <seb128> are you sure it's just not gnome-online-accounts doing it?
[13:55] <seb128> like GNOME upstream feature
[13:56] <jbicha> hmm
[13:56] <seb128> https://bugzilla.gnome.org/show_bug.cgi?id=723368
[13:56] <jbicha> oh, I guess it is GOA not gcp after all
[13:56] <jbicha> sorry
[13:57] <seb128> that makes more sense :)
[13:57] <jbicha> maybe I should have checked with Till before posting
[13:57] <tkamppeter> I have a GSoC 2018 (the GSoC which ended in August of this year) student who was supposed to do the GTK dialog support, but he did not finish and wants to finish after the summer. I did not yet get this work.
[13:57] <jbicha> oh
[13:58] <jbicha> I don't have a printer actually. less headache 😉
[13:58] <seb128> tkamppeter, btw what's the status of the issue that is/Was blocking https://bugs.launchpad.net/ubuntu/+source/cpdb-libs/+bug/1747759 ?
[13:58] <jbicha> is it only LibreOffice that would support that then?
[13:58] <tkamppeter> jbicha, by the way, can you compare my user name here in the IRC with the name as you have written in the blog?
[13:59] <jbicha> sure, sorry about that
[14:00] <tkamppeter> seb128, not yet solved I must return to get this stuff running on the porter box.
[14:00] <tkamppeter> at least I have a way again to log into the porter box.
[14:01] <tkamppeter> seb128, next problem is that I cannot simply run stuff as root or at least privileged printing (lpadmin group) user.
[14:01] <tkamppeter> jbicha, yes, only LO currently, the rest I hope to get together for the next release.
[14:03] <juliank> Heya desktop folks, I'm seeing gnome-software prompting me for system updates (reboot&upgrade) on cosmic recently. That seems a bit wrong given that we use update-manager?
[14:03] <seb128> juliank, https://launchpad.net/ubuntu/+source/gnome-software/3.30.2-0ubuntu4 ?
[14:04] <juliank> ah, thanks, seems I'm out of date
[14:04] <seb128> np
[14:08] <jbicha> tkamppeter: I updated my post. I hope it's more accurate now
[14:10] <tkamppeter> jbicha,  and the GSoC where these projects were done is 2017, not 2007 (I actually started in 2008 with GSoC, and also it is not that easy to integrate 10-year old software into our GUIs).
[14:12] <jbicha> ok
[14:28] <seb128> on screenreader issues, https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1797868
[16:48] <willcooke> desktoppers I've updated the release notes with a bullet list.  Please add to and expand where you can:  https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes
[16:50] <seb128> k
[19:12] <Laney> gggggggdmmmmmmmmmmmmmmmmmmmmm
[19:49] <Laney> Trevinho: it's up
[19:49] <Trevinho> Laney: great, thanks a lot
[19:50] <willcooke> thanks Trevinho Laney