[06:58] <didrocks> good morning
[07:23] <duflu> Morning didrocks
[07:29] <didrocks> hey duflu
[07:51] <oSoMoN> good morning desktoppers
[08:07] <seb128> gooood morning desktopers
[08:08] <duflu> Morning oSoMoN and seb128
[08:08] <seb128> hey duflu, how are you? had a good w.e?
[08:08] <seb128> lut oSoMoN
[08:09] <duflu> seb128, sore from excessive weeding :) And also have a trio of birthdays... You?
[08:10] <seb128> I'm good, we had a (mostly) relaxing w.e
[08:10] <seb128> we went to see the 'Cirque du soleil' on saturday which was very nice
[08:11] <duflu> That's usually great!
[08:13] <oSoMoN> salut seb128
[08:13] <oSoMoN> hey duflu
[08:22] <didrocks> hey oSoMoN, seb128
[08:23] <seb128> lut didrocks, oSoMoN, did you have a good w.e?
[08:23] <didrocks> was good, thanks!
[08:24] <oSoMoN> yeah, bbq in the sun on Saturday, and welcome party for new families at the school on Sunday, a very good week-end
[08:24] <seb128> nice
[08:28] <duflu> Ugh, I meant "had" not "have", obviously
[08:36] <jibel> on focal, gnome-shell hand when I press a shortcut eg ctrl+alt+t, anyone seen that?
[08:37] <jibel> hm, and now I cannot log in
[08:39] <seb128> I'm not using focal yet, still have eoan SRUs and fixing to do and focal opening hasn't even be announced yet
[08:40] <seb128> I would recommend against using it before at least the initial sync went through and thing have a chance to settle down a bit
[08:43] <jibel> yeah but the machine didn't boot in eoan, so I had to try focal
[08:47] <marcustomlinson> morning desktoppers
[08:47] <oSoMoN> good morning marcustomlinson
[08:47] <didrocks> hey marcustomlinson
[09:02] <Laney> hi ho
[09:02] <RAOF> And a fine day to you too, Laney!
[09:04] <duflu> Morning jibel, marcustomlinson and Laney. Evening RAOF
[09:06] <seb128> hey Laney, marcustomlinson, how are you? had a good w.e?
[09:06] <seb128> no willcooke anymore in that round of greetings, feeling weird
[09:11] <Laney> hey RAOF duflu seb128
[09:11] <Laney> i'm doing alright thanks!
[09:12] <Laney> went away with friends for the weekend, was nice
[09:12] <Laney> the place we were staying had cats
[09:12] <didrocks> hey Laney ;)
[09:13] <RAOF> For some reason that sounds like “the place had vermin” 😀
[09:14] <RAOF> But I presume that's not the intended reading!
[09:14] <Laney> try as I might, I can only read it as a delightful experience
[09:14] <Laney> yo didrocks
[09:15] <Wimpress> Morning o/
[09:17] <duflu> Morning Wimpress
[09:20] <seb128> hey Wimpress, how are you today? had a good w.e?
[09:20] <didrocks> hey Wimpress
[09:37] <Wimpress> Yep, good weekend thanks. Filled with Lego and swimming 🙂
[09:38] <Wimpress> And you?
[09:39] <seb128> w.e was good
[09:40] <seb128> went to see the 'cirque du soleil' on saturday, impressive show, I recommend it if you have the opportunity
[09:42] <Wimpress> Ooh. Something I've wanted to see.
[09:45] <seb128> :-)
[09:49] <marcustomlinson> oooh fancy
[10:01] <duflu> 🎪
[10:33] <Wimpress> https://lists.ubuntu.com/archives/ubuntu-devel/2019-October/040834.html
[10:33] <Wimpress> Had a bit of turbo lag this morning.
[10:34] <Wimpress> Helping pack the car, my girls are going away for a few days.
[10:47] <didrocks> popey: hey! zsys fix should now be published on https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/zsys/+packages, I changed the bug description with the 2 use cases (for people being impacted and people installing the fixed version directly). Tested locally and it works. Would welcome a confirmation :)
[10:48] <didrocks> I managed to get both use cases addressed (uploaded to focal already)
[10:53] <Laney> did we rls the bug about the wrong audio device being selectd?
[10:53] <Laney> ah yeah, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 cool
[10:56] <popey> didrocks: on it
[10:59] <didrocks> thanks :)
[11:01] <popey> didrocks: confirmed and commented
[11:01] <Laney> AH
[11:01] <Laney> perhaps that is what was breaking the firefox thing I whined about last week
[11:02] <didrocks> popey: thanks! (and I tested on a broken system, dancing on a tty and upgrading, and it works as well) :)
[11:02] <popey> Thanks for the quick fix
[11:02] <didrocks> uploading to eoan-proposed once autopkgtests for focal pass
[11:02] <didrocks> thanks for finding this!
[11:02] <popey> np. sorry for ruining your monday :D
[11:02] <didrocks> haha, well, better for having it spotted ;)
[11:03] <seb128> Laney, wasn't your about streams being muted?
[11:04] <Laney> might just be that they were outputting on the hdmi device
[11:04] <Laney> and that is how this situation is represented in g-c-c
[11:04] <Laney> last comment on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/749
[11:09] <seb128> yeah, could be I guess, though in theory there is no reason they should show as muted if they output on another port ... I guess we fix the first bug and see if the other one is still an issue
[11:10] <Laney> dunno how it works
[11:10] <Laney> but if it's like this it would make complete sense to me
[11:11] <Laney> send to one output -> 0 volume on the others
[11:12] <seb128> Ah, seen like that
[11:13] <seb128> I was expecting non-active-device to just not be listed but it's another valid way to have them showing but having the sound to 0
[11:18] <Laney> I'll just try turning off that module
[11:23] <Laney> if the theory is true then I think g-c-c / gnome-shell got confused about the state because they were still controlling line out
[11:24] <Laney> so maybe it doesn't make sense :-)
[13:02] <clobrano> hey all 0/
[13:03] <seb128> hey clobrano, how are you? how was your weekend?
[13:03] <clobrano> hey seb128, I'm fine, and the we was good, I went yesterday to see some stars and planets with ta telescope :D
[13:04] <clobrano> seb128, how about you?
[13:04] <seb128> I'm good, w.e was nice, we want to see the 'cirque du soleil' which was a nice show, otherwise some small works in the house and relaxing time
[13:05] <seb128> weather also starts being cold here, going to almost freeze at night this week brrrrr
[13:09] <clobrano> wow, I'd love to see the Cirque to soleil
[13:13] <clobrano> I think I broke something on yaru's deb package with this https://github.com/ubuntu/yaru/pull/1578as reported here https://github.com/ubuntu/yaru/issues/1591
[13:13] <clobrano> The PR above changes the installation path to /usr/share/themes/Yaru/gnome-shell and creates a symlink to /usr/share/gnome-shell/themes/YaruDid I miss to update something in the Yaru/debian folder?
[13:15] <marcustomlinson> hey clobrano
[13:15] <seb128> clobrano, https://github.com/ubuntu/yaru/blob/master/debian/yaru-theme-gnome-shell.postinst
[13:16] <seb128> is the css from line 7 still existing on disk?
[13:18] <clobrano> seb128, yes it exists
[13:18] <clobrano> but I thought that the installation script would create the symlink as installing from source does
[13:18] <clobrano> and then I expected the path to exist
[13:19] <seb128> it seems to not exist in the deb
[13:19] <seb128> how do you do the symlink?
[13:19] <seb128> didrocks ^ you probably know their build machinery better than me, maybe you know directly what's wrong?
[13:21] <clobrano> the symlink is made here https://github.com/ubuntu/yaru/blob/master/gnome-shell/src/install-shell.sh, as  meson's install script meson.add_install_script('install-shell.sh', meson.project_name())
[13:28] <seb128> clobrano, from https://launchpadlibrarian.net/448541820/buildlog_ubuntu-bionic-amd64.yaru-theme_19.10.4+201910260248+04f5461~ubuntu18.04.1_BUILDING.txt.gz
[13:28] <seb128> lrwxrwxrwx root/root         0 2019-10-26 02:48 ./usr/share/gnome-shell/theme/Yaru -> ../../themes/Yaru/gnome-shell
[13:33] <seb128> clobrano, I didn't debug on a real system and might be overlooking something but one reason could be that the target doesn't exist because the other package isn't installed (yet)
[13:35] <seb128> is that file new in the other deb? in which case it might be that you need to ensure the target is installed first
[13:35] <seb128> the g-s binary should at least Depends on the binary which ships the symlink target
[13:39] <seb128> marcustomlinson, I guess you have been pinged about that/it's on our backlog, but you are looking at the focal/libreoffice/autopkgtest failure?
[13:40]  * clobrano checking the file
[13:41] <marcustomlinson> seb128: I may have been pinged and missed it... I've been away since Wednesday, let me check excuses
[13:41] <seb128> marcustomlinson, new cycle opening so half of the world changed
[13:41] <clobrano> seb128, yes this symlink is new and in fact, /usr/share/themes/Yaru is created by the gtk part
[13:41] <seb128> marcustomlinson, http://autopkgtest.ubuntu.com/packages/libr/libreoffice/focal/amd64
[13:42] <clobrano> seb128, installing first yaru gtk deb and then yaru shell deb it seems to work on my VM, not on the guy who opened the bug, don't know why
[13:44] <seb128> clobrano, I've asked for some debug details on the issue, let's see
[13:44] <clobrano> seb128, thanks!
[13:45] <seb128> marcustomlinson, you probably got bitten by some depends changing while the world was being replaced behind your feet
[13:52] <seb128> oSoMoN, https://trello.com/c/cbm9DllY/237-thunderbird-6812-update and https://trello.com/c/UnkgODhV/244-thunderbird-6820-update should we merge the card or do you still plan to go through .1 first?
[13:55] <oSoMoN> seb128, I'll jump directly to 68.2, so the 68.1.2 card can be marked done, as it's already in eoan and focal
[13:55] <seb128> oSoMoN, k, thx, let me know if you want me to do the trello triage or if you do it
[13:59] <oSoMoN> I'll do it, thanks
[13:59] <seb128> oSoMoN, thx
[14:10] <didrocks> clobrano: seem, you mostly figured it out, correct? Do not hesitate if you need me
[14:21] <clobrano> didrocks, probably :D, otherwise I'll ping you later
[14:57] <hellsworth> good morning everyone
[14:57] <kenvandine> good morning hellsworth
[14:58] <hellsworth> kenvandine: did you resolve your linker issue?
[15:01] <marcustomlinson> morning kenvandine and hellsworth
[15:04] <kenvandine> hellsworth: no...
[15:04] <kenvandine> i decided to try gnome-calculator as a first example instead :)
[15:05] <kenvandine> but that's failing to find valac
[15:05] <hellsworth> the staple test app :)
[15:05] <kenvandine> however... it's there
[15:05] <hellsworth> interesting
[15:05] <kenvandine> meson.get_compiler(valac) fails
[15:05] <hellsworth> i'm picking back up with gnome-clocks, tyring to get a consistent failure
[15:05] <hellsworth> hmm
[15:05] <kenvandine> cool
[15:06] <kenvandine> not sure how this works in marcustomlinson's snap and fails here :)
[15:06] <kenvandine> i'll get back to it in a bit
[15:06] <hellsworth> maybe it's some general path problem since gnome-3-34-1804-sdk def builds vala
[15:06] <kenvandine> it's in the PATH we set in build-environment
[15:06] <marcustomlinson> I'm just magic
[15:06] <kenvandine> but i'm not sure how meson finds valac
[15:06] <hellsworth> s/marcus/merlin/
[15:07] <kenvandine> might not be checking the path
[15:07] <kenvandine> i'm working on something else this morning, will get back to it in a bit
[15:08] <hellsworth> sounds good
[15:09] <marcustomlinson> hellsworth: what's the issue? meson not finding vala with the gnome-3-34-1804-sdk build snap?
[15:09] <kenvandine> marcustomlinson: yes
[15:10] <ricotz> meson respects a VALAC envar pointing the valac executable
[15:10] <kenvandine> ricotz: thanks!
[15:10] <kenvandine> marcustomlinson: here's my expanded yaml
[15:11] <kenvandine> https://paste.ubuntu.com/p/rywF3nPjH9/
[15:12] <marcustomlinson> kenvandine: see line 71 - gnome-3-32-1804-sdk should be gnome-3-34-1804-sdk
[15:12] <marcustomlinson> x4
[15:14] <kenvandine> oh geez, missed one :)
[15:38] <seb128> tjaalton, hey, sorry that took a bit, but I've added  intel-gmmlib, intel-media-driver, intel-compute-runtime to https://people.canonical.com/~platform/desktop/xorg.html now
[16:00] <RikMills> o/ popeytesting
[16:02] <tomreyn> not registered :)
[16:03] <tjaalton> seb128: cool, thanks
[16:11] <tjaalton> seb128: looks like it's checking against eoan and not focal?
[16:12] <seb128> tjaalton, yeah, that was just fixed, next refresh should have it
[16:12] <tjaalton> ah
[16:12] <seb128> sorry :)
[16:12] <tjaalton> heh, there's time
[16:20] <seb128> Laney, do you know of any example of a package that opt-ed out of systemd-auto-enablement created by dh_installsystemduser? or how to do that best?
[16:21] <Laney> seb128: doesn't it have a parameter to do that?
[16:21] <Laney> yeh, --no-enable, is that what you want?
[16:22] <seb128> Laney, that works for new installs but isn't going to disable it for upgraders
[16:22] <seb128> it's just removing the snippet that does the enablement from postinst
[16:22] <Laney> oh, didn't understand that you wanted to fix up existing systems
[16:22] <seb128> I guess I need to copy the prerm snippet to the postinst of the new package or something
[16:24] <Laney> guess you get to call deb-systemd-helper disable
[16:24] <Laney> or whatever it is
[16:25] <seb128> the autogenerated postrm does
[16:25] <seb128> deb-systemd-helper --user mask ...
[16:25] <seb128> on remove
[16:26] <seb128> and
[16:26] <seb128> deb-systemd-helper --user purge
[16:26] <seb128> deb-systemd-helper --user unmask
[16:26] <seb128> on purge
[16:26] <Laney> not sure what these commands do exactly
[16:26] <seb128> I guess I want to purge/unmask if I want to pretend the enablement never happened?
[16:29] <seb128> Laney, thx, last question for now ... any opinion on what's the right maintainer script to do the cleaning? preinst of the new package?
[16:31] <Laney> postinst probably, then you don't have to worry about if the dependencies are right
[16:31] <Laney> probably before #DEBHELPER# and guarded by a version chekc for only only upgrades from the buggy versions
[16:32] <Laney> s/dependencies/pre-dependencies/
[16:32] <seb128> Laney, thx
[16:39] <kenvandine> hellsworth, marcustomlinson: I have gnome-calculator built with the gnome-3-34 extension and the build snap
[16:40] <marcustomlinson> \o/
[16:41] <hellsworth> nice!!
[17:00] <hellsworth> kenvandine: would you mind pelase sharing with me your calculator yaml?
[17:00] <hellsworth> maybe it will help me with clocks
[17:00] <kenvandine> hellsworth: evince built too
[17:01] <hellsworth> wow that's great to hear!
[17:03] <kenvandine> marcustomlinson: trying to open the about dialog in evince built with the gnome-3-34-1804 build crashes the same way drawing is
[17:03] <kenvandine> hellsworth: https://paste.ubuntu.com/p/Wj72kJk8tq/
[17:05] <kenvandine> hellsworth: and my diff to your extension https://paste.ubuntu.com/p/XJ5S2qh2tg/
[17:06] <kenvandine> hellsworth: we should refactor the platform and build snap paths out into a variable
[17:06] <kenvandine> so it can be more easily updated for the next version
[17:08] <hellsworth> ken thanks! i only see build snap paths (which we can def put in a var).
[17:09] <marcustomlinson> kenvandine: yeah sorry haven't gotten to the bottom of that yet. I did try a build of gnome-3-34-1804 last week and same issue with epiphany
[17:15] <kenvandine> hellsworth: look closely, it's both build snap and platform snap paths :)
[17:16] <hellsworth> ah ok i see the platform snap path wayy down the LD_LIBRARY_PATH line :)
[17:17] <kenvandine> yeah
[17:17] <kenvandine> marcustomlinson: correction... not opening the about dialog but opening the menu
[17:17] <hellsworth> when should you use build-snaps to point to the build snap? any part that would include build-packages that is already built by the build snap?
[17:18] <kenvandine> yes
[17:18] <hellsworth> mkay
[17:21] <marcustomlinson> kenvandine: why does the build environment need to know anything about the platform contents?
[17:22] <kenvandine> marcustomlinson: something i was planning to talk to you about
[17:22] <kenvandine> there are libs in the runtime that aren't in the build snap
[17:22] <kenvandine> which is odd
[17:23] <marcustomlinson> possibly from stage-packages
[17:23] <kenvandine> yeah, we should probably stage them in the build snap too
[17:23] <kenvandine> but
[17:24] <kenvandine> snapcraft does ensure the platform snap is installed during the build
[17:24] <kenvandine> so it might be fine
[17:25] <marcustomlinson> might as well move whatever is staged that is needed for build over
[17:25] <marcustomlinson> those find -exec rm commands ensure the dups are dealt with so _should_ be simples
[17:42] <oSoMoN> popey, shall I mark bug #1850174 invalid, or is there something you wanted me to look into?
[17:43] <popey> Yes please
[17:43] <popey> Sorry, I should have
[17:44] <oSoMoN> np, thanks
[18:09] <kenvandine> marcustomlinson: so yet another victim of the crasher you are hunting.  it seems everything that uses gtk crashes when build with either gnome-3-32-1804 or gnome-3-34-1804
[18:10] <marcustomlinson> yeah :/ a little less than ideal
[18:11] <marcustomlinson> kenvandine: I'll hit this head on tomorrow, got a little distracted with libreoffice autopkgtests
[18:11] <kenvandine> no worries
[18:12] <kenvandine> well, at least it's obviously broken
[18:12] <marcustomlinson> right
[18:12] <kenvandine> not subtle runtime issues
[18:14] <hellsworth> kenvandine: i had to restart my system so i missed it.. what is the other victim of the same crasher? clocks?
[18:16] <marcustomlinson> hellsworth: I think kenvandine was still referring to the evince crash
[18:16] <kenvandine> yeah... evince
[18:16] <kenvandine> it starts the app though
[18:16] <hellsworth> ah ok thanks
[18:16] <kenvandine> i think this is something related svg loading
[18:17] <marcustomlinson> kenvandine: If you switch to highcontrast theme it will probably not crash
[18:17] <hellsworth> oh right some themes caused the crash while others didn't
[18:18] <marcustomlinson> any theme with svg icons is the guess
[18:18] <kenvandine> marcustomlinson: confirmed, works with highcontrast
[18:18] <marcustomlinson> alright good to know it's the same issue and not a new one at least
[18:19] <kenvandine> same for calculator
[18:19] <kenvandine> it crashes loading the about dialog
[18:19] <kenvandine> it's fine until then
[20:28] <mitya57> Wimpress: hi! Can you please take a look at https://code.launchpad.net/~muktupavels/compiz/+git/compiz/+merge/374783?
[20:29] <mitya57> Ubuntu MATE no longer ships compiz, so maybe we can remove that config altogether? Or better move it to some other package?
[20:56] <jdstrand> kenvandine: hey, I know that firefox isn't our snap, but I'm wondering if you've seen the issue where on 19.10 wayland, firefox works fine and has proper theming in one profile, but not another
[21:15] <kenvandine> jdstrand: i haven't used wayland recently
[21:30] <popey> robert_ancell: why does ubuntu software have two login options in the burger menu? Is this a known bug? It was like this on 19.04 and 19.10 too
[22:04] <robert_ancell> popey, hmm, the Ubuntu One login should be unused since we switched to ODRS I think? I hadn't noticed that, thanks for pointing out.