[06:38] <oSoMoN> good morning desktoppers
[06:49] <duflu> Morning oSoMoN
[06:57] <oSoMoN> hey duflu, had a good week-end?
[06:58] <duflu> oSoMoN, yeah, not bad. You?
=== pstolowski|afk is now known as pstolowski
[07:04] <oSoMoN> yeah, a productive and relaxing week-end
[07:09] <tjaalton> terminator has somewhat transparent borders, anyone seen that?
[07:42] <willcooke> morning all
[07:48] <duflu> Morning willcooke
[07:48] <duflu> It's quiet here
[07:48]  * willcooke looks at the holiday calendar
[07:49] <oSoMoN> good morning willcooke
[07:50] <willcooke> hey oSoMoN
[07:50] <oSoMoN> Pentecost might be a national holiday in several countries
[07:50] <oSoMoN> here it's not a national holiday, but it might be a local one depending on where you live
[07:51] <willcooke> Seems it is in France
[07:51] <willcooke> Da'cour
[07:52] <willcooke> Also big in Ivory Coast and Iceland
[08:03] <ackk> hi, after latest updates on bionic I'm seeing a weird behavior. every ~3s, i have a very short screen "freeze", which is mostly noticeable when moving the mouse or typing. I'm not sure how can I debug what's causing it. any ideas?
[08:04] <Trevinho> Morning
[08:04] <Laney> |O|
[08:06] <willcooke> ackk, anything in the logs?  Are you running Wayland or X (probably doesnt matter).  might be useful to have top open to see if something jumps to 100% CPU when it freezes
[08:07] <ackk> willcooke, noting relevant in dmesg, and no cpu jumps that I can see. I'm running Wayland
[08:07] <ackk> willcooke, (and a plain GNOME session, if that could matter)
[08:07] <ackk> willcooke, the freeze is very brief, the machine is usable but it's noticeable especially when you move the mouse
[08:07] <willcooke> ackk, shouldnt matter.  Give X a go and see if it does the same thing?  That might narrow it down at least.  Syslog is likely to have more useful info that dmesg
[08:08] <ackk> willcooke, oh, you're right I see https://paste.ubuntu.com/p/Nmx4JHJrrY/ in syslog
[08:09] <ackk> willcooke, that's repeated. I wonder if system-monitor is the cause
[08:09] <ackk> oddly, it seems to work properly
[08:09] <willcooke> it probably restarts quick enough that you dont notice (apart from perhaps the freeze)
[08:09] <duflu> ackk, bionic right? I see the same problem on every machine I install cosmic on (so far)
[08:09] <ackk> duflu, yes bionic
[08:09] <ackk> willcooke, yes, it seems to be it
[08:10] <ackk> willcooke, I had seed a similar error in the past but I thought that was fixed?
[08:10] <ackk> (about trying to access deallocated objects)
[08:11] <ackk> sigh, it seemed they had fixed the plugin to work with bionic's gnome
[08:12] <ackk> willcooke, thanks for the tip, at least the issue doesn't show anymore
[08:14] <willcooke> ackk, np
[08:34] <Laney> Trevinho: hey, can you look into those comments on the gdm thing please?
[08:34] <Laney> also, how was your weekend in london?
[08:34] <Laney> the great weather continues
[08:35] <Trevinho> Laney: yes, I will. i noticed those last friday
[08:35] <Trevinho> Laney: great i was able to see many friends living here... I always love London, eventually :-)
[08:35] <Laney> \o/
[08:36] <Laney> are you in the office?
[08:38] <Trevinho> not yet.. Heading in a bit.
[08:39] <Trevinho> what about you?
[08:40] <Laney> yeah was nice, didn't do anything special just hanging around here
[08:41] <Laney> sowed some more sweetcorn and courgettes/squash ;-)
[08:41] <Laney> gourdgeous
[08:46] <popey> willcooke: remember I mentioned full screen windows on 2nd monitor have no controls? Seems it's only firefox. Can you reproduce?
[08:47] <popey> (perhaps this new funky CSD stuff in FF60)
[08:51] <willcooke> popey, testing
[08:51] <willcooke> works
[08:51] <popey> sorry, I said "full screen" I mean "maximised"
[08:51] <willcooke> at least I think it does
[08:53] <willcooke> popey, https://imgur.com/a/btYlgbP
[08:54] <popey> huh. I must have some reminant of unity kicking around, as you suggested. I still have my window controls on the left for example.
[08:54] <willcooke> yeah I think it's a Unity hangover
[08:54] <willcooke> but no idea what
[08:54] <popey> hm. is there a gnome shell dconf reset magic thing?
[08:55] <xnox> unity-default-settings or some such, maybe touch default settings?
[08:56] <willcooke> morning xnox
[09:19] <popey> willcooke: some judicious file removal and dconf resets fixed it, thanks!
[09:22] <willcooke> popey, woot!
[10:25] <popey> Where should I filed bugs which affect only the snap of firefox and not the deb?
[10:28] <xnox> willcooke, can seeded-snaps knowledgeable people review branches attached to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1767896 ? looks like seeded snaps missing a "dependency"
[10:28] <ubot5> Ubuntu bug 1767896 in OEM Priority Project "Live 18.04 with broken seed causes snapd high CPU usage" [Critical,Confirmed]
[10:30] <Laney> xnox: you can merge those
[10:37] <xnox> Laney, ok. but i don't quite understand it. I thought that there are no dependencies between snaps... and how would existing installs gain the dep?
[10:37] <xnox> do we need to respin desktop isos?
[10:37] <xnox> are there any other missing deps?
[10:38] <Laney> xnox: I think comment 13 and 15 answer your questions
[10:38]  * xnox rereads
[10:39] <xnox> ah, thanks
[10:43] <Laney> :>
[10:49] <duflu> xnox, watching the logs in a cosmic live session I got the impression that was causing frequent and short shell freezes/stutter. Would that be right?
[10:49] <duflu> Or Laney ^
[10:50] <Laney> If it's as CPU intensive as it says, could be...
[10:50] <Laney> see if it stops when that missing snap gets installed?
[10:50] <duflu> Yeah. Also I need to log off
[10:50] <duflu> Night
[11:38] <oSoMoN> popey, re firefox snap bugs (sorry I missed the question): https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox
[11:38] <popey> ok
[11:38] <popey> ta
[11:38] <oSoMoN> yw
[11:45] <popey> oSoMoN: https://bugzilla.mozilla.org/show_bug.cgi?id=1463091
[11:45] <popey> :)
[11:45] <ubot5> Mozilla bug 1463091 in Untriaged "snap links do not work in the firefox snap" [Normal,Unconfirmed]
=== pstolowski is now known as pstolowski|lunch
[12:02] <oSoMoN> popey, thanks
=== pstolowski|lunch is now known as pstolowski
[13:08] <Laney> GunnarHj: I'm going to upload your dh-translations to cosmic now, thanks for that
[13:08] <Laney> suggest watching things over the next little while before you decide on SRUing anything?
[13:32] <GunnarHj_> Laney: Yay! Right, I'll coordinate with jbicha about a possible SRU.
[13:34] <Laney> GunnarHj_: Why weren't icons and keywords stripped before?
[13:34] <Laney> I hope there's not some place that isn't using a library to read those...
[13:37] <GunnarHj_> Laney: No idea to be honest. Assuming it was a oversight.
[13:37] <Laney> guess we'll find out :-)
[13:37] <Laney> I personally probably wouldn't try to SRU that bit
[13:38] <Laney> it is up
[13:38] <GunnarHj_> Laney: We have stripped those for g-c-c during a few months now (via d/rules), and I haven't heard about any issues.
[13:39] <Laney> OK, but SRUs are about minimising risk and this seems to not minimise it
[13:39] <GunnarHj_> Laney: Indeed. That part is indeed not important enough for SRUing.
[13:40] <Laney> Anyways, lets see how it goes in cosmic for a bit
[13:40] <Laney> merci beaucoup!
[13:40] <GunnarHj_> Laney: Thank you for providing guidance and sponsorship!
[13:59] <xnox> Laney, so we did not get to the bottom of what creates the serial-getty@ wants symlink, have we?
[14:00] <xnox> Laney, should I email foundations-crew & server-crew to figure it out?
[14:08] <tseliot> Laney: hi, do you know if there is a recommended way to SRU a fix for pulseaudio (in bionic)? Shall I commit my changes in the git branch for cosmic first?
[14:11] <tseliot> xnox: I might need to backport some fixes for logind too about this problem, when I have the time (it should be about 3 commits) https://github.com/systemd/systemd/issues/8393
[14:11] <ubot5-ng> systemd bug 8393 in systemd "DRM devices opened by logind stay referenced indefinitely by PID 1" (comments: 2) [Closed]
[14:11] <ubot5> bug 8393 in openoffice.org (Ubuntu) "RTF documents not associated to OOO" [Medium,Fix released] https://launchpad.net/bugs/8393
[14:26] <xnox> tseliot, bug report with SRU template and commit ids from upstream repo to backport; and I can handle an sru backport.
[14:27] <tseliot> xnox: great, I'll do that. Thanks
[14:33] <Laney> xnox: nope - you can do if you like, I was hoping stgraber would turn up but maybe he was off
[14:33] <Laney> tseliot: I'm not familiar with pulseaudio in particular, but the bug should be fixed in cosmic too, yeah
[14:34] <tseliot> Laney: ok, I'll try to do as the previous uploaders did, and hope for the best. Thanks
[14:35] <Laney> tseliot: if there's not a branch, making one for bionic wouldn't be a bad idea
[14:35] <Laney> and then update that in debian/control
[14:37] <tseliot> Laney: they have an ubuntu-bionic branch https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/log/?h=ubuntu-bionic
[14:37] <Laney> sweet
[14:37] <tseliot> I think I'll use the "ubuntu" branch first, for cosmic, and then I'll use "ubuntu-bionic" for the SRU
[14:38] <Laney> makes sense
[14:38] <tseliot> finally fixing LP: #405294 would save us a lot of a pain
[14:38] <ubot5> Launchpad bug 405294 in pulseaudio (Ubuntu) "A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]" [High,Triaged] https://launchpad.net/bugs/405294
[14:44] <Laney> ♥
[14:44] <tseliot> :)
=== pstolowski is now known as pstolowski|afk
[16:43] <oSoMoN> have a good evening everyone!
[17:16] <GunnarHj_> sil2100: Thanks for taking on the missing codeset bug. Then I don't need dev hunting for that one. :)
[17:24] <GunnarHj_> Laney: I got a build fail msg about pkgbinarymangler. Did you request a rebuild?
[17:25] <Laney> GunnarHj_: Yeah looks like the tests aren't 100% great
[17:25] <GunnarHj_> Laney: I see. Success now anyway.
[19:46] <willcooke> night all