[01:52] amurray: PR submitted for communitheme-light https://github.com/ubuntu/yaru/pull/1568 [01:52] ubuntu issue (Pull request) 1568 in yaru "When building with communitheme_compat, link the light variant" [Open] [01:53] amurray: thanks for using the communitheme :) [03:26] 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] kenvandine: thanks for making it awesome' [03:29] you could always pin the yaru-theme-gtk package from a newer release [03:33] jamesh: true [03:57] hey jamesh [04:04] hi kenvandine [05:19] 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] good morning desktoppers [06:05] Morning oSoMoN [06:09] hey duflu [06:14] good morning [06:16] Hi didrocks [06:16] hey duflu [06:19] o/ [06:21] Laney etc al. Kubuntu manual partition seems ok with new ubiquity. Thanks for the fix :) [06:21] *et al [06:27] RikMills, yw [06:29] Morning jibel [06:29] And good morning Wimpress [06:29] hi duflu and all [06:29] hey Wimpress [06:30] salut didrocks [06:30] hey Wimpress [06:30] salut jibel [06:32] hey oSoMoN [06:34] oSoMoN: thanks for checking that Thunderbird Dictionary bug :) === pstolowski|afk is now known as pstolowski [07:07] kenvandine, hey thanks for the PR [07:07] and, hello everyone 0/ [07:08] gooood morning desktopers [07:14] Morning seb128 [07:14] hey duflu, how are you? [07:15] seb128, going well, and busy. Three of my release bugs require simultaneous attention today ;) [07:15] How are you seb128? [07:15] duflu, I'm good! [07:15] duflu, the fftw3 issue is weird, the source didn't change and it started failing :-/ [07:16] hey seb128 [07:16] also it's armhf only [07:16] hey didrocks, how are you? [07:16] I'm fine, thanks, you? [07:16] seb128, yeah I am digging deeper so won't confuse the situation by posting any guesses right now [07:17] 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] duflu, k [07:17] didrocks, I'm good :) [07:17] seb128: yeah, that's fine for me. However, for the installer ones, those are mostly dups [07:17] and we have annoying users when you repeat the same thing over and over again on bugs :/ [07:17] but otherwise, feel free to subscribe us, that's helpful [07:18] good, thx [07:19] seb128, I did however spend half the weekend finding my armhf hardware is now too old to be useful [07:19] seb128, i'm tracking installer related components on lp. you can always subscribe me too [07:19] So that was interesting [07:19] jibel, hey, good :) [07:20] duflu, :-/ we have those canonistack instance which are handy [07:20] Yeah. I also have a working VM. [07:20] duflu, I'm not sure if that armhf issue is worth spending too much time on though [07:20] I wonder if building with O1 would make a difference/be a workaround [07:20] I may be able to propose a fix "quickly" based on what I have seen. But will take time to confirm [07:21] k [07:22] so I did a daliy install yesterday using custom partitioning [07:23] 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] Also good news - eoan seems to have fixed a touchpad bug on a laptop I thought was faulty till now [07:24] duflu, ah, nice when bugs autoresolve themselves with updates :) [07:24] Yeah everyone hopes for it but really it practically never happens [07:25] didrocks, jibel, do you also watch zfs-utils? e.g bug #1847325 got reported that sound like installer issue [07:25] bug 1847325 in zfs-linux (Ubuntu) "ZFS Installer refuses to install the boot loader on both disks" [Undecided,New] https://launchpad.net/bugs/1847325 [07:26] you mean zfs-linux? [07:26] seb128, yes and it's our friend again [07:26] but yeah, this is the dup [07:26] didrocks, obviously :p [07:26] ah, you made a friend? nice :) [07:26] yeah, the one I was referring above ^ [07:27] 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] 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] :/ [07:28] a little bit tedious [07:34] Laney, hi, do you think the empty /cdrom could explain that there is no kernel on the installed system? [07:34] xnox, ^ [07:35] I hope bug 1845454 gets fixed in time [07:35] bug 1845454 in linux (Ubuntu) "Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10 (but 5.2 works)" [Critical,In progress] https://launchpad.net/bugs/1845454 [07:36] it looks for kernel in the casper_path, so sounds like it [07:36] duflu, don't really have a choice, it's a showstopper for the release IMHO [07:37] I would agree. Seems to be a minority of machines, but still a lot of machines [07:37] Anyway, Seth has a fix proposed already [07:37] weird that ubiquity doesn't fail on not being able to copy a kernel though [07:40] duflu, yeah just recent Dell machines ;) [07:42] who needs a kernel anyway [07:44] indeed, systemd should be enough :) [07:47] morning [07:47] hey willcooke, how are you? feeling better? [07:48] hey seb128, yeah much better than yesterday thanks [07:48] great! [07:49] and brb, relocating from my morning coffee :) [07:50] Morning willcooke [07:51] afternoon duflu [07:52] hey willcooke [07:53] morning didrocks [08:09] k, back now! [08:09] Laney, hey, how are you? [08:11] morning [08:11] weird internet problems but here now!!!! [08:12] Morning Laney [08:12] hey Laney [08:14] hey duflu didrocks [08:14] moin Laney [08:15] what up willcooke [08:28] morning desktopers [08:28] Hi marcustomlinson [08:30] hey marcustomlinson [08:38] morning marcustomlinson [08:51] Trevinho, bonjourno ... what happened, gnome-shell having tarballs on time?! :) [08:51] seb128, he was still around in my morning so give him time... [08:52] didrocks: I guess flavours should follow suit with this? https://launchpad.net/ubuntu/+source/ubuntu-meta/1.438 [08:53] RikMills: that's correct, Wimpress as well ^ [08:54] RikMills: feel free to hook you in to the bug [08:54] didrocks: thanks. I have put that info in #ubuntu-flavors [08:55] thx! [09:45] bah, I just did a daily install but it's not in my grub menu post reboot :/ [09:45] seb128: hey... Yaz, we pinged florian in various flavors yesterday. It worked 😅 [09:46] Trevinho, hey, well done :) [09:46] although I already found leftover bugs. [09:46] :( [09:46] nothing new, but they were staying there for a while. [09:46] when do you travel to ubucon? [09:47] and l_aney beated in handling the upgrade this morning, so... we'll get it soon [09:47] seb128: now :-). [09:47] ah, safe travel! [09:47] about to take off really [09:47] did you get the extensions bugfix updates ready? [09:48] ah ok [09:48] seb128: missing kernel? [09:48] roaming from a plane which is going to take off again? ;) [09:48] didrocks, how do I tell? [09:48] 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] seb128: boot a live, mount the system and check its /boot [09:49] didrocks, looks like it yes [09:49] I guess you didn't look if your install had the missing /cdrom? [09:49] it's a bit unfortunate :p [09:49] no, I just fired a daily install [09:49] but reading ubiquity code, it's really taking it from /cdrom/casper [09:50] I wanted to test if the screen turned off during install [09:50] so sounds suspiciously related [09:50] which it didn't [09:50] short install? [09:50] 15 min ? [09:50] also I stayed on the reboot dialog for 10 min while finishing other work on the other computer [09:50] hum, mine didn't take that long yesteday [09:50] but that was a 'install only', not live session [09:50] ah [09:51] I was on a live one [09:51] I will try that next [09:51] and maybe I get a kernel this time :) [09:51] check /cdrom!!! :) [09:51] will do! [09:51] if it's empty, it's a good opportunity to check the resulting fs [09:52] do we have a launchpad bug for the lack of kernel issue? [09:52] I don't see one in the recent ubiquity reports [09:52] no, but we don't have one for /cdrom either [09:52] I tried but LP keep erroring for me [09:52] so let's confirm if this is the case [09:52] it's the same bug [09:52] and if so, I'm happy to open [09:53] what's the cause of missing /cdrom? Recent casper change? (to know against which package to open the bug) [09:53] casper [09:53] the cdrom.mount inclusion [09:53] ah, thx [09:53] didrocks, here is the text of the bug I tried to file https://paste.ubuntu.com/p/k65xkq3dPs/ [09:53] thx jibel, filing it [09:54] Laney, is x_nox the one supposed to look at resolving that? [09:54] yes, he's been pinged about 1000000 times [09:54] and again this morning [09:55] no clear commitment to working on it though, get it rls-ed so that it is noticed in their meeting [09:55] bug #1847457 [09:55] bug 1847457 in casper (Ubuntu) "No /cdrom mounted on live" [Critical,New] https://launchpad.net/bugs/1847457 [09:55] that doesn't seem good enough at this point of the cycle [09:55] ok [09:55] that's up to you [09:55] 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] Laney, that would be nice, but seems to not work in this case since we get no traction/reply :/ [09:57] well he doesn't seem to be online yet today [09:57] I've subscribed the interested flavours to https://pad.lv/1847431 [09:57] Launchpad bug 1847431 in ubuntustudio-meta (Ubuntu) "Installing ZFS without network is failing" [Undecided,New] [09:58] Wimpress: saw that, thanks! [09:58] And let them know in the flavours IRC channel. [09:58] didrocks: I have a question for you. [09:58] The flavours can seed package from outside main. [09:58] Hum [09:58] What do you think about the flavours seeding zsys? [09:58] I see where you are going to :p [09:59] there is no snapshot "command" to create zsys snapshot (and so, reveal the history menu) [09:59] we can provide some guides [09:59] with manual commands [09:59] seb128, done [09:59] and then, yeah, there are some benefits for zsys [09:59] Wimpress: let's say if one flavor, like Mate, does that, it will be great [09:59] OK, cool./ [09:59] willcooke, thx [09:59] I plan to write blog posts about the benefits of adding zsys next week [09:59] thanks Wimpress [10:00] I think Budgie would be interested too. Probably Ubuntu Studio. [10:00] that should be fine, we have tests for it [10:00] didrocks: Advocacy are happy to assist with blog post review if you want? [10:00] unfortunately, no snapshot command as being descoped… [10:00] Wimpress: sounds great! [10:00] We can also schedule the social posts for any blogs you want to publish. [10:00] I used to have willcooke doing the per-reviewing [10:01] so other eyes are always good [10:01] still happy to review [10:01] Likewise. [10:01] 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] 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] seb128: can you remove mono from eoan-proposed? it looks like that will fix the libproxy/s390x build [10:34] 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] any eyes on this one? LP: #1847469 [11:04] Launchpad bug 1847469 in ubiquity (Ubuntu) "19.10 daily 20191009: amd64 UEFI zfs_install succeeds but cannot boot" [Undecided,New] https://launchpad.net/bugs/1847469 [11:05] I believe that report is from tomreyn ? [11:06] RikMills: sounds like bug #1847457 [11:06] bug 1847457 in casper (Ubuntu) "No /cdrom mounted on live" [Critical,New] https://launchpad.net/bugs/1847457 [11:07] I wondered, but was not sure [11:07] sounds really like it [11:19] RikMills: it is. i just noticed the installer / live system has upgrades available - so it may be PEBKAC [11:22] tomreyn: if you don't have the kernel, the issue can be /cdrom which isn't mounted [11:22] we have a revert ready if foundation can't fix it [11:22] (but it's not related to ZFS, it can be on ext4 as well) [11:29] didrocks: there's been no pending kernel upgrade [11:31] tomreyn: maybe I was unclear, the issue of empty grub is probably due to no kernel installed on your target [11:32] which is itself probably due to /cdrom being empty when installing [11:32] hence, if you can double check that the target system has no kernel installed, that would help! :) [11:34] didrocks: /target/boot/ has vmlinuz-5.3.0-13-generic which is about the size i'd expect [11:35] and thanks for clarifying ;) [11:35] do you have an initrd as well? [11:35] 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] ah, it's another install? [11:36] i'm just trying to find a way to gather logs before i try rebooting to it [11:36] not the one you reported? [11:36] not the one i reported, buut created the say way. [11:36] and grub.cfg is empty? [11:36] like doesn't have any kernel entry? [11:37] no, not empty, it lists the kernel :( [11:37] yeah [11:37] hence why I was asking if it's the same or not :) [11:37] it must have been the grub update then [11:37] /cdrom being empty is racy [11:37] so, it seems that on this install, you got lucky [11:39] 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] no worry! But yeah, look if /cdrom is empty or not before installing [11:40] if empty -> you will probably end up with an unbootable system (because no kernel installed) [11:40] this is ext4, zfs or whatever partionning option [11:40] that's /cdrom on the running installer / live system, right? [11:40] right [11:41] ok [11:48] 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] 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] systemctl start cdrom.mount [11:51] thanks! [11:51] :V V: [11:57] https://twitter.com/phoronix/status/1181886449270087680 [11:57] didrocks jibel ^ :-) [11:58] excellent! [12:00] laters potaters [12:00] see you tomorrow [12:00] see you Laney! [12:08] 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] 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] 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] 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] xnox: surprised you still have one of those around! [12:18] nah reproducible completely [12:18] * xnox ponders life [12:27] Wimpress, awesome :) [12:32] omg [12:47] xnox, hey, sorry I was at lunch, ack on what you wrote, I was speaking about empty /cdrom only today [12:47] seb128, hi :), vala updates are prepared in salsa [12:48] ricotz, hey, ok, I will review/sponsor in a bit [12:48] thank you [12:48] 0.44.9 for eoan and 0.46.3 for sid [12:48] k [12:56] 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] seb128: so yes, your revert is the way to go for 19.10 GA [12:56] seb128: thank you. [12:57] xnox, good, thanks for looking! [12:58] xnox, speaking about upstreaming, you still need to do that for your recent plymouth patch :) [12:58] seb128: which recent plymouth patch? [13:00] xnox, https://launchpad.net/ubuntu/+source/plymouth/0.9.4git20190712-0ubuntu2 [13:00] ' Add tile support in script plugin' [13:00] seb128: i submitted that to plymouth upstream, and i thought they took it https://gitlab.freedesktop.org/plymouth/plymouth/merge_requests/64 [13:00] plymouth issue (Merge request) 64 in plymouth "script: Add image tile support." [Closed] [13:00] seb128: that was submitted prior to upload. [13:01] seb128: is that person confused about gitlab, and closed the merge (as in reject) whilst expecting it to be merged/pulled? [13:01] xnox, ah sorry, I see it now [13:01] seb128: is it in, actually, master? [13:01] I don't know what he did but it's in the commit [13:01] yes [13:01] https://gitlab.freedesktop.org/plymouth/plymouth/commit/aa89dcdf5 [13:02] seb128: ok good. [13:02] seb128: it's not in debian though i don't think and i didn't try submitting there. [13:02] xnox, that's fine, we are no in sync with them anyway [13:02] yeah [13:03] I need to nag upstream into doing a release [13:03] the current one is almost a year old and doesn't include the bgrt theme [13:03] we are on a git snapshot atm... (as is fedora) [13:08] Trevinho: are you sure about the duplicate on https://gitlab.gnome.org/GNOME/gnome-shell/issues/1554 ? [13:08] GNOME issue 1554 in gnome-shell "Volume up/down repeat keys don't work on Xorg" [Closed] [13:09] at first, it looks unrelated, but just double checking :) [13:09] ah, you reduplicate it to the correct one now :) [13:10] didrocks: yeah, I bisected and... It is [13:10] yep I crossed my fingers (41 vs 14) [13:10] I see you like to blame on electron bug! :) [13:10] great news anyway :p [13:11] Laney: if not too late you can add https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841929 to the changelog party [13:11] Launchpad bug 1841929 in gnome-shell (Ubuntu Eoan) "Volume up/down repeat keys don't work on Xorg" [High,In progress] [13:11] electron? [13:12] the incorrect duplicate :p [13:13] ahh 😅 [13:13] I didn't either read... I saw the wrong number but was too late after my ctrl enter [13:32] 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] bug 1847457 in casper (Ubuntu) "No /cdrom mounted on live" [Critical,Confirmed] https://launchpad.net/bugs/1847457 [13:32] s/ one / on / [13:33] tomreyn, automated tests failed and the image has not been published [13:33] publish -> copied from pending to currnet [13:36] 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] tomreyn, correct, wait for next build which will have a revert of casper and hopefully will be good. [13:38] thanks === hyperair is now known as Guest14896 === meetingology` is now known as meetingology === lotus|i5 is now known as lotuspsychje [14:17] bah, valgrind doesn't seem happy on my machine, it doesn't pick up glib/gtk debug symbols it looks like [14:18] does it work for others? [14:19] like if you install gnome-calendar-dbgsym libglib2.0-0-dbgsym libgtk-3-0-dbgsym and try to valgrind gnome-calendar? [14:19] (also removing/adding a google account in goa while it's open and it should segfault) [14:21] good morning desktopers [14:21] 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] hey hellsworth, how are you today? [14:21] good morning hellsworth [14:21] hey hellsworth [14:21] i'm good. yesterday i was under the weather and today i feel great and ready to do all the things! [14:22] nice! [14:23] marcustomlinson, i will likely have questions for you in a bit so stay tuned :) [14:23] oSoMoN, marcustomlinson, you can't pretend you are not reading IRC :p fancy trying that valgrind thing? [14:24] i got the gnome-3-34-1804-sdk merged yesterday so looking at content snap and extension today [14:24] oh oops seb128.. i'll try to bug marcustomlinson minimally then :) [14:24] seb128, sure, what do you need me to try? [14:25] hellsworth, lol, don't worry, mine is easy and it's not important so marcus can ignore me :) [14:25] oSoMoN, ideally [14:25] $ sudo apt install gnome-calendar-dbgsym libglib2.0-0-dbgsym libgtk-3-0-dbgsym [14:25] seb128: ;) "desktop_ers" highlights for me so it was hard to miss [14:25] $ valgrind gnome-calendar [14:26] $ go to g-c-c -> online account and add your canonical account (or remove add it back) [14:26] see if [14:26] 1- it segfaults [14:26] 2- valgrind gives you some useful info [14:26] 3- it screws your shell in some way [14:26] oSoMoN, ^ but don't stop what you are doing for that [14:26] like if you want to try tomorrow morning when you are not in middle of something that works too [14:27] seb128, I can do that in a VM [14:27] as a background task [14:27] would be nice [14:27] thx [14:39] seb128, I added my Ubuntu SSO account but gnome-calendar didn't crash [14:39] did you mean google account, maybe? [14:39] oSoMoN, and it's picking up the events? [14:40] oSoMoN, oh yes, sorry, google canonical account I meant [14:40] one which actually has a calendar :) [14:40] that makes sense, calendar events and all that… [14:40] right [14:40] sorry for not being clear [14:41] account added, and hu ho, shell froze [14:42] ok, so it's not only me :/ [14:42] Trevinho, ^ did you see reports about that? [14:43] * Trevinho checks [14:43] sorry, just arrived at my place in SIntra [14:43] shell came back to life, but gnome-calendar crashed indeed [14:44] seb128, if I can help debug this further, let me know, I'll keep the VM paused [14:44] oSoMoN, did valgrind give you anything useful? [14:44] or do you lack symbols as well [14:44] mhmh, not sure I find where to read the whole report [14:44] maybe znc lost the messages... [14:49] Trevinho, basically valgrind gnome-calendar and adding a google account in goa makes gnome-calendar and gnome-shell unhappy [14:50] hrm, shell froze again in my VM [14:51] doing what? [14:52] seb128: can you catch where the shell is froozen at? [14:52] I can script you something in gdb if you want [14:52] or well just do things from tty [14:52] ssh [14:52] or whathever [14:52] oSoMoN, ^ if you have it stuck? [14:52] Trevinho, I will try in a bit again [14:53] I did switch back to upload vala and some other things [14:53] I've another go at the calendar problems in a bit [14:53] seb128, I was just scrolling in terminal to read valgrind's output, and everything froze [14:53] I have a TTY so I can do things, but shell remains frozen for now [14:54] oSoMoN, get a gdb bt t a a if you can maybe? [14:58] in ObjectBase::associate_closure(JSContext*, _GClosure*) () from /usr/lib/libgjs.so.0 [15:00] Trevinho, ^ [15:00] seb128: ok, so... try to do in gdb [15:00] call (void) gjs_dumpstack() [15:00] the output will be in journalctl /usr/bin/gnome-shell [15:00] oSoMoN, ^ [15:01] however, it might be just something like... the shell uses some sync dbus method for talking with it, so.... [15:01] all the trace would be useful though [15:02] probably the same can be, in such state, replicated when calendar is around and at given stop we kill -STOP it [15:02] I bet it's something like that [15:03] doing that [15:05] 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]