[05:29] <jibel> good morning
[06:11] <didrocks> good morning
[07:00] <oSoMoN> good morning desktoppers
[07:18] <seb128> gooood morning desktopers
[07:19] <oSoMoN> salut seb128
[07:19] <seb128> lut oSoMoN :)
[07:22] <seb128> oSoMoN, so, beta freeze starting ... I was wondering if we wanted to try to get the new tb on the iso/demote enigma to universe? depends how much testing you would like to get from the update
[07:24] <oSoMoN> seb128, it looks like enigmail is already in universe
[07:25] <seb128> oSoMoN, sorry, I'm online getting my coffee :-/ I meant to proposed
[07:25] <seb128> e.g delete if from eoan proper
[07:25] <seb128> since britney will block the tb update as long as it breaks something in eoan
[07:27] <oSoMoN> unless we add a hint to temporarily unblock the migration, no?
[07:28] <seb128> well, does enigmail work with the new tb?
[07:28] <oSoMoN> note that I'm working on enigmail today, hopefully I get a working solution before eod that we can use until the package is updated in debian
[07:28] <seb128> like is that a real breakage or a test problem ?
[07:28] <oSoMoN> right, it's actually a real breakage
[07:29] <seb128> so it would probably less misleading to remove it than force tb and have a package installable that blews
[07:29] <seb128> anyway, let's see what you get by tonight
[07:29] <seb128> and decide tomorrow if that's  ok with you?
[07:31] <oSoMoN> sounds like a plan
[07:35] <seb128> :-)
[07:56] <seb128> Trevinho, hey, did you prepare that unity landing? they wanted/needed the fix for beta and the freeze started now...
[08:01] <marcustomlinson> morning all
[08:01] <willcooke> morning
[08:02] <didrocks> hey marcustomlinson, willcooke
[08:02] <Laney> morning!
[08:04] <didrocks> morning Laney
[08:08] <Laney> hey didrocks
[08:08] <Laney> good weekend / trip back?
[08:11] <didrocks> Laney: yeah, uneventful. Yourself? After this week-end in Paris? :)
[08:12] <Laney> delays
[08:12] <Laney> had to take a much later train home
[08:12] <didrocks> still on the same day at least?
[08:13] <Laney> technically no
[08:13] <Laney> but yes :P
[08:13] <didrocks> ahah, ok, very late then :) but still "okish"
[08:13] <Laney> not as bad as the Lyon delays indeed
[08:15] <didrocks> heh
[08:29] <Trevinho> seb128: hey yes... but vvileto failed so need to do some manual things
[08:29] <Trevinho> morning all
[08:29] <Trevinho> from the last day in Paris, helping me to go home... With the classic strike 😭
[08:31] <seb128> Trevinho, hey, oh ok. Good luck with the public transports :/
[08:32] <seb128> hey marcustomlinson willcooke Laney, how are you?
[08:32] <didrocks> yeah, not the best day for Trevinho
[08:34] <willcooke> very wet seb128 :)
[08:35] <willcooke> I've now got 9 out of 10 wallpapers, so I'm going to call it done
[08:35] <marcustomlinson> seb128: haha, yeah, there are clouds in the sky again, balance has been restored :D
[08:35] <marcustomlinson> seb128: i.e. all good :) how are you?
[08:36] <Trevinho> didrocks: I was thinking that they were striking only on Friday... But, it looks like they really care about the cause, not just the day off
[08:43] <didrocks> not having zsys installed but the generator (which will still be needed in the future) -> FAIL. Will spent some days to debug
[08:49] <Laney> hey seb128
[08:49] <Laney> doing gooood, you?
[08:55] <willcooke> Laney, squoosh is pretty amazing at compressing jpegs!  40 MB PNG -> Gimp -> PNG with some better options -> 8 MB PNG
[08:55] <Laney> nice
[08:55] <willcooke> 40 MB PNG -> Gimp -> JPG  -> 1.1 MB PNG
[08:55] <willcooke> *1.1MB JPEG
[08:55] <willcooke> 8 MB PNG -> Sqoosh -> 28
[08:55] <willcooke> *287kB JPG
[08:56] <willcooke> !!!
[08:56] <Laney> nice, I like the sound of that
[08:56] <Laney> assuming the result is good
[08:56] <Laney> ;-)
[08:56] <willcooke> :)
[08:56] <willcooke> So far, so good
[09:05] <jibel> I'm testing netboot for the beta and the session freezes on login on i386.
[09:05] <jibel> here is the journal https://paste.ubuntu.com/p/tGwVbBYq5J/
[09:05] <jibel> anyone have any clue what could be going on?
[09:06] <jibel> there is no crash
[09:08] <jibel> ah now it crashed
[09:13] <jibel> bug 1845165, not very helpful
[09:14] <jibel> is ubutnu-desktop on i386 from netboot still something we want to offer or we should just remove the test case?
[09:24] <Laney> not actually sure at this point in time but I'd be ok with not
[09:24] <Laney> based on the wider i386 story
[09:26] <willcooke> yeah, I think I'd be ok with that too.  From what I remember, we had the story about "if you still want to install on i386 hardware you can use netboot" but it got nacked and removed from the "formal" Q&A.
[09:26] <willcooke> I dont think it's something we should support at this point forward
[10:26] <Wimpress> Morning desktoppers o/
[10:26] <Wimpress> Swap day.
[10:26] <Wimpress> Or rather, an Ubuntu MATE day :-D
[10:32] <Trevinho> apparently not too bad the strike, looks like I'll be to the airport way earlier (and no lounge)... So #floorhacking.
[10:33] <willcooke> Trevinho, are you aware of a problem where you log in and GNOME Shell just doesn't respond to any input?
[10:33] <willcooke> I've seen it a few times in the past week
[10:33] <willcooke> feels like a race, because it doesn't always happen
[10:34] <Trevinho> willcooke: hmmh... nope. Is that something temporary or staying?
[10:35] <Trevinho> I have it on my bionic machine but that's something caused by sync stuff not done properly, and fixed now
[10:36] <willcooke> Trevinho, I doesn't happen every time, but I'll see if I can find a way to reproduce it.  At the moment it is in this state.  I switched to tty1 and gdm started, then back to 2 and GNOME Shell is still on the screen and the mouse moves, but nothing responds (no kbd, no mouse) and I can open a new cli session on tty 3
[10:36] <willcooke> anything I can do before I reboot it?
[10:36] <willcooke> (or restart gdm)
[10:36] <Trevinho> willcooke: yes, attach to it via gdb...
[10:37]  * willcooke installs ssh
[10:37] <Trevinho> willcooke: sudo gdb -p `pidof gnome-shell` but check is the one launched by the user
[10:38] <Trevinho> the pid I mean
[10:38] <Trevinho> willcooke: also mutter and shell debug symbols please
[10:38] <willcooke> Trevinho, I should install those dbg packages right?
[10:39] <willcooke> I dont yet have the debug packages installed, but I do have gdb connected, anything useful I can do with out the debug packages?
[10:40] <Trevinho> willcooke: yes, add ddeb repo and install libmutter dbgsym and gnome-shell
[10:40] <Trevinho> willcooke: well for now you can just try with `call (void) gjs_dumpstack()`
[10:41] <Trevinho> and check journalctl /usr/bin/gnome-shell -b0 -e to see if you get anything useful from JS side of things
[10:41] <Trevinho> however I suppose isn't something triggered by JS, but we never know
[10:43] <willcooke> Trevinho, https://paste.ubuntu.com/p/CWtV8N9RZR/
[10:43] <Trevinho> willcooke: this should automatize it
[10:43] <Trevinho> sudo gdb -p $(pgrep -U $USER -x gnome-shell) -batch   -ex "set logging on"  -ex "bt full" -ex "call (void) gjs_dumpstack()"   -ex quit
[10:43] <Trevinho> ah goof
[10:43] <Trevinho> d*
[10:43] <Trevinho> mh, yeah.. nothing from JS lands
[10:44] <willcooke> Trevinho, so if I install the ddebs do I need to restart?
[10:45] <Trevinho> willcooke: no, just quit gdb and start again it
[10:45] <Trevinho> (or use that script, and attach the produced gdb.txt)
[10:47] <willcooke> dbg packages installer
[10:47] <willcooke> *installed
[10:50] <willcooke> Trevinho, https://paste.ubuntu.com/p/ZnY4YnRBWY/
[10:50] <willcooke> nothing new in journal it seems
[10:51] <willcooke> full journal: https://paste.ubuntu.com/p/tdKDGRcPzM/
[10:53] <willcooke> I wonder if the portals has anything to do with it... only because when it did this last time I somehow managed to get a polkit dialog up, and when I entered the password, everything continued as normal
[10:55] <Trevinho> willcooke: mh, can't see much from that thread, try with "thread apply all bt full"
[10:55] <Trevinho> willcooke: it also misses glib dbgsym, but it seems just the loop
[10:55] <Trevinho> well, actually better if you install them too :P
[10:56] <willcooke> libglib2.0-0-dbgsym this one?
[10:56] <Trevinho> willcooke: you can get that scripted by replacing the "bt full" with the command I gave you before
[10:56] <Trevinho> willcooke: yeah
[10:57] <willcooke> Trevinho, https://paste.ubuntu.com/p/rPY2VDj6tX/
[11:03] <willcooke> Laney, smol wallpapers! https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1845188
[11:03] <willcooke> 5.6MB this time
[11:03] <willcooke> in total
[11:03] <Laney> nice one
[11:03] <Laney> thx
[11:03] <willcooke> (but there is one missing still)
[11:03] <Trevinho> willcooke: there's something related to __pthread_cond_wait in i965_dri, so maybe add those symbols too and we could get something from tjaalton, might be a dead-lock in the driver? But there's something also in mozjs... mhmhm
[11:04] <willcooke> tjaalton, can you tell me what packages I need to install for dbg symbols?
[11:05] <willcooke> FWIW the mouse pointer still moves around the screen and gets painted correcty
[11:05] <Trevinho> willcooke: I need libmozjs-60-0-dbgsym
[11:06] <Laney> I had this with a Shell dialog last week: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1607
[11:06] <Laney> might be relevant
[11:06] <Trevinho> willcooke: dri package would be libgl1-mesa-dri-dbgsym
[11:06] <Trevinho> let's get the bt full with these all, once you get it you can kill it and open a bug with all the logs we have
[11:07] <willcooke> roger roger
[11:07] <willcooke> Laney, interesting, can confirm the clock is updating here too, which I hadnt noticed
[11:07] <Trevinho> although from a first look it might come from anywhere, and since we can't see where a trhead was started is a bit complicated
[11:08] <Trevinho> unless is there a way for that.... (Laney^) :o
[11:08] <willcooke> Trevinho, I'm running from the x staging ppa per t_jaalton's request for testing.
[11:08] <Trevinho> willcooke: ooohhh... mh, is there a dbg package there? maybe you've to get it manually
[11:08] <Trevinho> the name should be the same
[11:08] <willcooke> seems like its missing
[11:09]  * Trevinho cries
[11:09]  * Trevinho cries in 0x00007fef2461c5cb
[11:09] <willcooke> XD
[11:09] <willcooke> Trevinho, is this any use?  https://paste.ubuntu.com/p/BZdK6TcgpW/
[11:11] <Trevinho> willcooke: wait isn't https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+files/libgl1-mesa-dri-dbgsym_19.2.0~rc4-1ubuntu1~ppa1_amd64.ddeb the one we're looking for?
[11:11] <Trevinho> looking into details of https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages there are dbgsym's
[11:11] <Trevinho> so might need to manually install them
[11:11] <willcooke> ahhhhhhhhhhhh
[11:12] <popeycore> :( another lockup on 19.10
[11:12] <willcooke> popeycore, do me a favour - can you leave it 5 mins and see if the clock keeps up
[11:13] <popeycore> i had to reboot, sorry
[11:13] <willcooke> next time
[11:13] <Trevinho> niceeee..... :|
[11:13] <Trevinho> looks like it's something in the gfx stack though
[11:13] <popeycore> interestingly when i tried to reboot, i got messages in dmesg about hung process on my gpu
[11:14] <Trevinho> popeycore: oh!
[11:14] <willcooke> Trevinho, I think I installed that package correctly.. https://paste.ubuntu.com/p/pSshP8V2SZ/
[11:14] <Trevinho> popeycore: journalctl -b-1 once you rebooted
[11:17]  * Trevinho fighting with tunnels...
[11:17] <popey> Trevinho: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017
[11:17] <popey> attached to the bottom of that
[11:18] <popey> Sep 24 12:00:09 KinkPad-K450 kernel: INFO: task kcompactd0:43 blocked for more than 120 seconds.
[11:27] <tjaalton> willcooke: I don't see i965_dri.so in the latest one?
[11:28] <willcooke> curious
[11:33] <willcooke> Trevinho, is there anything more I can do with it in this state, or shall I reboot and focus on finding a way to reproduce it?
[11:42] <Trevinho> willcooke: mhmh I think we can't do much a part than studying the trace
[11:43] <willcooke> Trevinho, oki.  I've opened this: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845198   and I will try and find a way to recreate it
[11:43] <Trevinho> tjaalton: yeah weird... Maybe that thread died or something?
[11:43] <Trevinho> willcooke: try again just to see if we get the dri log again
[11:43] <willcooke> Trevinho, sorry, I just turned it off :(
[11:44] <popey> willcooke: you having similar issues to me? Or is this completely unrelated?
[11:44] <willcooke> popey, unclear
[11:44] <popey> ok
[11:44] <willcooke> hence my question about the clock
[11:44] <popey> how are you monitoring the clock? just ssh in and run "watch -d date"?
[11:44] <willcooke> no just looking at the screen
[11:45] <popey> oh
[11:45] <willcooke> i.e. gnome shell is not quite dead
[11:45] <popey> nothing updates for me, hard lockup of the shell
[11:45] <popey> I mean, I didnt look at the clock, but pretty sure, will check next time
[11:47] <willcooke> popey, was it related to building snaps again this time?
[11:47] <popey> nope. just happened randomly, when I opened a tab in firefox
[11:48] <willcooke> oki.
[11:48] <seb128> Laney, could you try if you also get "login with another user fail" and tell me what component you would report that problem against?
[11:48] <Laney> I'm looking at fast user switching now
[11:48] <Laney> you already told me about that one
[11:48] <Laney> gdm
[11:48]  * willcooke ponders gnome-keyring... unlocking... polkit windows 
[11:49] <popey> also, I have 3 screens on, and video playing in chrome
[11:49] <popey> that's quite a common setup when I get a lockup
[11:49] <seb128> Laney, yeah I told you, I would still welcome someone else to confirm if they get it too or if something weird here, but not important
[11:49] <Laney> it does happen here I'm looking at it atm
[11:49] <Laney> feel free to file a bug if you want a number to track or something
[11:50] <seb128> ah ok, sorry I didn't understood properly that you "fast user switching" was referring to that
[11:50] <seb128> your*
[11:50] <Laney> that might be a term from windows
[11:51] <seb128> anyway, I let you work on it then, thanks :)
[11:51] <Laney> no, I remember, we used to have a thing called FUSA, that's why I call it fast user switching
[11:52] <seb128> ah, makes sense now that you mention it
[12:06] <Trevinho> willcooke:  can you attach both your logs (the one with dri and the last one) to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017
[12:06] <Trevinho> I'm quite sure we're talking of the same issue
[12:10] <willcooke> Trevinho, done
[12:15] <jibel> seb128, I've the ubiquity-dm error again with beta
[12:15] <seb128> jibel, I'm not surprised, I didn't see a reason it would have been fixed in between the images
[12:16] <seb128> it's probably a timing issue :/
[12:17] <jibel> and the shell is frozen but I can switch to a vt
[12:17] <seb128> jibel, thx, I will download the daily ISO and see if I get it as well ... you let boot on the screen with the try/install gtk UI and click install right?
[12:17] <jibel> seb128, just boot and do nothing
[12:17] <jibel> I'll try on hw
[12:18] <seb128> k
[12:18] <jibel> seb128, it's the try/install session that crashes
[12:19] <popey> I had 19.10 crash in vbox today on first boot of the "try" option too
[12:20] <popey> from today's daily
[12:20] <popey> https://i.imgur.com/MKrwu54.png
[12:21] <jibel> yeah same that's bug 1844509
[12:21] <jibel> 2 critical for the beta then
[12:21] <GunnarHj> I have also noticed issues with the installer, and can't help wondering if I have contributed to it via this upload:
[12:22] <GunnarHj> https://launchpad.net/ubuntu/+source/localechooser/2.71ubuntu4
[12:22] <jibel> GunnarHj, what kind of issues?
[12:23] <GunnarHj> jibel: The Ubiquity welcome screen does not show up, but instead I see the error message which popey just showed in a screenshot.
[12:24] <popey> Further, clicking OK got me an unusable desktop
[12:24] <popey> locked up, or was for some other reason unresponsive
[12:24] <jibel> GunnarHj, I don't think it's related to your upload, I noticed this problem a day before;
[12:25] <jibel> popey, that's bug 1845198
[12:25] <GunnarHj> jibel: Ok, that's a relief for me, kind of. :)
[12:26] <seb128> GunnarHj, I wonder if you did create the issue still, the report from jibel had ibus error and it started a bit after the recent merge from experimental
[12:27] <GunnarHj> seb128: What I did was trying to make a new language visible in the installer. Do you know if there is more into it which I missed, and which may be the reason?
[12:28] <jibel> sounds more like a timing issue as seb128 said, because if you restart ubiquity-dm from a vt it starts fine
[12:28] <seb128> GunnarHj, in case that was not clear from why I wrote before, I wonder if the issue is due to the new ibus
[12:28] <GunnarHj> seb128: Sorry. Now I see what you wrote. :)
[12:28] <kenvandine> I'm so happy with the theme updates, looks great
[12:28] <willcooke> seb128, this "locking up" of GNOME Shell are you talking about there? ^  I did see some stuff in the logs related to ibus
[12:29] <seb128> willcooke, well, I was talking about the liveCD failing to load the ubiquity-try screen, could be the same bug that the lock though
[12:29] <jibel> willcooke, yeah 2 bugs lock up and the "try/install" session doesn't start
[12:29] <willcooke> interesting
[12:30] <seb128> or one bug and it doesn't load because it lock up?
[12:31] <jibel> it wouldn't be a real milestone without critical bugs :)
[12:32] <seb128> that's job security!
[12:33] <GunnarHj> The very latest ibus change is the reversal of the CVE patch which breaks Qt. It happened yesterday night.
[12:34] <seb128> GunnarHj, that bug was there a week ago before the reversal
[12:36] <GunnarHj> seb128: The patch was added about a week ago, and dropped yesterday.
[12:36] <seb128> GunnarHj, yes, I was saying that the issue was happening after the patch was added and is still happening today, so it's not due to this patch
[12:37] <GunnarHj> seb128: Ah, so the newest version is already in the ISO then?
[12:38] <seb128> jibel, did you try current or pending?
[12:39] <seb128> GunnarHj, it's on the newest image according to http://cdimage.ubuntu.com/daily-live/proposed/eoan-desktop-amd64.manifest
[12:39] <jibel> seb128, pending. It's today's build that I didn't promote due to this problem
[12:39] <seb128> GunnarHj, sorry, http://cdimage.ubuntu.com/daily-live/proposed/eoan-desktop-amd64.manifest
[12:39] <seb128> jibel, k, thx
[12:40] <seb128> GunnarHj, so yeah, was tested with 1~exp2ubuntu2
[12:40] <GunnarHj> k
[12:40] <seb128> well I'm guessing ibus issue but it might not be due to it and just gnome-shell
[12:40] <seb128> poor Trevinho
[12:43]  * Trevinho hides
[12:45]  * Trevinho actually goes boarding
[12:45] <seb128> Trevinho, safe flight!
[12:46] <Trevinho> thanks, I've plenty of branches to work on in between, so... lovely fliiight indeed
[12:48] <didrocks> the sound volume bug, the sound volume bug, the… :)
[12:49] <seb128> key repeat one?
[12:51] <didrocks> yep
[12:51] <didrocks> good memory ;)
[12:52] <kenvandine> I've rebuilt gtk-common-themes in candidate to include the latest yaru changes.  I'd appreciate it everyone could help kick the tires a little today
[12:53] <kenvandine> just run some snaps to make sure they look like you'd expect
[12:53] <seb128> just install them in a normal session and make sure they work with yaru normal?
[12:53] <Trevinho> ... and boarded. What would be life without euro-roaming!?!
[12:53] <Trevinho> L_aney I feel you :°
[12:53] <seb128> lol
[12:55] <clobrano> kenvandine, I have to rebuild my 18.04 VM, but I should be able to test it this afternoon
[12:56] <kenvandine> seb128: yeah
[12:56] <seb128> k
[12:56] <kenvandine> i'll do some thorough testing with gtk-3-widget-factory
[12:56] <kenvandine> but good to get some other eyes on our everyday snaps
[12:57] <seb128> right
[12:57] <popey> that should be something chris wayne could help with?
[12:57] <didrocks> removing zsys has a lot of repercution on the dataset (due to issues with non empty dir) :/
[13:05] <seb128> didrocks, enough that you think we need to revisit our options?
[13:05] <seb128> willcooke, ^
[13:05] <didrocks> seb128: I don't know, we are back at the race on boot now with the dataset layout that only zsys can fix properly
[13:05] <didrocks> we can workaround, but it's not going to be robust
[13:06] <didrocks> (and work that are going to be removed once zsys is in)
[13:06] <seb128> how much work and how unrobust?
[13:07] <didrocks> it's already a day "lost" (with progress, but now on that last roadblock ^). The last one will need testing and such, I think 3-4 days… (and again, things will be ditched next cycle hopefully)
[13:08] <seb128> (right, but we are our option, restart the discussion about including zsys after beta? how long is that likely to take into arguing and how likely to success in changing the outcome?)
[13:08] <seb128> I mean I understand the frustration
[13:08] <seb128> I'm just unsure we have other options at this point, out of saying we give up on shipping for this cycle or the normal image...
[13:08] <didrocks> well, I think the decision is already taken, but I just want to hilight that not including zsys is making us loose a week of work basically (which won't be reused)
[13:09] <seb128> right, understood
[13:09] <didrocks> so it's just the most expensive option (for our team)
[13:09] <seb128> thx for pointing it out, and don't worry we know it's not your fault and that it is impacting/delaying the "useful" work
[13:09] <seb128> right :/
[13:09] <willcooke> When you say "removing" what do you mean?   We said that people would have to install zsys manually, right?
[13:09] <seb128> well we are screwed at this point anyway, let's hope it doesn't happen again
[13:10] <didrocks> preferring to raise this :) (hoping as well we won't have specific bugs to those workarounds and won't impact transitionning to zsys next cycle)
[13:10] <didrocks> willcooke: as "the workaround may be incompatible with zsys approach"
[13:10] <didrocks> and so, hacks will have to be removed later on
[13:10] <didrocks> and if people install zsys, we have to figure out a way to transition them
[13:10] <willcooke> meh, IRC is no good for this sort of thing, let's have a hangout in a bit?
[13:11] <didrocks> if you want, but I had the feeling the decision won't change and it would be better to focus/not loose more time?
[13:11] <didrocks> I just escalated that it would be more work than envisioned
[13:12] <willcooke> oki, good to know, thanks.  I still don't really understand what the problem is though, and I would like to
[13:13] <didrocks> if you want to go into the details, there is a race between daemons writing early in /var/lib before the zfs systemd service is mounting it
[13:14] <didrocks> it's something that isn't fixed upstream, if you want a separate /var/lib dataset (which was desired after the review with Steve 6 months ago)
[13:14] <didrocks> and known to be problematic. Zsys fixed it by an early systemd generator
[13:15] <didrocks> hoping that's the level of tech details you were looking for
[13:17] <ricotz> hi, is it possible to sync libcloudproviders 0.3.0-2 from debian which re-introduces the dropped vala bindings
[13:17] <seb128> jbicha, ^
[13:18] <seb128> (since you did those uploads)
[13:18] <willcooke> didrocks, oki, I think I get it.  Aren't we expecting people to install zsys though?
[13:19] <didrocks> willcooke: right, but if they don't before first boot -> they are screwing up their datasets
[13:19] <didrocks> with no easy way to recover
[13:22] <willcooke> didrocks, got it.  Thanks for caring and working on a fix, much appreciated
[13:22] <didrocks> I just hope we'll be able to have something compatible with and without zsys (for transitions)
[13:22] <didrocks> we'll see how it goes
[13:24]  * willcooke has faith in the l33t skillz of didrocks 
[13:24] <willcooke> kenvandine, updated gtk-common-themes to beta, so far so good
[13:29] <popey> kenvandine: here's a fun thing. snap remove the gnome platform snap, reboot then try and run one of your snaps :)
[13:29] <popey> kenvandine: Your snaps aren't able to detect that the content snap went away, and they crash all over the place.
[13:29] <popey> Some might say "that's working as designed", but it might be nice if we did something pleasant. Where should I file this do you think? :)
[13:30] <willcooke> Meeting time, everybody shut up and pay attention to me
[13:30] <popey> 💩
[13:30] <willcooke> #startmeeting Desktop Team Meeting 2019-09-24
[13:30] <meetingology> Meeting started Tue Sep 24 13:30:34 2019 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:30] <meetingology> Available commands: action commands idea info link nick
[13:31]  * Trevinho at 10 meters from ground
[13:31] <seb128> Trevinho, safe flight!
[13:31] <Trevinho> love 4g on connection
[13:31] <seb128> you are supposed to be in flight mode at this point btw :p
[13:31] <willcooke> Roll call: didrocks, duflu (hols), jamesh (hols), hellsworth(swap), jibel, kenvandine (out?), laney, marcustomlinson, oSoMoN, seb128, tkamppeter, trevinho (going up), robert_ancell (out)
[13:32] <oSoMoN> 🐱/
[13:32] <oSoMoN> Trevinho, don't crash that plane
[13:32] <seb128> hey
[13:32] <willcooke> happy travels Trevinho
[13:32] <willcooke> Flight mode FTW
[13:32] <willcooke> Let's zip through the rls bugs
[13:33] <jibel> you're also not supposed to use a laptop during takeoff
[13:33] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:33] <willcooke> Looks clear
[13:33] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
[13:33] <willcooke> Also clear
[13:34] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
[13:34] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844575
[13:34] <willcooke> Is it Wayland only?
[13:35] <seb128> likely
[13:35] <Laney> think so
[13:35] <Laney> DENIED
[13:35] <willcooke> heh
[13:35] <willcooke> so yeah, -1 for rls status I guess
[13:36] <seb128> -1
[13:37] <willcooke> https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1845188
[13:37] <willcooke> I tagged that, but really, it's not a release blocker
[13:37] <willcooke> I shouldn't have tagged it on reflection
[13:37] <Laney> well
[13:37] <Laney> gives me a chance to ask if anyone else wants to do it
[13:37] <Laney> :-)
[13:38] <willcooke> :)
[13:38] <Laney> got my hands inside gdm, would be good not to switch
[13:38] <willcooke> Would anyone like to package up the wallpapers, they should be ready to go
[13:38] <Laney> plus, easy packaging, could be fun for someone
[13:38] <willcooke> oSoMoN, I think you helped out last time, if you're interested?>
[13:38] <Laney> plenty of examples in the history to copy
[13:38] <oSoMoN> yeah, can do
[13:38] <willcooke> merci
[13:38] <Laney> neato
[13:39] <willcooke> Assigned, and untagged
[13:39] <seb128> thx oSoMoN
[13:39] <willcooke> which is kinda odd, but I think that's opk
[13:39] <willcooke> ok
[13:39] <seb128> I can do review/sponsoring if needed
[13:39] <willcooke> thanks seb128
[13:39] <willcooke> next up: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845198
[13:39] <willcooke> which may be https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017 too
[13:39] <seb128> +1
[13:40] <willcooke> yeah, agree
[13:40] <willcooke> and I think there's really only one person to look at it, right?
[13:40] <seb128> assign to Trevinho (sorry Marco)
[13:40] <seb128> yes :/
[13:40] <seb128> well maybe duflu could but he's off atm
[13:40] <seb128> we can to tradding of some work once he's back if needed
[13:40] <willcooke> ack
[13:41] <willcooke> assigned and targetted
[13:41] <willcooke> k, that's it for rls bugs.
[13:41] <jibel> another ee-incoming is bug 1844509
[13:41] <jibel> it is not in the list and affects ubiquity but it's more likely due to a desktop component
[13:41] <willcooke> jibel, so comment #2 is not true any more?
[13:42] <jibel> no it is not, I thought I added a comment to say so.
[13:42] <jibel> will do
[13:42] <seb128> ideally foundations would do the investigation and bounce back to us if needed since they own ubiquity but do we count on that?
[13:42] <willcooke> oki, thanks
[13:42] <willcooke> seb128, I dont think we should count on it
[13:42] <seb128> k
[13:42] <seb128> anyway +1
[13:43] <willcooke> who would like to work out what's going on in that one?
[13:43] <willcooke> is it related to the previous one?
[13:43] <seb128> dunno but I've the bug in a VM atm and looking at the logs
[13:43] <seb128> so feel free to assign to me for round 1
[13:43] <willcooke> kk
[13:43] <willcooke> thanks seb128
[13:44] <seb128> I hope it doesn't hope going back Marco's way :p
[13:44]  * seb128 hugs Trevinho
[13:44] <Laney> bet not
[13:44] <willcooke> seb128, I was going to say - we should spend some time doing an "unassigned" review and seeing if we can trim the old rls bugs list.  Lets try and do that tomorrow?
[13:44] <Laney> bet it's something in the startup sequence rather than shell itself
[13:45] <Laney> just my guess, happy to put 10€ on it though
[13:45] <seb128> lol
[13:45] <willcooke> XDDDD
[13:45] <seb128> I'm not betting, made enough profit for the month :p
[13:45] <willcooke> :D
[13:45] <willcooke> #topic AOB
[13:45] <seb128> willcooke, +1 on cleaning rls
[13:45] <willcooke> Anyone got anything
[13:45] <willcooke> for AOB
[13:45] <seb128> we should review now the targetted/unassigned list
[13:45] <Laney> HAHA
[13:45] <seb128> since those are +1/-1 things
[13:45] <seb128> also proposedmigration
[13:46] <willcooke> seb128, you want to do the targetted ones in the meeting?
[13:46] <seb128> yes, we discussed that previous time and agreed it was the right to do iirc
[13:46] <jibel> AOB. I'd like to escalate bug 1840122. It's breaking automated tests and make iso testing a real PITA
[13:47] <seb128> it's basically the same as the incoming ones
[13:47] <Laney> you two mean different things by the word targetting
[13:47] <Laney> targetted*
[13:47] <seb128> I mean http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[13:47] <seb128> &co
[13:47] <seb128> for unassigned entries
[13:48] <willcooke> jibel, I will escalate that one one
[13:48] <willcooke> seb128, oki, let's do it
[13:48] <jibel> thx
[13:48] <willcooke> #topic unassigned rls bugs
[13:49] <willcooke> https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459
[13:50] <willcooke> GunnarHj, are you looking at that one for Bionic still?  ^
[13:50] <seb128> it that's fix commited we can skip those
[13:50] <willcooke> ah yeah
[13:50] <seb128> looks like there is none on the bionic list
[13:50] <willcooke> eyah
[13:51] <seb128> one one disco list
[13:51] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1842904
[13:52] <willcooke> assign duflu and see if he wants to push through the SRU?
[13:52] <seb128> I would delete the disco line
[13:52] <seb128> we got no user report and it's almost 19.10 time
[13:52] <willcooke> that works
[13:53] <seb128> duflu can still targetting it back with a sponsoring request if he wants
[13:53] <willcooke> ee is clear
[13:53] <willcooke> #topic proposed migrations
[13:54] <willcooke> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[13:54] <willcooke> Anything in that list cause for concern>
[13:54] <willcooke> ?
[13:55] <Laney> promote those libcairo-gobject-perl ones
[13:55] <Laney> the others are in hand
[13:55] <Laney> ... well I'm wondering why g-i is foundations ...
[13:56] <seb128> p_itti's heritage? ;-)
[13:56] <willcooke> should we move it to us
[13:56] <willcooke> >
[13:56] <willcooke> ?
[13:56] <seb128> it would probably reflect better reality
[13:56] <Laney> maybe they want to fix ruby-gnome
[13:56] <seb128> I looked a bit at this one yesterday btw and opened https://bugs.launchpad.net/ubuntu/+source/ruby-gnome/+bug/1845008
[13:56] <Laney> that's the only reason I just noticed
[13:57] <Laney> yeah
[13:57] <willcooke> k, I will ask Pat when I speak to her about #1840122
[13:57] <Laney> don't really understand it well enough to fix it atm
[13:57] <Laney> but the status is real there, new g-i does break that
[13:57] <Laney> guess I could own it, might work on that later in the week
[13:58] <willcooke> thanks Laney
[13:58] <Laney> that is it
[13:58] <willcooke> #topic AOB2
[13:58] <marcustomlinson> AOB2?
[13:58] <Laney> AAOOBB
[13:58] <didrocks> better than AOB1, obviously
[13:59] <marcustomlinson> haha
[13:59] <willcooke> I was too eager last time
[13:59] <willcooke> AOB2.0 serverless
[13:59] <willcooke> anyone got anything?
[13:59] <willcooke> in 5....
[13:59] <willcooke> 4...
[13:59] <willcooke> 3..
[14:00] <willcooke> 2.
[14:00] <willcooke> 1
[14:00] <willcooke> #endmeeting
[14:00] <meetingology> Meeting ended Tue Sep 24 14:00:40 2019 UTC.
[14:00] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-09-24-13.30.moin.txt
[14:00] <didrocks> thx
[14:00] <willcooke> thank you!
[14:00] <seb128> thanks!
[14:00] <willcooke> popey, carry on :)
[14:00] <marcustomlinson> thanks
[14:01]  * popey breathes 
[14:21] <kenvandine> popey: atsome point today i'll get emails of the automated builds with the  gtk-common-themes update
[14:21] <popey> ok
[14:21] <kenvandine> all thanks to cwayne :)
[14:26] <popey> What do you think of my question about removing content snaps?
[14:27] <seb128> popey, looks like something that should be solved by snapd for all snaps rather than requesting every single snap author to handle the case
[14:27] <seb128> imho
[14:27] <popey> well, i wasn't sure if it was an error in the snap-store snap or desktop launcher maybe
[14:28] <seb128> kenvandine, ^
[14:28] <seb128> popey, well if you use some content interface snapd should be able to tell no?
[14:29] <popey> That would indeed be sane :)
[14:29] <seb128> probably better discussed on discourse than here in any case
[14:29] <popey> I'll start a forum thread, see what they say
[14:29] <popey> agreed :D
[14:29] <seb128> thx
[14:38] <kenvandine> popey: i must have missed that
[14:44] <seb128> kenvandine, it was the minute before the meeting started
[14:45] <kenvandine> seb128: thanks
[14:46] <kenvandine> popey: yeah, forum post i think
[14:46] <kenvandine> i'd argue that snapd shouldn't let you remove those if there are snaps that need them
[14:46] <kenvandine> if the snap being removed would be the last snap that provided the required interface, snapd should at least complain
[14:47] <popey> yes, agreed, or worst case, should let you remove that snap, and install another which provides slots, and then carry on
[14:47] <popey> Anyway, will start a thread
[14:50]  * Trevinho landed... worried for the bugs 😓
[14:54] <seb128> Trevinho, don't for now :)
[14:54] <Trevinho> seb128: on that lockup issue I'm quite sure is something lower in the stack though
[14:54] <seb128> Trevinho, short flight it was!
[14:54] <seb128> Trevinho, ah, "good"
[14:54] <Trevinho> we're basically neighbors!
[14:55] <Trevinho> but I fixed some gjs branches I had in queue.. and tracker miner, so good flight 😅
[14:56] <seb128>  :)
[14:57] <seb128> you should fly more often!
[14:57] <Trevinho> if we only had that tunnel....
[14:58]  * kenvandine uploaded the fix for the impatience extension, now I am a much happier gnome-shell user :)
[15:00] <Trevinho> kenvandine: 0.5 or less?
[15:03] <kenvandine> i use 0.3
[15:04] <kenvandine> actually, no i have it set to 0.5
[15:08] <popey> kenvandine: https://forum.snapcraft.io/t/removing-content-snap-breaks-a-snap/13382
[15:08] <willcooke> Trevinho, have recreated the bug, but only by reboot about 5 times.
[15:08] <willcooke> ohohohohoho, got a crash report
[15:08] <willcooke> ha, but I can't interact with the crash dialog
[15:12] <mitya57> Trevinho: Hi! I see you looked at unity MRs, can you please also look at https://code.launchpad.net/~mitya57/compiz/+git/compiz/+merge/372943?
[15:13] <Trevinho> willcooke: try get the same trace again
[15:15] <willcooke> Trevinho, https://paste.ubuntu.com/p/x8NhtvZXG5/
[15:16] <willcooke> (also added to the bug comments)
[15:24] <jibel> Laney, could you review bug 1843768 and the branch attached?
[15:25] <jibel> Laney, this is the ffe for zfs in the installer
[15:26] <jibel> ths MP is https://code.launchpad.net/~jibel/ubiquity/+git/ubiquity/+merge/373087
[15:27] <jibel> for the shell zsys-setup apart from the layout of the dataset it's pretty standard sh, so it should not be a problem for you to review it too.
[15:27] <jibel> tell me is you have any question/comment
[15:29] <jibel> if*
[15:31] <Laney> jibel: ok, I will put it on the queue of stuff to do, thanks
[15:31] <seb128> jibel, do you think https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1844689 is something you could look at?
[15:32] <jibel> seb128, sure
[15:32] <seb128> thx
[15:32] <jibel> assign it to me
[15:32] <seb128> done!
[15:39] <seb128> bah, I can't reproduce that ubiquity-dm issue by stopping everything and starting the job from a VT and the logs are not very useful :-/ debugging that kind of problems is annoying
[15:43] <GunnarHj> seb128: I may recall wrong, but I think that the ubiquity welcome screen only shows up on a legacy machine, i.e. without UEFI.
[16:08] <marcustomlinson> howdy hellsworth
[16:21] <hellsworth> hi marcus!
[16:23] <Laney> anyone ever played with one of those toys where you take apart a cube made up of different shaped interlocking pieces and have to put it back together?
[16:23] <Laney> surpisingly hard
[16:23] <Laney> that's what gdm does to my brain
[16:23] <hellsworth> yep. they're fun but frustrating
[16:23] <Laney> hey hellsworth
[16:23] <hellsworth> hi there
[16:24] <Laney> anyway. fast user switching works here now, let's see what the reviewers say
[16:25] <Trevinho> Laney: anyway related to the super-secret issue? :)
[16:25] <Trevinho> Laney: and... where's the MP?
[16:25] <Laney> dunno what you mean
[16:25] <Laney> not there yet, writing the commit message
[16:26] <Trevinho> Laney: ah, nothing I was just creating some curiosity around :)
[16:28] <Trevinho> willcooke: you were getting that issue at login, or lockscreen, I mean, I should just reboot various times and it should happen on gdm right?
[16:28] <willcooke> yeah login
[16:28] <Trevinho> hi hellsworth
[16:29] <Trevinho> willcooke: mh, so we were analyzing the wrong shell xD
[16:29] <hellsworth> hi Trevinho
[16:29] <willcooke> Trevinho, oh?  I mean it logged in fine (it seems) and I got the proper desktop up
[16:30] <Trevinho> willcooke: mh, so you login, and things hang, but having the user view in front of you, the dasktop say.. not the lockscreen
[16:31] <willcooke> Trevinho, correct. I've got the full desktop in front of me, but I can't click on anything.  The clock tells the right time though
[16:49] <hellsworth> kenvandine, https://gitlab.gnome.org/GNOME/gnome-clocks/merge_requests/27 and https://gitlab.gnome.org/GNOME/gnome-clocks/merge_requests/32
[16:51] <kenvandine> hellsworth: thanks
[16:53] <kenvandine> hellsworth: question is, do we wait for 32 to merge then rebase 27?
[17:04] <hellsworth> kenvandine, nah I'd vote for merging 27 and let 32 be rebased
[17:14] <oSoMoN> seb128, I have an enigmail build of 2.1.2 in ppa:osomon/tb-tests with autopkgtests passing \o/
[17:15] <oSoMoN> I need to clean up my changes a bit, and it should be upload-able to eoan
[17:53] <willcooke> night all
[20:06] <hellsworth> kenvandine, https://gitlab.gnome.org/GNOME/gnome-mahjongg/merge_requests/16
[20:31] <hellsworth> kenvandine, https://gitlab.gnome.org/GNOME/gnome-tetravex/merge_requests/7
[20:49] <hellsworth> kenvandine, https://gitlab.gnome.org/GNOME/hitori/merge_requests/24
[21:09] <hellsworth> kenvandine, https://gitlab.gnome.org/GNOME/lightsoff/merge_requests/7
[21:52] <hellsworth> kenvandine, (or anyone really) I don't hear any sounds in quadrapassel installed from apt. Does anyone else? Without knowing what the sounds should be, I can't tell if my snap'd version has a correct sound section or not.
[22:29] <kenvandine> I'll check in the morning