[01:52] <kenvandine> amurray: PR submitted for communitheme-light https://github.com/ubuntu/yaru/pull/1568
[01:52] <gitbot> ubuntu issue (Pull request) 1568 in yaru "When building with communitheme_compat, link the light variant" [Open]
[01:53] <kenvandine> amurray: thanks for using the communitheme :)
[03:26] <amurray> kenvandine: if I wasn't such a curmudgeon I would have upgraded my bionic install already but in the meantime it's the only way to get recent yaru goodness
[03:27] <amurray> kenvandine: thanks for making it awesome'
[03:29] <jamesh> you could always pin the yaru-theme-gtk package from a newer release
[03:33] <amurray> jamesh: true
[03:57] <kenvandine> hey jamesh
[04:04] <jamesh> hi kenvandine
[05:19] <amurray> kenvandine: I can confirm the new candidate build of gtk-common-themes works with communitheme-dark - will wait on your new PR landing for -light - thanks again
[06:05] <oSoMoN> good morning desktoppers
[06:05] <duflu> Morning oSoMoN
[06:09] <oSoMoN> hey duflu
[06:14] <didrocks> good morning
[06:16] <duflu> Hi didrocks
[06:16] <didrocks> hey duflu
[06:19] <Wimpress> o/
[06:21] <RikMills> Laney etc al. Kubuntu manual partition seems ok with new ubiquity. Thanks for the fix :)
[06:21] <RikMills> *et al
[06:27] <jibel> RikMills, yw
[06:29] <duflu> Morning jibel
[06:29] <duflu> And good morning Wimpress
[06:29] <jibel> hi duflu and all
[06:29] <didrocks> hey Wimpress
[06:30] <oSoMoN> salut didrocks
[06:30] <oSoMoN> hey Wimpress
[06:30] <oSoMoN> salut jibel
[06:32] <didrocks> hey oSoMoN
[06:34] <dupondje> oSoMoN: thanks for checking that Thunderbird Dictionary bug :)
[07:07] <clobrano> kenvandine, hey thanks for the PR
[07:07] <clobrano> and, hello everyone 0/
[07:08] <seb128> gooood morning desktopers
[07:14] <duflu> Morning seb128
[07:14] <seb128> hey duflu, how are you?
[07:15] <duflu> seb128, going well, and busy. Three of my release bugs require simultaneous attention today ;)
[07:15] <duflu> How are you seb128?
[07:15] <seb128> duflu, I'm good!
[07:15] <seb128> duflu, the fftw3 issue is weird, the source didn't change and it started failing :-/
[07:16] <didrocks> hey seb128
[07:16] <seb128> also it's armhf only
[07:16] <seb128> hey didrocks, how are you?
[07:16] <didrocks> I'm fine, thanks, you?
[07:16] <duflu> seb128, yeah I am digging deeper so won't confuse the situation by posting any guesses right now
[07:17] <seb128> didrocks, jibel, how do you watch zfs related issues? I crossed a bunch yesterday when triaging recent report and subscribed you, unsure if that works for you or if you would prefer tagging or something else instead?
[07:17] <seb128> duflu, k
[07:17] <seb128> didrocks, I'm good :)
[07:17] <didrocks> seb128: yeah, that's fine for me. However, for the installer ones, those are mostly dups
[07:17] <didrocks> and we have annoying users when you repeat the same thing over and over again on bugs :/
[07:17] <didrocks> but otherwise, feel free to subscribe us, that's helpful
[07:18] <seb128> good, thx
[07:19] <duflu> seb128, I did however spend half the weekend finding my armhf hardware is now too old to be useful
[07:19] <jibel> seb128, i'm tracking installer related components on lp. you can  always subscribe me too
[07:19] <duflu> So that was interesting
[07:19] <seb128> jibel, hey, good :)
[07:20] <seb128> duflu, :-/ we have those canonistack instance which are handy
[07:20] <duflu> Yeah. I also have a working VM.
[07:20] <seb128> duflu, I'm not sure if that armhf issue is worth spending too much time on though
[07:20] <seb128> I wonder if building with O1 would make a difference/be a workaround
[07:20] <duflu> I may be able to propose a fix "quickly" based on what I have seen. But will take time to confirm
[07:21] <seb128> k
[07:22] <seb128> so I did a daliy install yesterday using custom partitioning
[07:23] <seb128> the details screen listed 0Mb partition in between each real partition which looked a bit weird, I wonder if that's a new issue or normal behaviour I never noticied/didn't remember (I also have more partitions on that test machine now than I had before so maybe that makes a difference)
[07:23] <duflu> Also good news - eoan seems to have fixed a touchpad bug on a laptop I thought was faulty till now
[07:24] <seb128> duflu, ah, nice when bugs autoresolve themselves with updates :)
[07:24] <duflu> Yeah everyone hopes for it but really it practically never happens
[07:25] <seb128> didrocks, jibel, do you also watch zfs-utils? e.g bug #1847325 got reported that sound like installer issue
[07:26] <didrocks> you mean zfs-linux?
[07:26] <jibel> seb128, yes and it's our friend again
[07:26] <didrocks> but yeah, this is the dup
[07:26] <seb128> didrocks, obviously :p
[07:26] <seb128> ah, you made a friend? nice :)
[07:26] <didrocks> yeah, the one I was referring above ^
[07:27] <didrocks> reporting xxx different various of the same issues, or when you explain, reporting a bug to report what you explain when it's not one…
[07:27] <didrocks> or asking when it's going to be released on omgubuntu when you directly told him on the discourse topics few days ago
[07:28] <seb128> :/
[07:28] <didrocks> a little bit tedious
[07:34] <jibel> Laney, hi, do you think the empty /cdrom could explain that there is no kernel on the installed system?
[07:34] <jibel> xnox, ^
[07:35] <duflu> I hope bug 1845454 gets fixed in time
[07:36] <didrocks> it looks for kernel in the casper_path, so sounds like it
[07:36] <jibel> duflu, don't really have a choice, it's a showstopper for the release IMHO
[07:37] <duflu> I would agree. Seems to be a minority of machines, but still a lot of machines
[07:37] <duflu> Anyway, Seth has a fix proposed already
[07:37] <didrocks> weird that ubiquity doesn't fail on not being able to copy a kernel though
[07:40] <jibel> duflu, yeah just recent Dell machines ;)
[07:42] <seb128> who needs a kernel anyway
[07:44] <didrocks> indeed, systemd should be enough :)
[07:47] <willcooke> morning
[07:47] <seb128> hey willcooke, how are you? feeling better?
[07:48] <willcooke> hey seb128, yeah much better than yesterday thanks
[07:48] <seb128> great!
[07:49] <seb128> and brb, relocating from my morning coffee :)
[07:50] <duflu> Morning willcooke
[07:51] <willcooke> afternoon duflu
[07:52] <didrocks> hey willcooke
[07:53] <willcooke> morning didrocks
[08:09] <seb128> k, back now!
[08:09] <seb128> Laney, hey, how are you?
[08:11] <Laney> morning
[08:11] <Laney> weird internet problems but here now!!!!
[08:12] <duflu> Morning Laney
[08:12] <didrocks> hey Laney
[08:14] <Laney> hey duflu didrocks
[08:14] <willcooke> moin Laney
[08:15] <Laney> what up willcooke
[08:28] <marcustomlinson> morning desktopers
[08:28] <duflu> Hi marcustomlinson
[08:30] <seb128> hey marcustomlinson
[08:38] <didrocks> morning marcustomlinson
[08:51] <seb128> Trevinho, bonjourno ... what happened, gnome-shell having tarballs on time?! :)
[08:51] <duflu> seb128, he was still around in my morning so give him time...
[08:52] <RikMills> didrocks: I guess flavours should follow suit with this? https://launchpad.net/ubuntu/+source/ubuntu-meta/1.438
[08:53] <didrocks> RikMills: that's correct, Wimpress as well ^
[08:54] <didrocks> RikMills: feel free to hook you in to the bug
[08:54] <RikMills> didrocks: thanks. I have put that info in #ubuntu-flavors
[08:55] <didrocks> thx!
[09:45] <seb128> bah, I just did a daily install but it's not in my grub menu post reboot :/
[09:45] <Trevinho> seb128: hey... Yaz, we pinged florian in various flavors yesterday. It worked 😅
[09:46] <seb128> Trevinho, hey, well done :)
[09:46] <Trevinho> although I already found leftover bugs.
[09:46] <seb128> :(
[09:46] <Trevinho> nothing new, but they were staying there for a while.
[09:46] <seb128> when do you travel to ubucon?
[09:47] <Trevinho> and l_aney beated in handling the upgrade this morning, so... we'll get it soon
[09:47] <Trevinho> seb128: now :-).
[09:47] <seb128> ah, safe travel!
[09:47] <Trevinho> about to take off really
[09:47] <seb128> did you get the extensions bugfix updates ready?
[09:48] <seb128> ah ok
[09:48] <didrocks> seb128: missing kernel?
[09:48] <seb128> roaming from a plane which is going to take off again? ;)
[09:48] <seb128> didrocks, how do I tell?
[09:48] <Trevinho> yes waiting for one more in desktop if we can, for the others I'll upload them in a silo later this afternoon
[09:49] <didrocks> seb128: boot a live, mount the system and check its /boot
[09:49] <seb128> didrocks, looks like it yes
[09:49] <didrocks> I guess you didn't look if your install had the missing /cdrom?
[09:49] <seb128> it's a bit unfortunate :p
[09:49] <seb128> no, I just fired a daily install
[09:49] <didrocks> but reading ubiquity code, it's really taking it from /cdrom/casper
[09:50] <seb128> I wanted to test if the screen turned off during install
[09:50] <didrocks> so sounds suspiciously related
[09:50] <seb128> which it didn't
[09:50] <didrocks> short install?
[09:50] <seb128> 15 min ?
[09:50] <seb128> also I stayed on the reboot dialog for 10 min while finishing other work on the other computer
[09:50] <didrocks> hum, mine didn't take that long yesteday
[09:50] <seb128> but that was a 'install only', not live session
[09:50] <didrocks> ah
[09:51] <didrocks> I was on a live one
[09:51] <seb128> I will try that next
[09:51] <seb128> and maybe I get a kernel this time :)
[09:51] <didrocks> check /cdrom!!! :)
[09:51] <seb128> will do!
[09:51] <didrocks> if it's empty, it's a good opportunity to check the resulting fs
[09:52] <seb128> do we have a launchpad bug for the lack of kernel issue?
[09:52] <seb128> I don't see one in the recent ubiquity reports
[09:52] <didrocks> no, but we don't have one for /cdrom either
[09:52] <jibel> I tried but LP keep erroring for me
[09:52] <didrocks> so let's confirm if this is the case
[09:52] <jibel> it's the same bug
[09:52] <didrocks> and if so, I'm happy to open
[09:53] <didrocks> what's the cause of missing /cdrom? Recent casper change? (to know against which package to open the bug)
[09:53] <Laney> casper
[09:53] <Laney> the cdrom.mount inclusion
[09:53] <seb128> ah, thx
[09:53] <jibel> didrocks, here is the text of the bug I tried to file https://paste.ubuntu.com/p/k65xkq3dPs/
[09:53] <didrocks> thx jibel, filing it
[09:54] <seb128> Laney, is x_nox the one supposed to look at resolving that?
[09:54] <Laney> yes, he's been pinged about 1000000 times
[09:54] <Laney> and again this morning
[09:55] <Laney> no clear commitment to working on it though, get it rls-ed so that it is noticed in their meeting
[09:55] <didrocks> bug #1847457
[09:55] <seb128> that doesn't seem good enough at this point of the cycle
[09:55] <Laney> ok
[09:55] <Laney> that's up to you
[09:55] <seb128> willcooke, ^ can you get that escalated to foundation by some way?
[09:56]  * Laney generally hopes we can talk to each other as colleagues
[09:56] <seb128> Laney, that would be nice, but seems to not work in this case since we get no traction/reply :/
[09:57] <Laney> well he doesn't seem to be online yet today
[09:57] <Wimpress> I've subscribed the interested flavours to https://pad.lv/1847431
[09:58] <didrocks> Wimpress: saw that, thanks!
[09:58] <Wimpress> And let them know in the flavours IRC channel.
[09:58] <Wimpress> didrocks: I have a question for you.
[09:58] <Wimpress> The flavours can seed package from outside main.
[09:58] <didrocks> Hum
[09:58] <Wimpress> What do you think about the flavours seeding zsys?
[09:58] <didrocks> I see where you are going to :p
[09:59] <didrocks> there is no snapshot "command" to create zsys snapshot (and so, reveal the history menu)
[09:59] <didrocks> we can provide some guides
[09:59] <didrocks> with manual commands
[09:59] <willcooke> seb128, done
[09:59] <didrocks> and then, yeah, there are some benefits for zsys
[09:59] <didrocks> Wimpress: let's say if one flavor, like Mate, does that, it will be great
[09:59] <Wimpress> OK, cool./
[09:59] <seb128> willcooke, thx
[09:59] <didrocks> I plan to write blog posts about the benefits of adding zsys next week
[09:59] <didrocks> thanks Wimpress
[10:00] <Wimpress> I think Budgie would be interested too. Probably Ubuntu Studio.
[10:00] <didrocks> that should be fine, we have tests for it
[10:00] <Wimpress> didrocks: Advocacy are happy to assist with blog post review if you want?
[10:00] <didrocks> unfortunately, no snapshot command as being descoped…
[10:00] <didrocks> Wimpress: sounds great!
[10:00] <Wimpress> We can also schedule the social posts for any blogs you want to publish.
[10:00] <didrocks> I used to have willcooke doing the per-reviewing
[10:01] <didrocks> so other eyes are always good
[10:01] <willcooke> still happy to review
[10:01] <Wimpress> Likewise.
[10:01] <didrocks> great ;) I hope to have some starts by Monday EOD (at least pure zfs one, then another one with zsys prepped as well)
[10:05] <seb128> xnox, are you around? what's the status of that casper/cdrom problem? should we consider reverting the previous change to unbreak the ISO?
[10:25] <jbicha> seb128: can you remove mono from eoan-proposed? it looks like that will fix the libproxy/s390x build
[10:34] <seb128> doko, your mono sync in eoan-proposed is failing to build on s390x which create issues/block other things, is that ok to remove it for now?
[11:04] <RikMills> any eyes on this one? LP: #1847469
[11:05] <RikMills> I believe that report is from tomreyn ?
[11:06] <didrocks> RikMills: sounds like bug #1847457
[11:07] <RikMills> I wondered, but was not sure
[11:07] <didrocks> sounds really like it
[11:19] <tomreyn> RikMills: it is. i just noticed the installer / live system has upgrades available - so it may be PEBKAC
[11:22] <didrocks> tomreyn: if you don't have the kernel, the issue can be /cdrom which isn't mounted
[11:22] <didrocks> we have a revert ready if foundation can't fix it
[11:22] <didrocks> (but it's not related to ZFS, it can be on ext4 as well)
[11:29] <tomreyn> didrocks: there's been no pending kernel upgrade
[11:31] <didrocks> tomreyn: maybe I was unclear, the issue of empty grub is probably due to no kernel installed on your target
[11:32] <didrocks> which is itself probably due to /cdrom being empty when installing
[11:32] <didrocks> hence, if you can double check that the target system has no kernel installed, that would help! :)
[11:34] <tomreyn> didrocks: /target/boot/ has vmlinuz-5.3.0-13-generic which is about the size i'd expect
[11:35] <tomreyn> and thanks for clarifying ;)
[11:35] <didrocks> do you have an initrd as well?
[11:35] <tomreyn> yes, also expected size. but note that this is a system i just installed after those apt updates, and which i have not tried to reboot to, yet
[11:36] <didrocks> ah, it's another install?
[11:36] <tomreyn> i'm just trying to find a way to gather logs before i try rebooting to it
[11:36] <didrocks> not the one you reported?
[11:36] <tomreyn> not the one i reported, buut created the say way.
[11:36] <didrocks> and grub.cfg is empty?
[11:36] <didrocks> like doesn't have any kernel entry?
[11:37] <tomreyn> no, not empty, it lists the kernel :(
[11:37] <didrocks> yeah
[11:37] <didrocks> hence why I was asking if it's the same or not :)
[11:37] <tomreyn> it must have been the grub update then
[11:37] <didrocks>  /cdrom being empty is racy
[11:37] <didrocks> so, it seems that on this install, you got lucky
[11:39] <tomreyn> i'll try again without upgrading apt, then see if i can rpeorduce and whether kernel is installed but not listed in grub.cfg. but i'll move to #ubuntu+1, don't want to spam here more. sorry for the waste of time.
[11:39] <didrocks> no worry! But yeah, look if /cdrom is empty or not before installing
[11:40] <didrocks> if empty -> you will probably end up with an unbootable system (because no kernel installed)
[11:40] <didrocks> this is ext4, zfs or whatever partionning option
[11:40] <tomreyn> that's /cdrom on the running installer / live system, right?
[11:40] <didrocks> right
[11:41] <tomreyn> ok
[11:48] <tomreyn> didrocks: one more question: can i just mount /cdrom if it's missing? or will i just need to keep rebooting the installer till it's therE?
[11:50] <tomreyn> can't "just mount" since /cdrom is not in fstab (and i'm not sure how i'd do it manually). will keep rebooting.
[11:50] <Laney> systemctl start cdrom.mount
[11:51] <tomreyn> thanks!
[11:51] <Laney> :V V:
[11:57] <Wimpress> https://twitter.com/phoronix/status/1181886449270087680
[11:57] <Wimpress> didrocks jibel ^ :-)
[11:58] <didrocks> excellent!
[12:00] <Laney> laters potaters
[12:00] <Laney> see you tomorrow
[12:00] <didrocks> see you Laney!
[12:08] <xnox> seb128:  it's desktop team's responsibility to maintain canary images and the layered livebuild code path; all release products using non-layered codepath are generated and are operating correctly; no you shall not revert the changes in casper & livebuild & livecd-rootfs as that will regress bootability of all the release products.
[12:09] <xnox> seb128:  also, i've spend time unbreaking canary images which were failing to build from source for a long time, even though it's not at all my responsibility to work on it. Your welcome =) at least the livefs builds succeed now.
[12:10] <xnox> seb128:  however initrds for them still do not appear to be generated with the correct environment, as they must provide unique uuid build stamp to operate correctly as expected by ubuntu-cdimage & casper
[12:13] <xnox> seb128:  unless you are about the new casper bug, empty /cdrom. Yes if things are broken revert that.
[12:15]  * xnox ponders how come I am testing this wrong, am I the only one using an actual CDROM?!
[12:16] <sergiusens> xnox: surprised you still have one of those around!
[12:18] <xnox> nah reproducible completely
[12:18]  * xnox ponders life
[12:27] <jibel> Wimpress, awesome :)
[12:32] <xnox> omg
[12:47] <seb128> xnox, hey, sorry I was at lunch, ack on what you wrote, I was speaking about empty /cdrom only today
[12:47] <ricotz> seb128, hi :), vala updates are prepared in salsa
[12:48] <seb128> ricotz, hey, ok, I will review/sponsor in a bit
[12:48] <ricotz> thank you
[12:48] <ricotz> 0.44.9 for eoan and 0.46.3 for sid
[12:48] <seb128> k
[12:56] <xnox> seb128:  i think i have a fix, but its ugly..... setting SYSTEMD_READY=1 in a udev rule. Imho, i think systemd is broken with their bound-device stuff for cdroms, so i want to file an upstream bug about it to hammer it out.
[12:56] <xnox> seb128:  so yes, your revert is the way to go for 19.10 GA
[12:56] <xnox> seb128:  thank you.
[12:57] <seb128> xnox, good, thanks for looking!
[12:58] <seb128> xnox, speaking about upstreaming, you still need to do that for your recent plymouth patch :)
[12:58] <xnox> seb128:  which recent plymouth patch?
[13:00] <seb128> xnox, https://launchpad.net/ubuntu/+source/plymouth/0.9.4git20190712-0ubuntu2
[13:00] <seb128> ' Add tile support in script plugin'
[13:00] <xnox> seb128:  i submitted that to plymouth upstream, and i thought they took it https://gitlab.freedesktop.org/plymouth/plymouth/merge_requests/64
[13:00] <gitbot> plymouth issue (Merge request) 64 in plymouth "script: Add image tile support." [Closed]
[13:00] <xnox> seb128:  that was submitted prior to upload.
[13:01] <xnox> seb128:  is that person confused about gitlab, and closed the merge (as in reject) whilst expecting it to be merged/pulled?
[13:01] <seb128> xnox, ah sorry, I see it now
[13:01] <xnox> seb128:  is it in, actually, master?
[13:01] <seb128> I don't know what he did but it's in the commit
[13:01] <seb128> yes
[13:01] <seb128> https://gitlab.freedesktop.org/plymouth/plymouth/commit/aa89dcdf5
[13:02] <xnox> seb128:  ok good.
[13:02] <xnox> seb128:  it's not in debian though i don't think and i didn't try submitting there.
[13:02] <seb128> xnox, that's fine, we are no in sync with them anyway
[13:02] <xnox> yeah
[13:03] <seb128> I need to nag upstream into doing a release
[13:03] <seb128> the current one is almost a year old and doesn't include the bgrt theme
[13:03] <seb128> we are on a git snapshot atm... (as is fedora)
[13:08] <didrocks> Trevinho: are you sure about the duplicate on https://gitlab.gnome.org/GNOME/gnome-shell/issues/1554 ?
[13:08] <gitbot> GNOME issue 1554 in gnome-shell "Volume up/down repeat keys don't work on Xorg" [Closed]
[13:09] <didrocks> at first, it looks unrelated, but just double checking :)
[13:09] <didrocks> ah, you reduplicate it to the correct one now :)
[13:10] <Trevinho> didrocks: yeah, I bisected and... It is
[13:10] <Trevinho> yep I crossed my fingers (41 vs 14)
[13:10] <didrocks> I see you like to blame on electron bug! :)
[13:10] <didrocks> great news anyway :p
[13:11] <Trevinho> Laney: if not too late you can add https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841929 to the changelog party
[13:11] <Trevinho> electron?
[13:12] <didrocks> the incorrect duplicate :p
[13:13] <Trevinho> ahh 😅
[13:13] <Trevinho> I didn't either read... I saw the wrong number but was too late after my ctrl enter
[13:32] <tomreyn> http://cdimage.ubuntu.com/daily-live/current/ currently points to http://cdimage.ubuntu.com/daily-live/20191006/ - that's one purpose, right? due to bug 1847457 ?
[13:32] <tomreyn> s/ one / on /
[13:33] <jibel> tomreyn, automated tests failed and the image has not been published
[13:33] <jibel> publish -> copied from pending to currnet
[13:36] <tomreyn> jibel: i see. so todays' (20191009) image failed some tests and shouldn't be used for testing, and those of the past two days, too? and sundays' ( current/ ) image does not yet have the zfs option enabled according to LuckyMan in #ubuntu+1.
[13:37] <jibel> tomreyn, correct, wait for next build which will have a revert of casper and hopefully will be good.
[13:38] <tomreyn> thanks
[14:17] <seb128> bah, valgrind doesn't seem happy on my machine, it doesn't pick up glib/gtk debug symbols it looks like
[14:18] <seb128> does it work for others?
[14:19] <seb128> like if you install gnome-calendar-dbgsym libglib2.0-0-dbgsym libgtk-3-0-dbgsym and try to valgrind gnome-calendar?
[14:19] <seb128> (also removing/adding a google account in goa while it's open and it should segfault)
[14:21] <hellsworth> good morning desktopers
[14:21] <seb128> also I got gnome-shell unhappy a few times while trying to valgrind gnome-calendar now, I wonder if it's just slowing things too much or triggering some other bugs :/
[14:21] <seb128> hey hellsworth, how are you today?
[14:21] <oSoMoN> good morning hellsworth
[14:21] <marcustomlinson> hey hellsworth
[14:21] <hellsworth> i'm good. yesterday i was under the weather and today i feel great and ready to do all the things!
[14:22] <seb128> nice!
[14:23] <hellsworth> marcustomlinson, i will likely have questions for you in a bit so stay tuned :)
[14:23] <seb128> oSoMoN, marcustomlinson, you can't pretend you are not reading IRC :p fancy trying that valgrind thing?
[14:24] <hellsworth> i got the gnome-3-34-1804-sdk merged yesterday so looking at content snap and extension today
[14:24] <hellsworth> oh oops seb128.. i'll try to bug marcustomlinson minimally then :)
[14:24] <oSoMoN> seb128, sure, what do you need me to try?
[14:25] <seb128> hellsworth, lol, don't worry, mine is easy and it's not important so marcus can ignore me :)
[14:25] <seb128> oSoMoN, ideally
[14:25] <seb128> $ sudo apt install gnome-calendar-dbgsym libglib2.0-0-dbgsym libgtk-3-0-dbgsym
[14:25] <marcustomlinson> seb128: ;) "desktop_ers" highlights for me so it was hard to miss
[14:25] <seb128> $ valgrind gnome-calendar
[14:26] <seb128> $ go to g-c-c -> online account and add your canonical account (or remove add it back)
[14:26] <seb128> see if
[14:26] <seb128> 1- it segfaults
[14:26] <seb128> 2- valgrind gives you some useful info
[14:26] <seb128> 3- it screws your shell in some way
[14:26] <seb128> oSoMoN, ^ but don't stop what you are doing for that
[14:26] <seb128> like if you want to try tomorrow morning when you are not in middle of something that works too
[14:27] <oSoMoN> seb128, I can do that in a VM
[14:27] <oSoMoN> as a background task
[14:27] <seb128> would be nice
[14:27] <seb128> thx
[14:39] <oSoMoN> seb128, I added my Ubuntu SSO account but gnome-calendar didn't crash
[14:39] <oSoMoN> did you mean google account, maybe?
[14:39] <seb128> oSoMoN, and it's picking up the events?
[14:40] <seb128> oSoMoN, oh yes, sorry, google canonical account I meant
[14:40] <seb128> one which actually has a calendar :)
[14:40] <oSoMoN> that makes sense, calendar events and all that…
[14:40] <seb128> right
[14:40] <seb128> sorry for not being clear
[14:41] <oSoMoN> account added, and hu ho, shell froze
[14:42] <seb128> ok, so it's not only me :/
[14:42] <seb128> Trevinho, ^ did you see reports about that?
[14:43]  * Trevinho checks
[14:43] <Trevinho> sorry, just arrived at my place in SIntra
[14:43] <oSoMoN> shell came back to life, but gnome-calendar crashed indeed
[14:44] <oSoMoN> seb128, if I can help debug this further, let me know, I'll keep the VM paused
[14:44] <seb128> oSoMoN, did valgrind give you anything useful?
[14:44] <seb128> or do you lack symbols as well
[14:44] <Trevinho> mhmh, not sure I find where to read the whole report
[14:44] <Trevinho> maybe znc lost the messages...
[14:49] <seb128> Trevinho, basically valgrind gnome-calendar and adding a google account in goa makes gnome-calendar and gnome-shell unhappy
[14:50] <oSoMoN> hrm, shell froze again in my VM
[14:51] <seb128> doing what?
[14:52] <Trevinho> seb128: can you catch where the shell is froozen at?
[14:52] <Trevinho> I can script you something in gdb if you want
[14:52] <Trevinho> or well just do things from tty
[14:52] <Trevinho> ssh
[14:52] <Trevinho> or whathever
[14:52] <seb128> oSoMoN, ^ if you have it stuck?
[14:52] <seb128> Trevinho, I will try in a bit again
[14:53] <seb128> I did switch back to upload vala and some other things
[14:53] <seb128> I've another go at the calendar problems in a bit
[14:53] <oSoMoN> seb128, I was just scrolling in terminal to read valgrind's output, and everything froze
[14:53] <oSoMoN> I have a TTY so I can do things, but shell remains frozen for now
[14:54] <seb128> oSoMoN, get a gdb bt t a a if you can maybe?
[14:58] <oSoMoN> in ObjectBase::associate_closure(JSContext*, _GClosure*) () from /usr/lib/libgjs.so.0
[15:00] <seb128> Trevinho, ^
[15:00] <Trevinho> seb128: ok, so... try to do in gdb
[15:00] <Trevinho> call (void) gjs_dumpstack()
[15:00] <Trevinho> the output will be in journalctl /usr/bin/gnome-shell
[15:00] <seb128> oSoMoN, ^
[15:01] <Trevinho> however, it might be just something like... the shell uses some sync dbus method for talking with it, so....
[15:01] <Trevinho> all the trace would be useful though
[15:02] <Trevinho> probably the same can be, in such state, replicated when calendar is around and at given stop we kill -STOP it
[15:02] <seb128> I bet it's something like that
[15:03] <oSoMoN> doing that
[15:05] <oSoMoN> man, journalctl is flooded with: JS ERROR: TypeError: windowActor is null (_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9)
[15:08] <oSoMoN> and then JS ERROR: TypeError: null has no properties
[15:08] <oSoMoN> I gotta go pick up my daughter from school, bbiab to dig further
[15:10] <seb128> oSoMoN, don't bother, I didn't mean to derail you
[15:10] <seb128> oSoMoN, I can do another round of debugging later as well, I just wanted someone to confirm it's not only me and it seems it's not :)
[15:53] <Trevinho> oSoMoN: mh those should be harmless...
[15:54] <Trevinho> Once you call the func from gdb you should get that out, so use journalctl -f in another terminal
[15:58] <seb128> Trevinho, can you try if you get the issue as well? just valgrind gnome-calendar and add a google account to online settings
[16:01] <Trevinho> seb128: ok sure
[16:01] <Trevinho> but want to finish this desktop icons packaging
[16:01] <Trevinho> first
[16:03] <oSoMoN> back, let me see if I can get the stack
[16:04] <oSoMoN> Trevinho, the JS errors might be harmless, but the journal is literally flooded with them, I've got countless occurrences every second, that can't be good
[16:06] <Trevinho> oSoMoN: mh, okwell indeed no... you can get more out of those if you run the shell with debugging bits
[16:07] <Trevinho> should be SHELL_DEBUG=backtrace-warnings:backtrace-segfaults
[16:07] <Trevinho> although they should be default in ubuntu...
[16:07] <oSoMoN> the stack dump doesn't look very useful to me, let me reproduce it here:
[16:07] <oSoMoN> == Stack trace for context 0x55f74f9b6310 ==
[16:07] <Trevinho> you can set that env in your xsession file
[16:08] <Trevinho> ohhhk... then it's stuff happening in a js level that we can't control (i.e. not direct js call)
[16:08] <oSoMoN> #0   7ffcc6522790 I   resource:///org/gnome/shell/ui/closeDialog.js:138 (7f873625af70 @ 153)
[16:08] <oSoMoN> and that's all
[16:08] <oSoMoN> afaict
[16:08] <Trevinho> and the full C trace is useless as well?
[16:08] <Trevinho> ahhhh ok then no :)
[16:09] <Trevinho> that line is useless here let me check ubuntu srcs
[16:10] <Trevinho> mhmmh, it's connecting to a signal... how can be.
[16:11] <Trevinho> oSoMoN: ooohohh, wait... that's not what we care here, that is the dialog that shows in alt+f2
[16:11] <Trevinho> so some errors like that are expected
[16:11] <Trevinho> we need to catch the one while is hangign
[16:11] <Trevinho> hanging*
[16:13] <Wimpress> didrocks: Ubuntu MATE, Ubuntu Budgie, Xubuntu and Ubuntu Studio are joining the ZFS fun.
[16:14] <Wimpress> Kubuntu and Lubuntu require UI work, so not able to participate this cycle.
[16:15] <jibel> Wimpress, this is excellent, thank you.
[16:15] <Wimpress> jibel: 👍
[16:15] <didrocks> Wimpress: great! Thanks a lot :) and getting early feedback on zsys will be nice! (I think we'll do an eoan ppa for people to get some feature updates)
[16:16] <Wimpress> Cool. Looking forward to taking advantage of the ZFS features.
[16:17] <didrocks> I guess we'll sync up after release with the incoming plans
[16:17] <jibel> I'm rebuilding an iso with the new casper
[16:17] <jibel> fyi
[16:19] <Wimpress> The green edition is also rebuilding with new casper and seeds :-)
[16:20] <didrocks> should be called matcha, not mate
[16:21] <Wimpress> :-)
[16:38] <Trevinho> meanwhile.... shell extensions are building here https://bileto.ubuntu.com/#/ticket/3819
[17:20] <Wimpress> New iso is good :-) ZFS FTW!
[17:20] <didrocks> nice!
[17:20] <didrocks> high time for evening now that the code generation is working though, see you tomorrow!
[17:27] <willcooke> nice one chaps
[17:27] <willcooke> and with that, good night
[17:46] <ricotz> please approve the vala package waiting the in eoan queue :)
[23:16] <amurray> kenvandine: \o/ - latest candidate gtk-common-themes has your communitheme-light support - thanks again for fixing this :) now I don't have a transparent calculator anymore
[23:18] <kenvandine> amurray: great, thanks so much for finding it
[23:24] <sarnold> "canonical takes away transparent calculator"
[23:32] <kenvandine> sarnold: tomorrow's headline
[23:32]  * sarnold nods
[23:41] <xnox> must make sure phoronix is not highlighted about this
[23:42] <xnox> and askubuntu should not blog about this