[07:03] <oSoMoN> good morning desktoppers
[07:24] <ricotz> good morning desktopers
[07:25] <didrocks> good morning
[07:26] <ricotz> oSoMoN, hi, looks like firefox 65 requires gcc 7 for armX builds (more precisely webrtc aka chromium)
[07:26] <ricotz> didrocks, hey
[07:26] <didrocks> hey ricotz
[07:32] <duflu> Morning oSoMoN, ricotz, didrocks
[07:32] <didrocks> hey duflu
[08:56] <willcooke> morning
[08:56] <duflu> Morning willcooke
[09:01] <Laney> ahoy
[09:02] <duflu> Morning Laney
[09:02] <duflu> I assume
[09:04] <clobrano> morning all o/
[09:05] <duflu> Hi clobrano
[09:05] <clobrano> hi duflu :)
[09:09] <didrocks> hey willcooke, duflu, Laney, clobrano!
[09:09] <clobrano> morning didrocks
[09:46]  * Laney meows
[17:21] <willcooke> andyrock, kenvandine just mentioned that he can recreate the d-2-d lock sreen bug
[17:21] <willcooke> or at least, he could, until he installed your fix
[17:21] <willcooke> :)
[17:21] <kenvandine> andyrock: yeah, i did a clean install of 18.10 the week of release
[17:21] <kenvandine> and didn't see the bug for more than a week
[17:21] <kenvandine> and it's been consistent ever since
[17:21] <kenvandine> and i never installed dash-to-dock
[17:22] <kenvandine> yesterday i installed the deb of ubuntu-dock from disco and haven't seen it since
[17:22] <kenvandine> so i think the fix is good
[17:22] <andyrock> kenvandine: any steps to reproduce it?
[17:22] <andyrock> kenvandine: there are people still reporting the issue
[17:22] <kenvandine> just let my laptop sleep
[17:22] <kenvandine> it would happen 100% of the time
[17:23] <kenvandine> willcooke witnessed this daily back in SLC :)
[17:24] <andyrock> kenvandine: the main issue is a reference count mismatch in one or more MetaWindows between the c code and the gjs one
[17:24] <andyrock> but one it happens I'm not sure
[17:24] <kenvandine> yeah, i'm pretty sure you have actually fixed it
[17:24] <kenvandine> my laptop has gone to sleep quite a few times since installing the fix
[17:24] <kenvandine> and it hasn't happened
[17:24] <kenvandine> but it did happen 100% of the time
[17:25] <andyrock> mmm it's not a true fix, it's a workaround that allows use to buy some time
[17:25] <andyrock> :D
[17:26] <kenvandine> lol
[17:26] <kenvandine> ok
[17:26] <kenvandine> well i do appreciate it :)
[17:26] <kenvandine> andyrock: and once it would happen the shell was all out of whack
[17:27] <kenvandine> the appindicators didn't show any more
[17:27] <kenvandine> and the dock wouldn't show running apps
[17:27] <andyrock> yeah that's because gnome-shell expects an extension to unload correctly
[17:27] <andyrock> there is no mechanism of protection in case this is not true
[17:28] <andyrock> once it happens your shell is in an undefined state
[17:29] <willcooke> Should we sru that fix to B?
[17:29] <andyrock> willcooke: it's on my list
[17:29] <willcooke> cool, thanks andyrock
[17:29] <kenvandine> and 18.10 please :)
[17:29] <andyrock> I proposed a C branch will ping the right people to get in C before and then we can backport to B
[17:30] <kenvandine> andyrock: thanks
[17:30] <andyrock> kenvandine: try not to change your configuration too much so we can debug it in Malta if you're going to be there
[17:30] <andyrock> :D
[17:30] <kenvandine> andyrock: sure
[17:31] <andyrock> it's not easy to fix those reference issues without being able to interactively debug them
[18:07] <Laney> laters, see you monday
[18:07] <Laney> #christmasshopping
[18:07] <ovrh> Hello! I've been sent here to ask for help to report a bug with the snap version of gnome-system-monitor... which made me worry it might be an actually hard process, so here I am
[19:40] <willcooke> ovrh, hi!  Can you report it against this: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+filebug
[19:40] <willcooke> and mention that it's the snap
[19:40] <willcooke> and let me know the bug number
[19:42] <ovrh> willcooke, Thank you, will do! I was not sure if I should have reported it on launchpad, gnome, or somewhere else. I'll send you the bug # when I've prepared it
[19:42] <sarnold> I think "the" solution for bug reports isto email whoever is listed as the snap owner
[19:43] <willcooke> sarnold, there was talk of adding something to the description of the snap, or to the contact field, can't remember which.  kenvandine do you remember? ^
[19:44] <willcooke> sarnold, this might be a bit special since they're kinda "main" snaps
[19:45] <ovrh> sarnold, That would be Canonical, I doubt I can email them directly
[19:46] <kenvandine> yeah
[19:46] <kenvandine> we need to add a URL
[19:46] <sarnold> url would be much appreciated :) this is far from the first time someone's had trouble reporting a bug against a snap :(
[19:46] <kenvandine> to the contact field
[19:46] <kenvandine> yeah
[19:46] <kenvandine> also, it would be really cool of ubuntu-bug could report a bug against a snap
[19:47] <sarnold> yes
[19:47] <sarnold> but if snaps are going to live elsewhere too, at minimum an url would be nice, since not all publishers are going to want to put up an email address :)
[19:47] <kenvandine> yeah, email doesn't make sense
[19:48] <kenvandine> we want real bug tracking
[20:47] <willcooke> night asll
[20:47] <willcooke> all
[21:06] <ovrh> willcooke, Here's the bug report for when you'll be online again: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1808420 thanks again for the help.
[21:08] <sarnold> ovrh: nice; I suggest adding the pastes and image to the bug report directly, so it's not dependant upon external sites
[21:08] <sarnold> ovrh: thanks for filing the bug
[21:10] <ovrh> sarnold, Will do. Is there any formatting supported? I see markdown didn't exactly work
[21:11] <sarnold> ovrh: no :( attachments are best if th formatting really matters, but probabyl just a standard comment is sufficient to convey "there's a lot of mounts on this thing"