[08:18] <didrocks> good morning
[08:21] <jibel> Morning didrocks
[08:21] <didrocks> salut jibel
[08:21] <didrocks> I can give some hands on iso testing, it's the one in pending, correct?
[08:23] <jibel> didrocks, it's http://cdimage.ubuntu.com/bionic/daily-live/current/
[08:23] <didrocks> ok, already moved to current
[08:23]  * didrocks does
[08:51] <willcooke> morning all
[08:53] <didrocks> hey willcooke
[08:54] <jibel> Hi willcooke
[08:55] <willcooke> ca va?
[09:02] <Laney> lo
[09:07] <didrocks> hey Laney
[09:15] <willcooke> jibel, do you know, is the lack of "drums" when the live session starts (I'm doing the screen reader iso test) a known/reported issue?
[09:18] <willcooke> Ah, the drums are the signal for the installer starting, kk
[09:20]  * Laney boops at didrocks 
[09:25] <seb128> good morning desktopers
[09:25] <willcooke> hi seb128 Laney
[09:26] <seb128> hey willcooke
[09:26] <Laney> moin seb128 & willcooke
[09:26] <seb128> hey Laney :)
[09:27] <Laney> vots up
[09:30] <willcooke> jibel, where should this bug go:
[09:30] <willcooke> I did the install with the screenreader
[09:31] <willcooke> Before the install completed the screensaver kicked in, and so I was never told that the install finished.
[09:31] <willcooke> Also there is no indication that I'm looking at the lock screen from the screenreader, so I just sat there for 10 mins not knowing what was going on
[09:31] <willcooke> Is that a ubiquiuty bug?
[09:32] <willcooke> Simple fix would be to disable the screensaver when the install is running perhaps?
[09:32] <willcooke> (which I thought we did)
[09:43] <Laney> that'd be a ubiquity bug, it's supposed to disable that stuff, so I'd file it there
[09:44] <willcooke> Laney, thanks
[09:48] <Laney> https://git.launchpad.net/ubiquity/tree/ubiquity/frontend/gtk_ui.py#n567
[09:48] <Laney> don't think that is the right stuff to be using in shell
[09:49] <Laney> org.gnome.desktop.session idle-delay 0 maybe
[09:50] <willcooke> I'll try that
[09:59] <willcooke> ha
[09:59] <willcooke> It's python3 and my print statements broke it
[09:59] <willcooke> :D
[10:00] <Laney> /o\
[10:00] <Laney> maybe just gsettings set that before you install
[10:00] <willcooke> oh, nice idea
[10:00] <willcooke> well, I've fixed it now, so lemme see both ways
[10:01] <didrocks> willcooke: welcome to 2008, oh wait :)
[10:01] <willcooke> didrocks, as far as I'm concerned, anything that happened after 1997 is rubbish
[10:01] <didrocks> haha
[10:01] <Laney> new labour
[10:01] <didrocks> is that the correct time to mention ubuntu's creation date? :p
[10:02] <willcooke> I stand by my decision
[10:02] <willcooke> oh, my kids
[10:02] <willcooke> meh
[10:03] <didrocks> haha
[10:03] <didrocks> … "I still stand by my decision"
[10:03] <willcooke> :D
[10:03] <willcooke> indeed
[10:04] <didrocks> hum, starcraft was 1998 though
[10:04] <didrocks> maybe add this exception? ^
[10:06] <willcooke> haha
[10:13] <willcooke> welp, my changes to the code didnt work, but I probably did it wrong.
[10:13] <willcooke> I will try just setting that setting
[10:16] <seb128> willcooke, screensaver or screenlock is your issue?
[10:16] <willcooke> oh, right, screenlock
[10:16] <willcooke> erm
[10:16] <willcooke> well
[10:17] <willcooke> the screen goes blank, which is screensaver
[10:17] <willcooke> then it's "locked"
[10:17] <willcooke> so... both?
[10:23] <seb128> willcooke, you can try to 'gsettings set org.gnome.desktop.lockdown disable-lock-screen true'
[10:23] <Laney> this is different from screen blanking
[10:23] <willcooke> I did laney's suggestion of "org.gnome.desktop.session idle-delay 0" and so far that's working... just want to give it a few more mins
[10:24] <seb128> well, blanking isn't an issue is it?
[10:24] <seb128> imho it's fine if the screen goes in power saving over a long install
[10:25] <Laney> that's what the code was doing previously
[10:25] <seb128> as long as it resume fine/unlocked once you touch the match
[10:25] <Laney> if you want to revisit that decision, fine
[10:25] <seb128> *the mouse
[10:25] <Laney> but it broke due to a bug
[10:25] <Laney> not an intentional change
[10:25] <willcooke> I will have to test, but.. the problem was that if the screen blanked then the screenreader stopped reading things
[10:25] <willcooke> s/blanked/locked
[10:26] <Laney> fine by me if seb128 wants to take over owning the fix
[10:36] <willcooke> Happy that Laney's fix solves my problem
[10:42] <seb128> IRC in train is not the best :/
[10:42] <willcooke> :D
[10:43] <willcooke> seb128, L_aney's fix worked, testing your alternative now...
[10:43] <seb128> Laney, willcooke, unsure what's the intend of that code was, but yeah fine with me either way making it work as it used to work or look at what's supposed to do/what makes sense and do that
[10:43] <willcooke> my concern is that if the screen turns off then the screenreader will stop talking, and never tell me that the install finished
[10:45] <seb128> yeah, that's possible, I don't know if having screen turning off stops the reading
[10:47] <willcooke> k, with your change the lockscreen still came down and moving the mouse around gives no feedback at all
[10:48] <willcooke> clicking does nothnig
[10:48] <willcooke> so yeah, I think that's conclusive then
[10:49] <Laney> https://code.launchpad.net/~ubuntu-installer/ubiquity/+git/ubiquity/+merge/362788
[10:49] <Laney> try that
[10:50] <willcooke> How do I do that?  Just download and copy over the one which is on the USB stick?
[10:50] <Laney> you should be able to hax0r that diff in from a live session
[10:50] <Laney> and pro tip
[10:51] <Laney> `gsettings monitor org.gnome.desktop.session' in a terminal will show you any changes to keys in there
[10:51] <willcooke> ace!
[10:51] <willcooke> thanks
[10:51] <Laney> so you should see that do the thing straight after starting ubiquity
[10:55] <willcooke> Laney, do I ninja the one in /rofs (which I assume is read only, so probably not) or /usr/lib/ubiquity/blah
[10:56] <Laney> ya the second one
[10:56] <willcooke> tas
[10:56] <willcooke> ta
[10:56] <Laney> if you get lucky it might even work to apply the patch
[10:56] <willcooke> imma just over write it
[10:57] <Laney> like "cd /usr/lib/ubiquity; GET https://git.launchpad.net/ubiquity/patch/?id=9017a4dfc3b7ded03dec0312231f0f89d7101871 | sudo patch -p1" or something
[10:57] <Laney> don't forget the change to gsettings.py
[10:57] <willcooke> ah right
[10:59] <willcooke> # patch -p1 < screensaver.patch
[10:59] <willcooke> patching file ubiquity/frontend/gtk_ui.py
[10:59] <willcooke> Hunk #1 succeeded at 585 (offset -2 lines).
[10:59] <willcooke> Hunk #2 succeeded at 759 (offset -2 lines).
[10:59] <willcooke> patching file ubiquity/gsettings.py
[10:59] <willcooke> root@ubuntu:/usr/lib/ubiquity#
[10:59] <willcooke> \o/
[11:00] <Laney> you lucky thing
[11:01] <willcooke> boom!  idle-delay: 0
[11:02]  * Laney nods sagely
[11:03] <Laney> probably too late for .2, but if you file a bug we can SRU that for the next one
[11:03] <Laney> or we get lucky and .2 gets delayed ;-)
[11:04] <Laney> also needs to be reviewed of course
[11:15] <seb128> tkamppeter, hey, thanks for the modemmanager update! You forgot to Cc Mathieu on the email though I looks like?
[11:16] <seb128> tkamppeter, also it might make sense to open a bug on the Debian BTS or launchpad for the update, easier for comments/review?
[11:16] <willcooke> Laney, https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1814875
[11:16] <willcooke> thanks!
[13:05] <jibel> didrocks, I've something weird in a live session, it's like the chrome of the shell is missing, no background, no dock. Did you see that in a VM?
[13:05] <jibel> I thought I did something wrong but it's the second time I see this
[13:07] <didrocks> jibel: I didn't get that in vm at all, no chrome of the shell… like if it crashed?
[13:08] <didrocks> a*
[13:08] <jibel> not a crash because I've the top bar and it's reactive, I can click on the indicators for example
[13:08] <didrocks> but it doesn't have any transparent background?
[13:08] <didrocks> so it's there, but wrongly stacked?
[13:09] <jibel> no
[13:09] <jibel> no transparent bg
[13:09] <jibel> there are JS errors in the journal: TypeError: monitor is null
[13:09] <didrocks> ah :) could explain
[13:10] <didrocks> I don't have that in my journal, so that's one difference
[13:30] <willcooke> muhaha.  I used up the 50 MB of free data on the train wifi, and it has "limited my connection speed".  Jokes on them, IRC FTW!
[13:36] <ricotz> hey, is webkit2gtk 2.22 likely to be backported to Xenial/16.04?
[13:39] <mdeslaur> ricotz: can't, it needs a newer gcc
[13:45] <ricotz> mdeslaur, ah I see
[13:47] <doko> mdeslaur, ricotz: there is gcc-8 in bionic
[13:47] <doko> ahh, xenial. that has gcc-mozilla
[13:48] <ricotz> yeah, was about to mention the possible use of gcc-mozilla
[13:48] <mdeslaur> it has gcc-mozilla, but it would need a newer libstdc too
[13:48] <mdeslaur> and I don't know how to handle that
[13:48] <mdeslaur> firefox has a big compatibility shim to be able to build with a newer gcc but run with an older library
[13:51] <jbicha> upstream will bump other dependencies for webkit 2.26 (this September) since the 3-year Xenial clock is expiring https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy
[13:54] <xnox> hmmm... has anybody inherited libpam-freerdp in ubuntu?
[13:54] <xnox> do we care about maintaining it still?
[13:56] <mdeslaur> jbicha: "We support each Ubuntu LTS until one year after the release of the next Ubuntu LTS." didn't really turn out to be accurate anyway
[13:56] <jbicha> there is the big "except for gcc" disclaimer :(
[13:57] <mdeslaur> heh
[14:18] <doko> mdeslaur: don't they support building with static libstdc++? do you really need a libstdc++ of a newer major GCC version?
[14:18] <mdeslaur> doko: I don't know...it's a library too, what happens when something else loads it?
[14:19] <mdeslaur> doko: wouldn't that be problematic?
[14:21] <mdeslaur> someone would need to investigate this, but it's not high on our priority list
[14:26] <willcooke> seb128, I asked ondra to plug his iPhone X in to a Bionic machine.  He didnt get the "Lockdown" error and could browse his phone, but not his photos.  Which is a strange problem, because it should either work or not work.  He's running a beta firmware though, so could be that usbdmux etc need updating to support the new version.  Trying to find a spare iphone while I'm in the office
[14:27] <seb128> willcooke, thx for testing, and no it's not "either it works on not", browsing the photos and the "documents" section are different protocols/stacks
[14:31] <willcooke> ah
[14:53] <willcooke> jibel, didrocks - thank you for the iso testing :)
[14:53] <didrocks> yw!
[15:09] <jibel> willcooke, tested on hw and vm, no real issue found
[15:11] <willcooke> same
[15:11] <willcooke> seb128, got an iphone 6 (that's what stef had) and it works
[15:11] <willcooke> so I think it's new phones only
[15:12] <jibel> quick q, when can a desktop system with autologin enabled be considered up ?
[15:15] <willcooke> when the user session dbus service starts?
[15:15] <willcooke> we could configure an app to auto start too?
[15:20] <jibel> not sure about autostart, it starts very early
[15:25] <Laney> like when org.gnome.Shell gets on the bus, or maybe an autostart with X-GNOME-Autostart-Phase=Application?
[16:20] <Laney> TFW you do a complex search-replace in vim and it works first time
[17:05] <Laney> BAH
[17:05] <Laney> I was like "yes, I should do <thing> before uploading glib"
[17:06] <Laney> went to get a glass of water, came back, and now I can't remember what <thing> was
[17:06] <didrocks> and you forgot about <thing>?
[17:06] <didrocks> hehe, typical
[17:06] <didrocks> sure it was *very* important
[17:06] <didrocks> unsure if you can sleep before resolving this dangling pointer :p
[17:06] <willcooke> ha
[17:07] <willcooke> 2am:  AHAHAH!  I remember.  I'll do that first thing in the morning...
[17:07] <willcooke> 8am: hmmmmmmm
[17:07] <Laney> haha
[17:07] <Laney> i'm going to sleep with a notebook next to my head
[17:08] <Laney> YESSSSSSSSSSSSSSSSSSSSSS remembered
[17:08] <Laney> (breaks on gnome-keyring, upload fixed version)
[17:08] <didrocks> time to distract Laney
[17:09] <Laney> dunno about putting a breaks on glib though, seems like something that might break upgrade calculation
[17:09]  * Laney leaves it for now
[18:31] <willcooke> night all