=== cpaelzer_ is now known as cpaelzer [06:22] good morning [06:45] Salut didrocks [06:48] good morning desktoppers [06:49] salut jibel, hey oSoMoN [06:49] salut didrocks, ça va mieux? [06:49] salut jibel [06:50] un peu mieux oSoMoN, merci :) déjà, plus de fièvre aujourd'hui, mais encore bien pris par une rhino [06:50] Bonjour oSoMoN [06:50] ça passera doucement :p [06:51] didrocks, take it easy, faut être en forme pour le week-end :) [07:02] bonjour madame [07:05] Good timing, looks like the images are just popping out [07:05] bien le bonjour willcooke [07:10] My youngest wants peanut butter on a croissant for breakfast. [07:10] Is that allowed? [07:14] willcooke, in France this was subject to death penalty before it was abolished [07:15] :D [07:15] I made it for him anyway, but he decided he didnt like it. [07:16] Now I have to eat it [07:16] The sacrifices we make. [07:18] oSoMoN: merci ;) [07:48] jibel, I'm downloading xubuntu now [07:54] jibel, still getting a black screen on Xubuntu [07:54] :(( [07:55] andyrock: hey! Mind updating https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1790146 description to state that we wanting completely to drop that page? Nothing is telling that in the bug itself and the release team will likely review this [07:55] Ubuntu bug 1790146 in gnome-initial-setup (Ubuntu Cosmic) "Update Welcome page for Ubuntu 18.10" [High,In progress] [07:55] andyrock: Otheriwse, I'm sponsoring [08:01] jibel, removing quiet and nosplash at least gets to a login screen [08:01] Laney, I have tried the patch for libnma and now I can set up Canonical's VPNs again, the "CA Private Key" field simply went away after applying the patch. Thank you very much. [08:02] Laney, so please let this patch go into Cosmic. [08:02] Laney, only the DNS problem is not solved. I cannot connect to rugby.internal. [08:03] tkamppeter: Can't help you with the last thing, but good for the first [08:03] morning [08:03] morning Laney [08:03] tkamppeter: also, I got that last night when you sent it. [08:04] hey didrocks [08:05] what's up [08:07] nothing special, what about you? [08:09] bit of a sore throat today [08:09] was a small group at folk club so we ended up doing 5 songs /o\ [08:09] normal is more like 2 [08:25] Laney, what do you mean, you also got the problem with the grayed "Apply" button and the extra fields or the DNS problem? [08:28] I mean that you sent those three messages last night when I was connected to IRC, and so there wasn't any need to do it again this morning [08:42] didrocks, yaru looks nice in the installer [08:42] (but the virtualbox situation is still FUBAR) [08:43] willcooke, with build 20180927 [08:43] ? [08:44] willcooke: yeah, quite some work on the installer theming, but I agree, it looks good ;) [08:45] jibel, hm, lemme check. Maybe I did something stupid [08:45] * willcooke crosses his fingers [08:46] I'm going to clear out all my old ISOs and start again, this is getting confusing [08:46] just check the md5 [08:52] jibel, so xubuntu, from here: http://cdimage.ubuntu.com/xubuntu/daily-live/pending/ [08:52] is stil broken [08:52] the md5sums match that file and the one I downloaded [08:52] :( [08:54] jibel, trying Ubuntu Desktop now [08:55] same, broken [08:56] remove "quiet" & "splash" and I can get to a live session with a login prompt [08:57] and from there I can start the install [08:57] willcooke, what if you keep quiet splash and add nomodeset [08:57] checking [08:58] ooh [08:58] got a pointer [08:58] yes! [08:58] In to a live session [09:00] install running === abeato_ is now known as abeato [10:57] willcooke, popey, Wimpress: could you check if the telegram-snap in edge correclty auto-connects to content interfaces and use them? [10:58] Trevinho, "telegram-desktop" right? [10:59] tjaalton, hey! There is a common problem in the beta images that some flavours (xubuntu eg) and the main desktop image won't boot to a working live session from the ISO in Virtualbox. Adding nomodeset to the boot options for the live session makes it work. Once it's installed, you don't need the nomodset. Odd. Wimpress caught this which showed xorg crashing: telegram-desktop [10:59] any ideas? [11:00] willcooke: sounds like the image does not have new mesa yet [11:01] it does [11:01] then I have no idea [11:02] willcooke: yep, doing manual refresh from edge might always work though [11:05] Trevinho, fresh install, looks OK; https://paste.ubuntu.com/p/3fV6NRwvmb/ [11:05] willcooke: yeah, that always was there, but might happen that actually the mount points were not there [11:06] ? [11:06] willcooke: like this should have values [11:06] `snap run --shell telegram-desktop -c 'find $SNAP/usr/share/themes'` [11:07] Trevinho, I get the adwaita theme on File -> Open FYI [11:07] while `/snap/telegram-desktop/current/usr/share/themes` should not exist when poked from host [11:07] mh [11:08] Trevinho, snap run --shell telegram-desktop -c 'find $SNAP/usr/share/themes' [11:08] find: '/snap/telegram-desktop/281/usr/share/themes': No such file or directory [11:08] willcooke: yah, so that's the bug [11:10] willcooke: like I've this https://paste.ubuntu.com/p/yT8gj7zTbs/ [11:12] willcooke: this is what I submitted long time ago https://bugs.launchpad.net/snappy/+bug/1781906 [11:12] Ubuntu bug 1781906 in Snappy "Content provider interfaces introduced to snaps aren't correctly set up" [High,Triaged] [11:13] willcooke: also what's yours `cat /run/snapd/ns/snap.telegram-desktop.fstab|grep gtk-common-themes` [11:17] willcooke: maybe you can poke zyga about that since your system can be checked better (maybe you still have logs stating more what happened) [11:22] so, mh I don't know what's better honestly... [11:27] Trevinho, that grep returns nothing [11:28] Can you sync with kenvandine and see if he has any clues [11:28] willcooke: yeah, expected and that's the issue which prevented me to make this default [11:28] willcooke: it seems it's not much related to our stuff, it happened also with the desktop interface (the one providing fonts and such) [11:29] willcooke: it's probably better if you can provide snapd logs for installing the snap to zyga [11:29] as it's something lower level [11:31] zyga, what logs do you need? ^ [11:31] (TL;DR: content interfaces not connecting when I install the telegram snap) [11:32] jibel: what was the full kvm config for that gdm issue? [11:32] jibel: also for https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280 you had nothing in /var/crash? [11:32] Ubuntu bug 1794280 in gdm3 (Ubuntu Cosmic) "gdm doesn't start on a fresh installation of Cosmic Desktop" [Critical,Confirmed] [11:34] Trevinho, there is a plymouth crash. Nothing special about the VM, 2G of RAM, 1CPU and qxl video driver [11:34] Trevinho, you can try with vmware easyinstall too [11:34] same problem [11:34] ah no [11:35] it took a while but it eventually started [11:35] jibel: can you share the jouralctl of that machine too? As might have crashed anyway [11:35] but just restarted [11:36] Trevinho, it's attached to the bug report [11:36] jibel: I meant the vmware one that you just got starting [11:36] but after a while [11:36] sure 1sec [11:37] nothing in /var/crash [11:40] Trevinho, http://paste.ubuntu.com/p/dZ3fC9fNY9/ [11:47] jibel: ok, my easyinstallation test still has a black image [11:47] can't switch tty though [11:47] to get infos [11:48] mouse moves but nothing more, not sure it's the same [11:50] willcooke, Trevinho: reading backlog [11:51] mmm [11:51] snap changes would be lovely [11:51] also journald logs for snapd please [11:51] lastly the /var/lib/snapd/mount/*.fstab file for the affected snap [11:51] as well as the /run/snapd/ns/*.fstab counterpart (clearly labelled please) [11:51] the revision of the snap (but it should be in the logs) [11:51] and that should be it [11:52] ace, thanks zyga - I'm on it [11:53] Trevinho, please could you open a LP bug and I will gather the logs and attach them to it [11:54] yes, that would be best [11:54] I'm debugging something in that area now so perhaps related [11:55] Trevinho, ignore, I've done [11:56] willcooke: oh, sorry I thought I already linked it... https://bugs.launchpad.net/snappy/+bug/1781906 [11:56] Ubuntu bug 1781906 in Snappy "Content provider interfaces introduced to snaps aren't correctly set up" [High,Triaged] [11:56] zyga: ^^^ [11:56] hmmm [11:56] that was already there for some time [11:56] yeah, I got the email now [11:56] Trevinho: do you have the logs from snapd for this revision? [11:57] zyga: mine worked fine, willcooke one should be the best to poke [11:57] we had bugs before where part of logging was broken [11:57] and some fixes went into the mount system as well [11:58] willcooke: did that just happen on your system? [11:58] zyga, yeah [11:58] can you paste the logs please, that's most interesting to me [11:58] zyga, will do [11:59] zyga, on the bug, or pastebin, or both, or ??? [11:59] willcooke: both I guess :) [11:59] :) [11:59] yeah [11:59] :-) [11:59] $ snap changes [11:59] ID Status Spawn Ready Summary [11:59] 385 Done today at 12:03 BST today at 12:04 BST Install "telegram-desktop" snap from "edge" channel [12:00] so just one snap, that's good [12:00] was that a fresh install or a refresh from edge? [12:00] can you please show the associated tasks as well (snap tasks 385) [12:01] https://paste.ubuntu.com/p/rmTcSFZGG9/ [12:02] mmmm [12:02] ok, nothing erring here [12:02] how about in the journal? [12:02] man journalctl [12:02] :) [12:02] stand by [12:03] jounrnalctl -u snapd.service [12:03] AFAIK [12:03] or AFAIR [12:03] * willcooke hugs zyga [12:04] https://paste.ubuntu.com/p/Zz3W8dRPXF/ [12:04] (I'm adding thiese to the bug) [12:05] no mention of telegram there :/ [12:05] fstab: https://paste.ubuntu.com/p/7Fdr9nfJYm/ [12:06] ok, that's the "what we want stab" [12:06] fstab [12:07] https://paste.ubuntu.com/p/nVnJDVdjgS/ [12:08] that's the what we _have_ one [12:08] that's great [12:08] can you please run now: [12:08] sudo /usr/lib/snapd/snap-update-ns telegram-desktop [12:08] zyga, while the snap is running? [12:08] you can set SNAPD_DEBUG=1 too [12:08] yes, it's always running live [12:08] this is what happens when you connect content interfaces [12:09] (or was that SNAP_DEBUG, I never remember) [12:09] $ sudo /usr/lib/snapd/snap-update-ns telegram-desktop [12:09] 2018/09/27 13:08:53.110962 main.go:192: cannot change mount namespace of snap "telegram-desktop" according to change mount (/snap/gtk-common-themes/701/share/icons/Suru /snap/telegram-desktop/281/usr/share/icons/Suru none bind,ro 0 0): cannot use "/snap/gtk-common-themes/701/share/icons/Suru" as bind-mount source: not a directory [12:09] ha! [12:09] thank you! [12:09] oh, I didnt set that [12:09] lemme redo [12:09] * zyga is proud of _that_ error message [12:09] what is the source exactly? is it a symlink? [12:10] $ ls -l /snap/gtk-common-themes/701/share/icons/Suru [12:10] lrwxrwxrwx 1 root root 12 Sep 11 16:56 /snap/gtk-common-themes/701/share/icons/Suru -> communitheme [12:10] yes! [12:10] wham! [12:10] what does the content interface connection request? [12:11] what is the actual target and source part? [12:11] kenvandine, buzzzzzzzzzz ^ [12:11] willcooke: in the next next release (2.37) this will be a warning [12:11] woot [12:11] I'll make sure of that [12:11] thanks zyga [12:11] 2.36 is almost out now (out of master) and it's too late [12:11] nw [12:12] willcooke: I think this particular issue is more about discoverability of the problem [12:12] zyga, we need to wait for kenvandine to come online now, that'll be around 1hr. Sorry [12:13] yeah, I agree [12:13] than snapd not doing mounts correctly [12:13] cool, I've made notes that we should warn about such problems [12:14] thanks zyga. So we need to change the common-themes to not use symlinks right? [12:14] well, mount source and target cannot be a symlink [12:14] ack [12:14] so some crafting required [12:14] awesome stuff, thank you very much [12:14] I canna change the laws of linux # with scotty's voice [12:14] * willcooke talks in to his mouse [12:18] zyga: interesting finding... why this randomly works though? [12:19] Trevinho: I _suspect_ that unless you reboot and the layout of the older revisions was different (correct) you just don't notice because the old mount namespace is used [12:19] or maybe edge vs stable [12:19] I see [12:26] can anyone remember how to comment out text in moin wiki?> [12:26] comment out? hmm nope [12:27] I only remember {{{ }}} [12:27] maybe something akin to {! ... } ? [12:29] bah, [12:29] it was "##" [12:30] and, incidently, an example was right at the top of the page. le sigh [12:30] willcooke, https://wiki.ubuntu.com/HelpOnMoinWikiSyntax#Comments [12:31] yeah I saw that, but it's not what I wanted [12:31] I want to hide a whole load of content from the page, but leave it there so that we can edit it later [12:35] zyga willcooke, yes we know. jamesh was going to fix that. [12:36] Trevinho, there we go ^ [12:36] told you he'd know [12:36] :) [12:36] We debugged that last week, I think that's why he bumped the meson version in Yaru [12:36] Yaru is creating the symlink [12:37] yaru? [12:37] Theme [12:37] * zyga promises to call the next build system "build-system-from-zyga" [12:37] Lol [12:37] not random-word < /usr/share/dict [12:37] (I'll call it zbs for short) [13:14] willcooke, kenvandine. Good. However i'm pretty sure snapd should be more clear about this with proper failures probably. [13:29] Trevinho, that's what z_yga said he would do for next release of snapd [13:29] yeah.. [13:29] I've opened a bug for the provider too [13:41] jibel: weird thing... https://usercontent.irccloud-cdn.com/file/E7gnaVb8/Screencast%202018-09-27%2015%3A40%3A28.mp4 [13:42] woah [13:43] Trevinho, in qemu? [13:43] remove splash from the boot cmdline [13:45] jibel: yeah, just starting it without doing anything else (like I didn't select the language) [13:46] I can use the mouse there, but not keyboard [13:47] or if you select cirrus or vga it should work but then there are other limitations [14:25] it's weird also that if I select not to download updates, it still installs stuff [14:25] from the net [14:31] languages packs? [14:57] Trevinho: Hi, I filed the bug about ccsm here https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1794765 [14:57] Ubuntu bug 1794765 in compiz (Ubuntu) "CCSM has no icon, Gtk.Button.do_draw (self, cr), TypeError: Expected cairo.Context (Ubuntu 18.10)" [Undecided,Confirmed] [14:57] may be compiz requires a rebuild [15:34] Laney, thanks for the ping. Working on the screenshots [15:34] heh [15:34] just wanted it on The List :-) [15:34] I still need the mascot, but I can get everything else done today I think [15:34] Laney, yeah, I appreciate it, I would have been next week before I knew it [15:35] ah there's a screenshot of libreoffice which talks about bionic, guess that needs updating [15:35] actually they probably all do for yaru don't they [15:35] think so [15:36] * Laney senses a highlight [15:36] I'll redo them all [15:36] r0x0r [15:36] Laney, you know the beta still has beaver right/ [15:37] wallpaper? [15:37] ya [15:37] yes [15:37] cool [15:37] that's in the unapproved queue [15:37] ack [15:37] figured [15:37] (not even any highlight, just reading IRC ;)) [15:38] heheh [15:46] I have a mascot! [15:47] think I have a cold [15:47] * Laney is sniffling [15:47] * willcooke consides the healing powers of the cuttlefish [15:47] * Laney pouts, not even been around any freshers [15:47] considers [15:48] (what are out in force this week) [15:49] That feels like a long time ago [15:49] Hooch was cool in those days [15:49] that's back in production you know [15:50] noooo [15:50] * willcooke googles [15:50] my god [15:50] when the pub was closing down and they had to sell all their stock I had one [15:50] F M L [15:50] That explains the Viz "reverse shandy" tweet the other day [15:51] Which is of course, made with Hooch and alcohol free beer [15:51] :D [15:51] I was too young to drink it but I do remember the newz getting in a twist about alcopops when hooch first came out [15:51] :) [15:52] * Laney imagines town on a friday night [15:52] ... [15:52] hmm... [15:52] didrocks, hi, the communitheme snap description says “This package allows you to try out the theme on Ubuntu 18.04 LTS.” Will the 18.10 install ship it as a snap? [16:08] mpt: no, it shipped as a deb package [16:08] it's* [16:08] so only 18.04 LTS is a snap [16:55] kenvandine: guessing, tuesday next week for completion, I've been on PTO after the sprint [16:58] willcooke, Laney, jibel: I know why vbox initial startup fails. vboxvideo takes an eternity to initialize, and x starts before it [16:58] zomg [16:59] tjaalton, it was working ok though, in the past, so does that mean there have been some changes in xorg to make it start faster now? === Class7_ is now known as Class7 [17:00] well I'd expect the kernel driver to be ready in less than 25s [17:00] dunno why it's slow [17:02] takes nearly 30s [17:04] How does nomodeset "fix" it? [17:04] wonder if the module is in initrd, probably should be [17:06] it doesn't fix it, just works around the crash [17:06] tjaalton, why only when booting the iso and not the installed system? [17:07] jibel: dunno, check when vboxvideo shows it's initialized? [17:08] tjaalton: is that somewhat related to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1794280 ? [17:08] Ubuntu bug 1794280 in xorg (Ubuntu Cosmic) "gdm doesn't start on a fresh installation of Cosmic Desktop" [Undecided,New] [17:09] Looks all this is a race, and somewhat all connected... [17:09] Even in an installed system, when starting through grub recovery mode everything works [17:10] and vbe driver has the same issue apparently, while qxl only sometimes [17:10] dmesg & xorg log would be nice [17:11] to check the timestamps [17:11] the journal doesn't have all of this information? [17:11] ah there is something [17:12] but no,journal just has a dump with the same timestamp for kernel messages [17:13] no fb device found, so gdm is started too early [17:14] from the x log [17:15] Yeah so I was noticing too... [17:19] so with nomodeset it loads vesa which doesn't try to load glamor [17:19] ahhhh [17:19] the failing case loads both for some reason [17:20] vesa because there's no fb dev, modesetting is unloaded but loaded again later on and then it goes boom trying to init glamor (dri) [17:24] oh right, the device appeared and device hotplug kicks in and loads modesetting [17:24] sarnold: thanks [17:24] that's why [17:43] jibel: check if the initrd has vboxvideo in it.. 'lsinitramfs /boot/initrd.img-4.18.0-7-generic | grep vbox' [17:43] the initial one doesn't but one generated on the system might [17:59] ffs. [18:00] I made all the images for the slideshow, and then went and installed Ubuntu Studio over the top of that machine without copying them off first [18:02] willcooke: I've used The Sleuth Kit / Autopsy to do image recovery from busted SD card before; maybe you could get lucky? [18:02] of course installing a whole OS over the disk might be too much. but you never know. [18:03] sounds like an interesting app [18:06] sarnold, ah, nice tip, thanks. Alas I think it will take me less time to re-do them than to try it [18:07] willcooke: either way it's not fun :( [18:07] It should be quicker second time around :) [18:44] and done [18:44] :) [18:49] right, finish off in the morning. Night all