[02:25] <tsimonq2> JanC: That's why I figured he should make his case to an AA :)
[06:23] <didrocks> good morning
[06:36] <duflu> Morning didrocks
[06:43] <duflu> Also morning seb128
[06:47] <didrocks> hey duflu
[07:27] <seb128> hey didrocks duflu
[07:27] <seb128> (re)good morning desktopers
[07:27] <jamesh> hi seb128, didrocks
[07:28] <seb128> hey jamesh, how are you? did you recover from the conf & trip back already?
[07:28] <didrocks> hey seb128 & jamesh
[07:29] <jamesh> seb128: yes.  It took a while to get out of the airport on Friday night, since it looked like there were two A380's worth of passengers trying to get through immigration at once
[07:29] <jamesh> plus a flight from Bali
[07:30] <seb128> :/
[07:31] <duflu> Surely having a flight from Bali just coming in is a given :)
[07:33] <seb128> hey duflu, how are you?
[07:34] <duflu> seb128, was going well, then unwell. Now OK. You?
[07:34] <seb128> I'm fine, just day/week just started though
[07:34] <seb128> sorry you felt unwell, good that you are back to "ok" at least
[07:35] <duflu> I had some very enjoyable food, but possibly something I can't eat. Don't know. So just went and grabbed a pile of boring vegetables
[07:36] <didrocks> :/
[07:37] <duflu> Oh, good news though! A significant CPU reducing fix just landed in mutter
[07:40] <duflu> seb128, also I think (as suggested by Marco) that we will need to ignore my suggested 18.04.1 fixes. Because the important one hasn't been finalized and merged upstream yet, and we are powerless to speed it up. The only option would be to take the unverified patch
[07:41] <seb128> right, it feels a bit late to "force" that in the .1 now
[07:41] <duflu> It's a shame because I had hoped 18.04.1 would solve all the can't boot/login bugs
[07:42] <seb128> but on the other side that's not important to have on the iso, upgraders (& new installers who apply updates) are going to get the fix once we SRU it
[07:42] <Trevinho> Morning...
[07:42] <seb128> good morning Trevinho
[07:42] <duflu> Hi Trevinho
[07:42] <Trevinho> Hi duflu and seb128
[07:42] <seb128> Trevinho, how are you? had a good w.e?
[07:42] <duflu> seb128, I'm still concerned about those users who never get a login screen. Some proportion of them will give up and not bother to find out the workaround
[07:43] <seb128> duflu, that's right, those class of issues are annoying :/
[07:43] <Trevinho> seb128: great yes... Exploring the the coasts here, awesome
[07:43] <seb128> hopefully that's not of hardware concerned?
[07:43] <seb128> Trevinho, where are you now?
[07:44] <Trevinho> San José, a bit north of Almería
[07:45] <Trevinho> duflu: I agree that's a bad thing... We can still sru and most people will get it working anyway if choosing to update at install
[07:45] <duflu> I forget normal people do that :)
[07:45] <Trevinho> It's a shame, but since the fix isn't exactly stable yet, it's a bit risky
[07:46] <didrocks> hey Trevinho
[07:46] <Trevinho> Well that's the default no?
[07:46] <Trevinho> Hi Didier
[07:46] <duflu> Not if you don't enter a wifi password
[07:47] <didrocks> Trevinho: duflu: no, they don't, because updates aren't installed, just downloaded
[07:47] <didrocks> I was surprised as well when discovering that before going to GUADEC (like, "why don't people are running latest ubuntu-report in general?")
[07:47] <Trevinho> Mh...
[07:48] <didrocks> you just end up with the .deb in /var/cache/apt/archives
[07:48] <didrocks> I guess only security updates are installed right away
[07:51] <duflu> It was a while ago, but also worth noting 18.04.1 will solve the QHD/cairo/ubiquity installer crash
[07:52] <seb128> right
[07:52] <Trevinho> I see... Well, if we can get the guy to finaliza the fix and jonas to ack it quickly we might still have a small window of time, but otherwise... duflu if you're confident with it feel free to prepare a package, with the patch. Personally I don't know enough of that code to ack
[07:52] <seb128> didrocks, security updates are not applied before first boot either, are they?
[07:53] <didrocks> seb128: I don't know when they are applied, I thought I've seen "installing updates" in ubiquity, but I didn't check at the time assuming all updates were installed
[07:53] <duflu> Trevinho, yeah I don't think there's anyone who knows the code for my fix. That's why it stayed broken for so many years
[07:53] <didrocks> maybe it's just wrongly worded or my memory playing with me
[07:53] <seb128> ubiquity is confusing :)
[07:53] <didrocks> +1 ;)
[07:55] <tsimonq2> *cough* Calamares *cough* *cough* ;) ;)
[08:02] <Laney> guten morgen!
[08:02] <duflu> Hi Laney
[08:02]  * tsimonq2 waves to Laney 
[08:04] <didrocks> hey Laney
[08:08] <Laney> hey duflu tsimonq2 didrocks
[08:08] <Laney> what's up
[08:09] <Laney> didrocks: well done :->
[08:10] <seb128> hey Laney, happy monday!
[08:10] <Laney> hey seb128
[08:10] <Laney> and to you!
[08:12] <didrocks> Laney: pffffff :p
[08:12] <Trevinho> Laney: hi Ilenio (I think could be your name... Like it? 😅)
[08:13] <oSoMoN> good morning desktoppers
[08:14] <didrocks> salut oSoMoN, ça va ?
[08:15] <Laney> Trevinho: are you trying to Trevinhoise me?!?!?!
[08:15] <seb128> salut oSoMoN, en forme ? bon w.e ?
[08:15] <duflu> Morning oSoMoN
[08:16] <oSoMoN> didrocks, seb128: ça va bien, et vous?
[08:16] <oSoMoN> hey duflu, Laney
[08:16] <didrocks> oSoMoN: ça va bien, il fait beau et pas très chaud, on peut enfin faire tomber la température ici ;)
[08:17] <seb128> oSoMoN, nickel, un peu fatigué, ça va que c'est lundi et que je peux me reposer tranquillement à l'ordi :)
[08:19] <oSoMoN> seb128, héhé, pareil :)
[08:26] <Trevinho> Laney: hell yes 😋😘
[08:27] <Laney> 😈
[08:51] <GunnarHj> Good morning all!
[08:51] <GunnarHj> seb128: Can you please give me a hand as an archive admin with https://launchpad.net/ubuntu/+source/freshplayerplugin/0.3.9-0ubuntu1 . Build failure on s390x, but there is really no need to build on that arch.
[09:11] <seb128> hey GunnarHj
[09:11] <seb128> GunnarHj, well "no need" is a bit vague, things should be built on all supported archs unless there is a good reason not to
[09:11] <seb128> in which case it's not "no need to" but "can't because <reason>"
[09:15] <Trevinho> popey: hey, I'm notcing even more issues in auto-connect of some snap interfaces (icons and themes) on snap refresh (remember the issue with fonts in telegram)? Same with the theming. Is there an issue to track it?
[09:16] <popey> Trevinho: heya, not that I'm aware of. Might want to file a bug in snapd
[09:17] <Trevinho> popey: is that happening in other snaps too?
[09:17] <GunnarHj> seb128: browser-plugin-freshplayer-pepperflash is a wrapper to make use of the PPAPI Flash plugin on Firefox. PPAPI is available on Ubuntu via adobe-flashplutin (build only on amd64 and i386) and pepperflashplugin-nonfree (built only on amd64).
[09:17] <popey> I haven't seen it for a while Trevinho
[09:18] <seb128> GunnarHj, but the url you gave shows it built on e.g armhf
[09:18] <seb128> GunnarHj, in any case if the package does only make sense on some archs then the debian/control should list those rather than use "all"
[09:18] <GunnarHj> seb128: True, it has been that way for a long time (and it worked up to bionic) but actually not needed.
[09:18] <Trevinho> popey: I've noticed that adding the usage of the gtk-themes to the snap, we end up on the same issue after few refreshes
[09:18] <Trevinho> well now for theming
[09:19] <Trevinho> popey: if you're on telegram-edge, if you see the X cursor back, that a sign
[09:19] <seb128> GunnarHj, again "not needed" is different from "can't work"
[09:19] <popey> ugh, I'd definitely file an issue then
[09:19] <seb128> GunnarHj, it's "not needed" to build firefox on amd64
[09:19] <seb128> but it's preferable to have it
[09:23] <GunnarHj> seb128: I suppose we are talking about "can't work" in this case, for the reason I mention. Replacing "any" with "amd64,i386" would be possible, of course, but it's a sponsored upload. So I thought it might be easiest in this case to just let it through...
[09:27] <GunnarHj> seb128: The version in cosmic-release has the same build failure on s390x, btw.
[09:27] <czajkowski> morning
[09:28] <czajkowski> popey: would a latest update have removed all my logins from snap applications I use such as telegram and skype by any chance?
[09:29] <popey> uhhh
[09:29] <popey> It *shouldn't*
[09:29] <popey> i have only seen that when i had to reboot when my system failed
[09:30] <popey> I have seen that a lot with browsers, where all my cookies are lost if I reboot the computer while the browser is open :(
[09:30] <czajkowski> popey: I've had a weekend of many failed starts after reboot, today I cannot log into skype, and now telegram is looking to be reset up again
[09:30] <czajkowski> I thought I had lost my hard drive
[09:35] <GunnarHj> *bbl*
[09:38] <seb128> GunnarHj, then it shouldn't be an issue if the current version has the issue, britney only stops regressions
[10:18] <GunnarHj> seb128: Hmm.. I was wrong about the latter. :( So, what do we do? Should I prepare patches with only "amd64,i186" in d/control? (There are two SRU uploads too.)
[11:08] <Trevinho> popey: https://bugs.launchpad.net/snappy/+bug/1781906
[12:00] <willcooke> hi all
[12:01] <Laney> hey willcooke
[12:06] <Trevinho> hi willcooke
[14:25] <GunnarHj> Hi tsimonq2, the conclusion as regards those freshplayerplugin uploads is that we should better only build on amd64 and i386. I will prepare new proposals, and I think it would be smartest to drop the uploads from the bionic and xenial queues. Can you do the latter, please?
[16:25] <oSoMoN> didrocks, I hadn't tested the community theme in a while, it's looking great!
[16:29] <didrocks> oSoMoN: yeah, we are getting closer and closer to release it in cosmic :)
[16:35] <oSoMoN> didrocks, looking forward to it
[16:45] <GunnarHj> tsimonq2: Please disregard my latest request - Brian M. did it.
[20:31] <seb128> have a good night desktopers